Search the Community

Had a small freakout and a minor disappointment. I worked late last night on some tones for this weekend. I turned on my Helix today to practice for rehearsal and a couple of weird things happened; let me fill you in on my set up and then describe the circumstance: For my rig I have a Helix floor unit (FW 3.71) with a James Tyler Variax plugged in. A USB cable is connecting it to my MacBook Pro (14" M1 Pro 2021 running Sonoma 14.4.1) and operating in Logic Pro 11.0.1. I use Logic to listen to tracks (and sometimes build tabs/charts) and I build my Presets using HX Edit (3.70). This morning when I booted up the Helix, I got a notification in HX Edit that the app failed to get preset names citing DSP overload (code -8611). The name of the preset seemed to be "New Preset" but it looked like it already had a string of blocks used from some other preset that weren't at all in the layout I would normally use (because I typically have the two paths running). I power cycled my Helix and then there was the same error message, but the Preset was completely blank. I was able to access other Setlists, but only the Setlist I was working on the night prior created the DSP overload error code. I attempted to restore from a backup which failed due to the same DSP overload error. I then attempted to rebuild the Presets. This attempt also resulted in the DSP overload error. I used FS9 and FS10 to restore much of the Helix to factory. This got rid of the DSP overload error. I then restored from the Backup which previously failed and I have not yet run into the DSP overload error. I unfortunately lost close to two months of work, which thankfully wasn't too bad and I am back up and running, but boy this was frustrating. I perused the forum and saw some input about what people thought the issue might be, but I don't think I saw anything conclusive. Someone commented on using the same versions of Helix FW and HX Edit versions, but all of that is up to date for me. Any ideas? I feel very paranoid now, as if I need to carry my MacBook with me to gigs now just in case this ever happens again... And you'll bet I'll be making Backups more regularly now! Has anybody else received this error code? If you did, did the error ever pop up again randomly?