Please ensure Javascript is enabled for purposes of website accessibility Jump to content

line 6 Helix bug: Simple Delay mix 100% after preset import


Smashcraaft
 Share

Recommended Posts

Found a very bad helix bug. When I copy over a preset with a simple delay from USER 1 to USER 2 (to setup a setlist for a gig), the delay mix rises to 100% after preset import. That happens no matter if I copy or export/import the preset.
On the source USER 1 everything is fine and at the target USER 2 the sound is going muddy as hell.


AI told me: The "delays mix 100" bug after importing a preset is likely caused by missing or incorrect Impulse Responses (IRs) or unrecognized models. To fix this, update both the Line 6 HX Edit app and your Helix firmware to their latest versions, and ensure any necessary IRs are correctly imported and selected within the preset's IR blocks. 


... but none of that fits the problem. Any ideas?
 

Link to comment
Share on other sites

On 11/25/2025 at 10:46 PM, theElevators said:

What version of the firmware are you on?  Sounds like a recent bug from around 3.15.  If you haven't updated your HX Edit / Firmware, you should do that.  This sounds like an HX Edit bug!

I'm using HX Edit 3.82 and FW 3.80. I always updated to the latest version as quickly as possible if no gig was expected in the next few days.

Link to comment
Share on other sites

On 11/26/2025 at 5:01 AM, waymda said:

Works fine for me. Imported, copied between setlist, conpied within set lists - mix retained@ 12% [snaphot Hook].

 

HX Edit 3.82

Firmware: 3.8 

It seems I need to completely global reset my Helix to fix the problem, but I want to wait for support first.
Maybe they'll have an idea how to find the cause of the error, which could help others avoid it.

Link to comment
Share on other sites

Do you have Snapshot Edits setting set to Recall  BTW?

 

I've had issues with parameter assignments completely not working when editing one preset, it would affect the other, etc.  The issue for me was on 3.15, before I downgraded to 3.11.  And now I'm on 3.7.10 -- no such issues for me there.  Maybe it's a new bug with HX Edit on Mac or Windows. 

 

What happens if you save to a different setlist from within the Helix?  Simply press save, and select a different setlist.  

 

Also, sometimes presets become corrupted as well.  I've had this one preset that just had a different gain compared to the others.  I checked one block at a time, recreated it, and the sound was back to normal.  I haven't been able to pinpoint what exactly was different, but I had to basically recreate the preset from scratch, so it would start behaving correctly.  

  • Like 1
Link to comment
Share on other sites

On 11/26/2025 at 3:30 PM, theElevators said:

Do you have Snapshot Edits setting set to Recall  BTW?

Good point, but… no. This preset ran stably over a month in USER 1 and wasn't changed.
It only occurs when copying it to a different setlist, even though all values in the file are (verifiably) correct.
I will do the full reset next time I have the device on my PC.
Link to comment
Share on other sites

On 11/26/2025 at 5:01 AM, waymda said:

Works fine for me. Imported, copied between setlist, conpied within set lists - mix retained@ 12% [snaphot Hook].

 

HX Edit 3.82

Firmware: 3.8 

Are you absolute sure you tested snapshot 4 in this preset?
Because I have done a full reset now and the mix is still at 100% in this snapshot.

 

Okay, things are getting completely crazy now!!!

To explain again how I even noticed the error:

 

Bank USER 1 is where I collect and edit all my presets. I use this bank at home and at rehearsals.

To prepare for our gig two days ago, I copied all the USER 1 presets from the evening's playlist (including "Judas Priest - Breaking the Law") to USER 2 in the correct order of our band's setlist.

While playing through the songs on Bank USER 2 one last time before the gig, I noticed the delayed, muddy sound with the "Simple Delay" set to 100%.

 

I then opened this thread and a support ticket, but decided to access the presets from USER 1 for the gig, just to be safe (which involved a bit more searching, since that bank was unsorted).

 

Today, two days after the gig, I performed the recommended full reset of the Helix.
First, I loaded my exported preset of the song "Breaking the Law" (attached here) into the now completely empty USER 1 bank.

Result: Preset on USER 1, Simple Delay Mix 100%


Wow, that confused me, because waymda wrote that the preset was perfectly fine.

So I did a full restore from my last backup, and... now this preset is also corrupted and muddy in the restored USER 1 bank.
That's the exact same user bank I used for a flawless gig on Thursday!


So I restored my second-to-last backup.

Result: Preset on USER 1, Simple Delay Mix 100%


So I restored a backup that's a week old.

Result > Preset on USER 1, Simple Delay Mix 100%


So I restored a one-month-old backup.

Result > Preset on USER 1, Simple Delay Mix 100%


This definitely can't be right, because I played all the countless band rehearsals of the last few weeks perfectly fine with exactly this one preset on USER 1. It looks like I'll have to do a series of full resets in a row, because some kind of error has crept into the system.

Edited by Smashcraaft
Things got complicated
Link to comment
Share on other sites

Unfortunately, I now have to stop trying to reproduce the error and its source, since the entire system has decided to abandon all logic.

No matter which backup I use to restore the preset, it always has a delay mix that was definitely not at maximum at the time of the backup.


However, the very latest backup, where I manually adjusted the "Simple Delay" mix again, produces a clean result even after the restore.

It's really strange but apparently, there's a discrepancy between what was backed up before the full reset and what was backed up afterward.

Link to comment
Share on other sites

As I've also mentioned.  A few times for me a preset would become "corrupted".  The only thing to do is to recreate it from scratch, then it would start behaving normally.  You need to get to the bottom of this by recreating the preset, one block at at time, then try the experiment again.  If a preset is corrupted, then expecting it to work properly is just a waste of time.  

  • Like 1
Link to comment
Share on other sites

I understand your point. I will conduct all possible tests to ensure that this preset will remain reliable in the future.
Should further anomalies emerge, I hope they will help me better understand the underlying problem.

Hope springs eternal (as they say) :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...