Helix Bug Reports

[datacommando]

3 hours ago, fremen said:

Wondering if someone here experienced such a bug :

Hi Fremen,

 

There is a post here about this issue and it seems the fix is a reinstall of the firmware, and to follow the install instructions exactly. Something may have been accidentally overlooked during the remote install.

 

Hope this helps/makes sense.
 

link:

 

[fremen]

Thanks ! I'll forward this to the user :)

[AeroUSA]

Hi everyone. I am trying to use my HX Stomp with a Boss RC-500 looper. I would like the RC-500 to send the tempo information to the HX. This works correctly until I stop a loop on the RC-500. The HX then returns to its default bpm value. I tested this with my Fractal FM3 and it did not happen so I believe the issue is with the Stomp. Any help would be appreciated. 

[shmaque]

1 hour ago, AeroUSA said:

Hi everyone. I am trying to use my HX Stomp with a Boss RC-500 looper. I would like the RC-500 to send the tempo information to the HX. This works correctly until I stop a loop on the RC-500. The HX then returns to its default bpm value. I tested this with my Fractal FM3 and it did not happen so I believe the issue is with the Stomp. Any help would be appreciated. 

Correct, the HX logic (at least up to the last time I did this a year or so ago) needs the midi clock constantly sent to it to be slaved to that tempo - it doesn’t train its internal clock to the midi clock, but rather switches over to it wholesale (tap led turns blue iirc). Once the midi clock stops being received, it reverts to its internal clock (which hasn’t been re-trained at all throughout this process). 
 

And yes, this is contrary to how several other vendors do it, and is super annoying. 

[AeroUSA]

12 minutes ago, shmaque said:

Correct, the HX logic (at least up to the last time I did this a year or so ago) needs the midi clock constantly sent to it to be slaved to that tempo - it doesn’t train its internal clock to the midi clock, but rather switches over to it wholesale (tap led turns blue iirc). Once the midi clock stops being received, it reverts to its internal clock (which hasn’t been re-trained at all throughout this process). 
 

And yes, this is contrary to how several other vendors do it, and is super annoying. 

Thanks. What I want to do is tap the tempo in for a freeform loop and then switch to a saved loop that has a specified tempo which is sent to the Stomp...

[shmaque]

34 minutes ago, AeroUSA said:

Thanks. What I want to do is tap the tempo in for a freeform loop and then switch to a saved loop that has a specified tempo which is sent to the Stomp...

As long as the Stomp is being sent a MIDI tempo/clock, it'll slave to that. If that (constant) clock goes away, it'll revert to whatever you had previously tapped in. So, depending on how the loops work on your RC500, that's either ideal or makes it impossible to do what you want to do :) (It's an all or nothing thing, and I'm not sure if you can arbitrarily tell the RC500 to send clocks or not send clocks on a loop by loop basis)

[danieles]

Meters on compressor have some big lag issue.

It works fine after rebooting the Helix, but after editing for a while they reliably start lagging to the point that they're unusable.

[Elephantstomp]

Hello, I copied a text that I wrote someone here.

 

HX STOMP - NO SOUND

Once in a while my Stomp also has no Sound.

Everything else works as it should.

The first time I was really concerned and checked all other Equipment around.

Then I simply switched the unit off and on again and it was fixed.

Now I am used to it and know what to do.

This is anything but nice.

 

Thanks

[Ilya-V]

I've posted this on TGP too.

Das Benzin Lead preamp only lacks a lot of volume.

 

My bypassed guitar is twice as loud than this preamp even with Master and Ch volumes at 10.

[kreator1972]

I am the only one that after updating to 3.0 is constantly losing usb connection ? I am on a windows 10 pc, all drivers are up to date

[rondesjardins]

Updated HX Stomp to 3.0 last night.

Now, when in Snapshot mode...the foot switches are not changing the Snapshot, or lighting up the selected footswitch.

For example...I'm in Snapshot mode and FS1 is lit, and the screen indicates that I'm on FS1. If I select FS2 or FS3, the footswitch does not light up, nor does the Snapshot # change on the display screen. The only thing that changes is that the letter "E" appears under the camera icon on the screen.

 

If I switch to any other mode, all of the footswitches work as expected. As soon as I switch back into Snapshot mode, footswitches do not work or light up (except for whichever foot switch I last pressed in one of the other modes). Meaning, if I was in Snapshot mode and FS1 was lit, then switched to "Stomp" mode and pressed FS2, when I switch back to Snapshot mode...FS2 is now lit....but I cannot change the snapshot by clicking FS1 or FS3.

 

If I go into "Command Center", and set the function of FS1 and FS2 to "Snapshot"...it seems to work...HOWEVER if I have also Stomp assignments to each of those switches (say a Chorus on FS1 and Delay on FS2)....when I'm in Snapshot mode and select FS1 or FS2...it'll change the snapshot but ALSO change the status of the assigned stomp to that switch (it should ONLY be changing the Snapshot when in Snapshot mode).  ALSO, In Command Center, I cannot assign a function to FS3 (when turning the button to change the command for FS3...it does nothing....but works fine when trying to set the command for FS1 and FS2).

 

I have upcoming gigs and need Snapshots to work properly.

Is this a bug in 3.0? 

[molul]

26 minutes ago, rondesjardins said:

Updated HX Stomp to 3.0 last night.

Now, when in Snapshot mode...the foot switches are not changing the Snapshot, or lighting up the selected footswitch.

For example...I'm in Snapshot mode and FS1 is lit, and the screen indicates that I'm on FS1. If I select FS2 or FS3, the footswitch does not light up, nor does the Snapshot # change on the display screen. The only thing that changes is that the letter "E" appears under the camera icon on the screen.

 

If I switch to any other mode, all of the footswitches work as expected. As soon as I switch back into Snapshot mode, footswitches do not work or light up (except for whichever foot switch I last pressed in one of the other modes). Meaning, if I was in Snapshot mode and FS1 was lit, then switched to "Stomp" mode and pressed FS2, when I switch back to Snapshot mode...FS2 is now lit....but I cannot change the snapshot by clicking FS1 or FS3.

 

If I go into "Command Center", and set the function of FS1 and FS2 to "Snapshot"...it seems to work...HOWEVER if I have also Stomp assignments to each of those switches (say a Chorus on FS1 and Delay on FS2)....when I'm in Snapshot mode and select FS1 or FS2...it'll change the snapshot but ALSO change the status of the assigned stomp to that switch (it should ONLY be changing the Snapshot when in Snapshot mode).  ALSO, In Command Center, I cannot assign a function to FS3 (when turning the button to change the command for FS3...it does nothing....but works fine when trying to set the command for FS1 and FS2).

 

I have upcoming gigs and need Snapshots to work properly.

Is this a bug in 3.0? 

Oops! :( I think I'm waiting a few days before updating my Helix LT. I use snapshots a lot.

[rondesjardins]

3 hours ago, rondesjardins said:

Updated HX Stomp to 3.0 last night.

Now, when in Snapshot mode...the foot switches are not changing the Snapshot, or lighting up the selected footswitch.

For example...I'm in Snapshot mode and FS1 is lit, and the screen indicates that I'm on FS1. If I select FS2 or FS3, the footswitch does not light up, nor does the Snapshot # change on the display screen. The only thing that changes is that the letter "E" appears under the camera icon on the screen.

 

If I switch to any other mode, all of the footswitches work as expected. As soon as I switch back into Snapshot mode, footswitches do not work or light up (except for whichever foot switch I last pressed in one of the other modes). Meaning, if I was in Snapshot mode and FS1 was lit, then switched to "Stomp" mode and pressed FS2, when I switch back to Snapshot mode...FS2 is now lit....but I cannot change the snapshot by clicking FS1 or FS3.

 

If I go into "Command Center", and set the function of FS1 and FS2 to "Snapshot"...it seems to work...HOWEVER if I have also Stomp assignments to each of those switches (say a Chorus on FS1 and Delay on FS2)....when I'm in Snapshot mode and select FS1 or FS2...it'll change the snapshot but ALSO change the status of the assigned stomp to that switch (it should ONLY be changing the Snapshot when in Snapshot mode).  ALSO, In Command Center, I cannot assign a function to FS3 (when turning the button to change the command for FS3...it does nothing....but works fine when trying to set the command for FS1 and FS2).

 

I have upcoming gigs and need Snapshots to work properly.

Is this a bug in 3.0? 

 

SO...an update.

I hooked up the Stomp to my computer and launched HX Edit. I then went into a preset and tried selecting the Snapshots within the Snapshot dropdown. Each time I did this, I got the following error message in an orange bar across the top of the HX Edit window:  "The Helix failed to recall the snapshot data properly."

 

This error message happened regardless of the preset I selected in HX Edit. 

 

THANKFULLY, I did a Backup before updating to 3.0.

So, I just "Restored from Backup", which reloaded all my presets and the Snapshot switches now work! Success...well, kinda...

 

As I went through each preset, the first Snapshot would typically be just amp and reverb, and the second snapshot would add a delay (and maybe a drive). When I load the preset the first Snapshot comes up fine. Then, when I press FS2 and get the second snapshot, it also turned on the delay (as expected). But, when I hit FS1 to go back to the first snapshot it did not turn off the delay block (that was only supposed to be on in snapshot 2)  Interestingly, for presets where I had a preset with 3 snapshots...each with a different delay setting....it still had all of the correct delay settings/values per snapshot. It just seems that if you have snapshots that turn on/off different block...the 3.0 update (at least on my Stomp) did not maintain the on/off (bypass) state of the blocks in each snapshot.

To resolve this....I went into each of my presets...looked at the first snapshot and noted which blocks were "off". Then I went into the second snapshot and noted which ones turned "on". THEN, I went back to the first snapshot and turned off the block(s) that shouldn't be on in that snapshot. I then saved the preset....and it "seems" to work fine now.

 

Thankfully I only have a small # of presets with relatively simple settings. If you have a lot of presets, fixing them this way would be very tedious. 

Hopefully Line6 can advise if this is a bug and get a fix released soon.

 

Hope this helps someone.

[molul]

Isn't it "normal" making a backup of your presets and system settings and restore them after updating?

[datacommando]

6 hours ago, rondesjardins said:

So, I just "Restored from Backup", which reloaded all my presets and the Snapshot switches now work!

The thing about updates is, you are advised to do a backup because everything will be reset to factory defaults. First thing most people notice is the global settings have changed. Reload your backup and everything should be fine.

 

Hope this helps/makes sense.

[Pamp1nos]

3.0 Firmware New Bug Report !!
Hello guys. So there's a bug that's caused ONLY when you turn Spillover ON. I've double checked it and here's what happens. Let's say you have all EXP(1,2 & 3) pedals set to Global Position which means they keep their value while you change presets. Now, lets say you have a Volume pedal on Exp 3, while you have Spillover OFF,  it works just fine, retaining its value while you go through presets. When you have Splillover ON tho, that value keeps switching while you change presets and especially when you have EXP 3 as your volume pedal, you get massive ups and downs on volumes between presets, which is annoying. The same problem happens to EXP1 and EXP2 as well. I hope they fix it soon cause Spillover is kind of a good Addon but it's useless like that.

[firehawkkwah]

My Variax settings per snapshot seem to have disappeared. 

 

F/W 3.0

Edit version 3.0

Windows 7

Helix LT

Variax Standard

 

My presets have snapshots with different Variax models. Snap 1 is Spank3, Snap 2 is Lester5, Snap 3 is Magnetics, etc.

 

Since updating to 3.0 none of the snapshots recall those settings.

Now the all Snapshots (with Variax as input)  just shows whatever the knobs on the variax show.  ie, if I have the knobs on Variax set to T model 1, then all the snaps in that preset shot Tmodel 1 as the Variax input. 

[datacommando]

5 minutes ago, firehawkkwah said:

My Variax settings per snapshot seem to have disappeared.

Fire up HX Edit and choose to reload the backup you made before updating to v3.0. You should see the option to reload your Global settings. That should bring it back to how you had it set. If not, reload everything in your backup, as the settings for the Variax may be stored in each preset.

 

See if that helps.

 

You did make a back up didn’t you?

 

;-)

[Mikkelmusiker]

I Just updated to 3.0, and it worked fine..almost. It says its running 3.0, but there's no new fearures. What to do?

As you can see- no acoustic sim here. 

[medle]

On 10/13/2015 at 9:54 PM, archisc said:

1) Helix randomly freeze when I create patches from scratch.. like adding stomp boxes or amps. Don't know if there is a particular pattern or happens only with certain amp and stomps.

I found the same issue today on my HXstomp, after firmware update 3.0, twice, addiing or moving patches with editor on Mac (high sierra), no sound going out, need a reboot to fix it.

 

Gian

[PeterHamm]

1 hour ago, firehawkkwah said:

My Variax settings per snapshot seem to have disappeared. 

 

F/W 3.0

Edit version 3.0

Windows 7

Helix LT

Variax Standard

 

My presets have snapshots with different Variax models. Snap 1 is Spank3, Snap 2 is Lester5, Snap 3 is Magnetics, etc.

 

Since updating to 3.0 none of the snapshots recall those settings.

Now the all Snapshots (with Variax as input)  just shows whatever the knobs on the variax show.  ie, if I have the knobs on Variax set to T model 1, then all the snaps in that preset shot Tmodel 1 as the Variax input. 

This is a global issue, but the global setting you need to change is not in globals, instead it is the first dial when you page to the Variax input block. Can't remember the name of it. but you change that and you are golden across all your patches.

 

[phil_m]

5 hours ago, Mikkelmusiker said:

I Just updated to 3.0, and it worked fine..almost. It says its running 3.0, but there's no new fearures. What to do?

As you can see- no acoustic sim here. 

 

You need to update HX Edit.

[phil_m]

10 hours ago, Pamp1nos said:

3.0 Firmware New Bug Report !!
Hello guys. So there's a bug that's caused ONLY when you turn Spillover ON. I've double checked it and here's what happens. Let's say you have all EXP(1,2 & 3) pedals set to Global Position which means they keep their value while you change presets. Now, lets say you have a Volume pedal on Exp 3, while you have Spillover OFF,  it works just fine, retaining its value while you go through presets. When you have Splillover ON tho, that value keeps switching while you change presets and especially when you have EXP 3 as your volume pedal, you get massive ups and downs on volumes between presets, which is annoying. The same problem happens to EXP1 and EXP2 as well. I hope they fix it soon cause Spillover is kind of a good Addon but it's useless like that.

 

Well, I'm not exactly sure that's a bug. Your presets may just be a different levels. The EXP Position set to Global maintain the position of the expression pedal through preset changes, but the relative level of the signal it's control will be different, so you can still have volume fluctuations.

[Pamp1nos]

1 hour ago, phil_m said:

 

Well, I'm not exactly sure that's a bug. Your presets may just be a different levels. The EXP Position set to Global maintain the position of the expression pedal through preset changes, but the relative level of the signal it's control will be different, so you can still have volume fluctuations.

 

No Phil. My presets are on the same level. I use these presets on live gigs so, the whole pedal is set correctly when it comes to leveling sounds. That's what i'm saying. It doesn't maintain the position when the pedal is set to Spillover ON. If you said Spillover OFF, it works just fine. In simple words, when Spillover is Off, Global Position works correctly on all EXP pedals. When Spillover is ON, Global Position on all EXP pedals doesn't work and instead it gives you an almost random pedal position value every time you change preset, even if you don't touch the EXP pedal at all. I could have it to 50% for example while playing "Preset 1", then switch to "Preset 2" or any other preset ( i also tried switching 3-4 presets in a row), and figure out it gives me some random Values (say 82% or 36% for example) and even when i go back to Preset 1, there's a 50-50 chance it gives me a random number again. Some times it keeps up with the Global position and some other times, it doesn't. Check it out and tell me if it works ok for you please. Thank you for your reply.

[phil_m]

35 minutes ago, Pamp1nos said:

 

No Phil. My presets are on the same level. I use these presets on live gigs so, the whole pedal is set correctly when it comes to leveling sounds. That's what i'm saying. It doesn't maintain the position when the pedal is set to Spillover ON. If you said Spillover OFF, it works just fine. In simple words, when Spillover is Off, Global Position works correctly on all EXP pedals. When Spillover is ON, Global Position on all EXP pedals doesn't work and instead it gives you an almost random pedal position value every time you change preset, even if you don't touch the EXP pedal at all. I could have it to 50% for example while playing "Preset 1", then switch to "Preset 2" or any other preset ( i also tried switching 3-4 presets in a row), and figure out it gives me some random Values (say 82% or 36% for example) and even when i go back to Preset 1, there's a 50-50 chance it gives me a random number again. Some times it keeps up with the Global position and some other times, it doesn't. Check it out and tell me if it works ok for you please. Thank you for your reply.

 

I just tried it using my Rack, and it's working as expected. I haven't tried it on my Floor yet.

 

Have you done a factory reset since updating?

[Pamp1nos]

2 hours ago, phil_m said:

 

I just tried it using my Rack, and it's working as expected. I haven't tried it on my Floor yet.

 

Have you done a factory reset since updating?

 

Yeah.. I've done a Global Reset. I also restored my back up twice but nothing worked. Like i said, it only happens when i have spillover on. When it's off, everything is fine.

[phil_m]

34 minutes ago, Pamp1nos said:

 

Yeah.. I've done a Global Reset. I also restored my back up twice but nothing worked. Like i said, it only happens when i have spillover on. When it's off, everything is fine.

 Yes, I tried it with Spillover on when I tested it on my Rack as well.

[Pamp1nos]

2 minutes ago, phil_m said:

 Yes, I tried it with Spillover on when I tested it on my Rack as well.

 

Ok. I would appreciate to get your feedback whenever you try it on Floor. I'm curious to see if it's a general bug or just happens to me :) Thank you in advance !!

[firehawkkwah]

16 hours ago, datacommando said:

Fire up HX Edit and choose to reload the backup you made before updating to v3.0. You should see the option to reload your Global settings. That should bring it back to how you had it set. If not, reload everything in your backup, as the settings for the Variax may be stored in each preset.

 

See if that helps.

 

You did make a back up didn’t you?

 

;-)

I restored to to the backup and everything worked fine.

Then when I restarted the Helix it  started updating automatically back to 3. Rebuilding the presets. Without any intervention from me.

 

So now it's back to 3, even though I didn't try, and the Variax assignments through snapshots works.

So I'm ok, but the whole thing was a little weird!

[alighton]

3.0 computer crash bug?

 

I'm having a pretty consistent computer reboot issue when I turn off the 3.0 Helix LT while it is the selected interface in Ableton. This is a fairly recent build Windows 10 20H2 build computer that has been rock solid up until 3.0 Helix. 

 

If the Helix is the selected Audio interface and I turn off the Helix with the DAW running, it will consistently crash the PC.

If I select my Tascam as the audio interface instead, turning off the helix does not crash the PC.

 

A friend of mine has a stomp with a similar build PC and he has noticed the same thing, except he uses Reaper.

[phil_m]

10 minutes ago, alighton said:

3.0 computer crash bug?

 

I'm having a pretty consistent computer reboot issue when I turn off the 3.0 Helix LT while it is the selected interface in Ableton. This is a fairly recent build Windows 10 20H2 build computer that has been rock solid up until 3.0 Helix. 

 

If the Helix is the selected Audio interface and I turn off the Helix with the DAW running, it will consistently crash the PC.

If I select my Tascam as the audio interface instead, turning off the helix does not crash the PC.

 

A friend of mine has a stomp with a similar build PC and he has noticed the same thing, except he uses Reaper.

Well, don’t do that... It doesn’t happen all the time, but Reaper will often crash if you turn off the interface while it’s running.

 

What would be the reasoning for powering off the Helix before closing Reaper?

[hefonthefjords]

Think I found a bug. Helix Floor 3.0, HX Edit 3.0

If you switch on spillover mode with HX Edit connected everything works as expected and HX Edit correctly reflects what's going on in the unit.
If you then turn off spillover mode, HX Edit doesn't show the second path again in any preset until you restart HX Edit.

[alighton]

It doesn't just crash Ableton, it crashes the whole PC. It's not that big a deal, I just have to remember to kill the DAW or change the interface before turning off the Helix. But it's still unexpected and undesirable behavior that I think is new with 3.0.

[angusstornoway]

Poly Capo not showing in HX edit.

[datacommando]

1 hour ago, angusstornoway said:

Poly Capo not showing in HX edit.

 

Hi,

 

Strange, if just that is missing?

 

Make sure that you are running HX Edit v3.0 - then check under "Pitch/Synth" - > Mono and it should be right there under Poly Pitch and Poly Whammy. If not do a Factory Reset on your hardware.

 

Hope this helps/makes sense

[angusstornoway]

Thank you, correct. I had not updated the HX edit.

[Mandomony]

hi everyone, i updated to 3.0 on my helix lt and I'm not able to see the new amp models and poly tune  any suggestion?

[phil_m]

8 minutes ago, Mandomony said:

hi everyone, i updated to 3.0 on my helix lt and I'm not able to see the new amp models and poly tune  any suggestion?

 

Yes, I suggest searching before asking a question... :-)

 

 

[StaccoP2P]

Downloaded 3.0 on Friday,  been playing with it happily since. A while ago, which switching presets it got stuck and HX suddenly disconnected. I've restarted both but no dice. It´s stuck on the same presets and neither the foot-switches nor the joysticks are doing anything. Thankfully I backed everything up today, but is this "absolute freeze" thing a known issue )I've only had the Helix for a couple of months.

 

Any ideas or recommendations? Thanks!

[phil_m]

7 minutes ago, StaccoP2P said:

Downloaded 3.0 on Friday,  been playing with it happily since. A while ago, which switching presets it got stuck and HX suddenly disconnected. I've restarted both but no dice. It´s stuck on the same presets and neither the foot-switches nor the joysticks are doing anything. Thankfully I backed everything up today, but is this "absolute freeze" thing a known issue )I've only had the Helix for a couple of months.

 

Any ideas or recommendations? Thanks!

 

It sounds like it could be a corrupted preset. If you power up while holding FS11 & FS12 down, that will clear the current preset.

 

If that doesn't work, you can do a factory reset by holding down FS9 & FS10 while powering up and then do a Restore from Backup.