Helix Bug Reports

[screwjack]

Thanks both!

 

Peter - Helix is/was on the latest FW and yes it is awesome - it was losing some of that functionality that was so disturbing!  HX Edit was not fully updated - now at 3.1.  

 

I must have missed a HX Edit update notice or something.  The odd thing is that i was able to use the new cabs on what must have been HX Edit 3.0 (which is how I knew about the graphical cab mic-ing).  Or my backup got out of sync when I upgraded my Mac to a new machine and restored.  Lesson learned on checking the SW version in any case.

 

File under RTFM.

[datacommando]

On 3/1/2023 at 1:08 PM, screwjack said:

Or my backup got out of sync when I upgraded my Mac to a new machine and restored.  Lesson learned on checking the SW version in any case.

 

Hi,

 

As noted in the link I provided regarding updating HX Edit if you don't see the new stuff - on some Macs, it is sometimes the case that when installing the new version of HX Edit an older version may still be launched by clicking on an "alias" to the previously installed version. It's always wise to double check.

 

Enjoy your new cabs.

[molul]

Huh, found a big bug this morning. I made a backup, saved a bundle and two setlists from my Helix LT, and when importing them to HX Native, all Amp+Cab blocks have been changed to just the amp.

 

I'm reporting it to Line6 right now.

[datacommando]

On 3/3/2023 at 1:51 PM, molul said:

Huh, found a big bug this morning. I made a backup, saved a bundle and two setlists from my Helix LT, and when importing them to HX Native, all Amp+Cab blocks have been changed to just the amp.

 

I'm reporting it to Line6 right now.

 

Hi,

 

That's weird - I just imported a Bundle of the entire contents of my Helix floor and everything is it should be. No missing cabs, or anything else, here.

 

Mysterious.

 

Have to you tried importing the bundle and setlists again - maybe a computer glitch?

[molul]

Tried a few times, yes. I have to try exporting again and see what happens. It's weird because this has never happened until this time, and I've exported a few times since I updated to 3.50 without issues.

[Andreas0815]

Hi Line-6 & community,

 

I came across the following issue on my HX Stomp (firmware 3.50) regarding TAP Tempo Function:

 

a) Using footswitch FS3 (works as expected):

 

1) Assign FS3 to Tap/Tuner.

2) Send Midi CC 51 (Emulates FS3) with value 127 to the HX stomp

3) Wait for 1-2 seconds

 

Result: the device switches to the tuner display (as expected).

 

b) Using footswitch FS5 (inconsitent behaviour):

 

1) Assign FS5 to Tap/Tuner.

2) Send Midi CC 53 (Emulates FS5) with value 127 to the HX stomp

3) Wait for 1-2 seconds

 

Result: the device does *NOT* switch to tuner display, other than the previous example!

 

As a workaround a separate cc 68 message (Tuner screen on/off) can be send to the device, but this requires a more complex setup or more dedicated external switches which is sad because it works perfectly using footswitch FS1-3 assigned to Tap/Tuner and using their corresponding CCs.

 

Dear Line6, please let me kow your opinion about this issue/inconsistency.

 

Kind regards in advance,

Andreas

 

PS: Loving the HX Stomp, it is just so versatile... and after this bugfix even more so! ;)

[bsimmons106]

 

I’m not sure if this is a bug, or intended to work this way, but I have had this issue on my HX Effects through multiple devices, resets and upgrades, and it is an issue on all of them.

 

Currently using HX Effects on 3.5

 

I have a mission spring loaded effects pedal that is inactive on the snapshots, but is set to activate the effect when the pedal is moved and then deactivates once it returns back to normal (0%) position.

If I engage the pedal for a wha effect, then release and quickly change to a different snapshot, the wah pedal is active on the next snapshot when it should not be, and does not inactivate even though the pedal is back in its (0%) position.

This basically activates the muffled wah effect on my snapshots where it the effect should not be engaged and there is not a good way to disengage it, because the pedal is already at its (0%) position.

[theElevators]

On 3/6/2023 at 10:57 AM, bsimmons106 said:

 

I’m not sure if this is a bug, or intended to work this way, but I have had this issue on my HX Effects through multiple devices, resets and upgrades, and it is an issue on all of them.

 

Currently using HX Effects on 3.5

 

I have a mission spring loaded effects pedal that is inactive on the snapshots, but is set to activate the effect when the pedal is moved and then deactivates once it returns back to normal (0%) position.

If I engage the pedal for a wha effect, then release and quickly change to a different snapshot, the wah pedal is active on the next snapshot when it should not be, and does not inactivate even though the pedal is back in its (0%) position.

This basically activates the muffled wah effect on my snapshots where it the effect should not be engaged and there is not a good way to disengage it, because the pedal is already at its (0%) position.

Check if your expression pedal is set to "per snapshot" for your Expression Pedal 2.  Set it to "per preset" instead, that's what I personally use.  Or use "global". 

 

Basically, do you want your expression pedal's percentage to stay the same when you go between presets/snapshots? 

 

-- global: your expression pedal stays a the same percentage when you change your presets or snapshots

-- per preset: your expression pedal gets reset to the percentage that you saved your preset as

-- per snapshot: your expression pedal gets reset to the percentage that you saved each individual snapshot as

 

Go to Global settings / EXP pedals / and twist the knob for your Expression Pedal 2 and set it to the desired value. 

 

 

 

Otherwise, if you have it "per snapshot", then when you switch to that snapshot, the position of the expression pedal is as you saved it.  So if you saved that snapshot  with the pedal at 6% instead of 0%, you will have this engaged wah sound....

 

 

 

[Guitarmaniac64]

When are you gonna fix the offset tuner issue?
I use the offset settings on the tuner to tune my true temperamented fretted guitar 
i set it up as follows 

Low E string = -2

A-string  = 0

D-string = +2

G-string = +4

B-string = -1

High E-string = -2
If i save a backup to my computer and have ticked in all "boxes" i guess tuner is  "global" and then load in that backup later on (it doesn't matter if i have upgraded the firmware or if i am on the same firmware)
All offset setting i have setup works except the D-string which stay on = 0 so i always have to change it to +2 otherwise my TT fretted guitar will not be in tune
I have reported it here before maybe i need to send in a ticket as it shouldnt take alot of time to fix that bug.

Hope it will be fixed on the next firmware update

[rd2rk]

On 3/9/2023 at 5:25 AM, Guitarmaniac64 said:

When are you gonna fix the offset tuner issue?

 

"You" doesn't hang out here. If you want L6 to hear your plea, you need to open a support ticket.

Sucks, but it is what it is.

[bbehrens]

I think that I have found a bug in Helix 3.5 New Cabinet Models. I thought that I liked the sound of a Dual Cab (1x12 Grammatico with the 2x15 Brute Bas Cabinet) with the US Double Nrm Amp Model. I found two issues: 1) It crashed Helix Native in Reaper and I suspect other DAWs as well.

[datacommando]

On 3/17/2023 at 9:56 AM, bbehrens said:

and I suspect other DAWs as well.

Have you checked this using anything other than Reaper?

 

You haven’t specified what version of Reaper, your computer type and operating system details. It’s good to know these things.

 

Hope this helps/makes sense.

[bbehrens]

On 3/17/2023 at 5:15 AM, datacommando said:

"version of Reaper"

 

Thanks,

 

I always keep Reaper at the latest version v6.78 Win64. I was posting in the hopes that others with other DAWs would reply and see if the issue is present in other DAWs as well.

 

[rd2rk]

On 3/17/2023 at 3:56 AM, bbehrens said:

I think that I have found a bug in Helix 3.5 New Cabinet Models. I thought that I liked the sound of a Dual Cab (1x12 Grammatico with the 2x15 Brute Bas Cabinet) with the US Double Nrm Amp Model. I found two issues: 1) It crashed Helix Native in Reaper and I suspect other DAWs as well.

 

Confirmed in Reaper and LIVE11.

Reaper simply crashes out. LIVE11 crashes the AI too!

 

Further notes -

Factory Bass presets work fine

Specifically affects Bass models in NEW Presets (or editing Factory Presets)

Bass+Cab or Bass Amp and separate Cab both crash

 

Bass+Legacy or Bass Amp and separate Legacy Cab work fine, BUT...

If you then attempt to switch the Legacy Cab to a new model Cab, it allows the change without crash, but the Native Output Meter instantly spikes with NO signal reaching the Reaper track.

 

All of these anomalous behaviors ONLY occur with the NEW Bass Cabs. Legacy and Guitar (new or legacy) Cabs do not cause a problem.

 

OP - Congratulations, you've found a bug! Open a support ticket so that L6 can confirm and pass it up to the bug killers!

[bbehrens]

Thanks datacommando and rd2rk,

 

I have updated the Support Ticket with some additional information from rd2rk. I don't like finding bugs! Save your congratulations for Line 6 who will squash the problem like a... bug?!?!?

[johnbeamon]

From the 3.50 Release Notes under "Bug Fixes in 3.50".

 

• When assigning block bypass to an expression pedal, Behavior > "Heel Down" or "Toe Down" could sometimes revert to "Toggle"—FIXED

 

This is not fixed. I have a block of presets in which I try to use this feature, because an auto-return/switchless wah is great. I powered on my unit yesterday, found all these Toe Down settings reverted back to Heel Down. I corrected them all, saved them, and found some of them changed AGAIN on second inspection. I corrected and saved them, rebooted the unit. They came up reset to Heel Down. I corrected and saved all of them. Copied them to a new set of Preset slots. Every one of them changed from my Toe Down spec to Heel Down between my fixing them and my pasting them into new slots.

 

This is NOT fixed. It's a valuable feature that I really want to use. But I'm having to pack an external switchless wah to manage a feature Line 6 says was fixed. Where's the QC in this bug report?

[datacommando]

On 3/26/2023 at 11:10 PM, johnbeamon said:

From the 3.50 Release Notes under "Bug Fixes in 3.50".

 

• When assigning block bypass to an expression pedal, Behavior > "Heel Down" or "Toe Down" could sometimes revert to "Toggle"—FIXED

 

This is not fixed. I have a block of presets in which I try to use this feature, because an auto-return/switchless wah is great. I powered on my unit yesterday, found all these Toe Down settings reverted back to Heel Down. I corrected them all, saved them, and found some of them changed AGAIN on second inspection. I corrected and saved them, rebooted the unit. They came up reset to Heel Down. I corrected and saved all of them. Copied them to a new set of Preset slots. Every one of them changed from my Toe Down spec to Heel Down between my fixing them and my pasting them into new slots.

 

This is NOT fixed. It's a valuable feature that I really want to use. But I'm having to pack an external switchless wah to manage a feature Line 6 says was fixed. Where's the QC in this bug report?

 

Sadly, there are no Line staff here and only very occasionally do they visit these forums - (See the “sticky comment” in the black banner stripe at the top of this page entitled “Welcome to the Line 6 forums”).

It might be wise to raise a ticket with Customer Support and then at least they will be aware of the issue.

 

Hope this helps makes sense.

[maxm17]

This one is killing me.  98% sure it's not a setting.

HXFX running 3.50

Using snapshots.

Create two snapshots with an Ext amp switch on in both. 

On snap 1, go into it (Mode button) and then turn off Ext Amp switch, (which in my case changes my amp channel from dirty to clean).

Press mode again to get back to Snaps

Press snap 2 that also has ext amp switch on.  SWITCH DOES NOT WORK). Amp switch is lit like it's on and therefore should switch. But it did not change when I went to that snapshot. Stayed on my clean channel.

 

Channel switching breaks if you go into a snapshot, turn off ext. amp switch, go to another snap with ext amp turned on and it doesn't turn on. Stays in off mode even though lit.    

 

This used to work before 3.50

 

Ugh.

 

Hope you can help! :) 

[rd2rk]

On 3/27/2023 at 8:47 PM, maxm17 said:

This one is killing me.  98% sure it's not a setting.

HXFX running 3.50

Using snapshots.

Create two snapshots with an Ext amp switch on in both. 

On snap 1, go into it (Mode button) and then turn off Ext Amp switch, (which in my case changes my amp channel from dirty to clean).

Press mode again to get back to Snaps

Press snap 2 that also has ext amp switch on.  SWITCH DOES NOT WORK). Amp switch is lit like it's on and therefore should switch. But it did not change when I went to that snapshot. Stayed on my clean channel.

 

Channel switching breaks if you go into a snapshot, turn off ext. amp switch, go to another snap with ext amp turned on and it doesn't turn on. Stays in off mode even though lit.    

 

This used to work before 3.50

 

Ugh.

 

Hope you can help! :) 

 

Attach the actual preset so we can troubleshoot it.

[datacommando]

On 3/28/2023 at 5:26 AM, rd2rk said:

 

Attach the actual preset so we can troubleshoot it.

Hi,

We seem to have a cross post glitch. 

 

This guy had posted the same issue in the main forum, where I mentioned you had asked for an example preset. Guess it’s not a bug until it’s been checked out.

 

He has uploaded the HXFX preset to this thread:

 

Hope you can help him out, as I don’t have access to switchable external amps. (Studio Rat!) ;-)

[maxm17]

On 3/29/2023 at 3:41 AM, datacommando said:

Hi,

We seem to have a cross post glitch. 

 

This guy had posted the same issue in the main forum, where I mentioned you had asked for an example preset. Guess it’s not a bug until it’s been checked out.

 

He has uploaded the HXFX preset to this thread:

 

Hope you can help him out, as I don’t have access to switchable external amps. (Studio Rat!) ;-)

 

I am the person who posted both. Grateful for any insights here. I have a feeling it's a bug, however. :( 

[jiml6]

On 3/17/2023 at 2:56 AM, bbehrens said:

I think that I have found a bug in Helix 3.5 New Cabinet Models. I thought that I liked the sound of a Dual Cab (1x12 Grammatico with the 2x15 Brute Bas Cabinet) with the US Double Nrm Amp Model. I found two issues: 1) It crashed Helix Native in Reaper and I suspect other DAWs as well.

Can you attach the preset that's crashing your DAW? Also, are you using Mac or Windows? AU or VST plugin? Thanks!

[jiml6]

On 3/26/2023 at 3:10 PM, johnbeamon said:

From the 3.50 Release Notes under "Bug Fixes in 3.50".

 

• When assigning block bypass to an expression pedal, Behavior > "Heel Down" or "Toe Down" could sometimes revert to "Toggle"—FIXED

 

This is not fixed. I have a block of presets in which I try to use this feature, because an auto-return/switchless wah is great. I powered on my unit yesterday, found all these Toe Down settings reverted back to Heel Down. I corrected them all, saved them, and found some of them changed AGAIN on second inspection. I corrected and saved them, rebooted the unit. They came up reset to Heel Down. I corrected and saved all of them. Copied them to a new set of Preset slots. Every one of them changed from my Toe Down spec to Heel Down between my fixing them and my pasting them into new slots.

 

This is NOT fixed. It's a valuable feature that I really want to use. But I'm having to pack an external switchless wah to manage a feature Line 6 says was fixed. Where's the QC in this bug report?

Hey John,

 

I'm not able to repro this on Helix Floor. Which Helix device are you using? If you'd like to send over one of the problematic presets I'd be happy to take a closer look at it. Thanks!

[acousticglue]

Oddly, and I thought this was new cheaper guitar causing this (the pickups) but when I have Helix off sometimes at night and cut on, sound is darker, making pickups sound muffled, when switch preset is fine, when go back to last preset booted to is fine. I dont get this. But when I cut unit off again and went back to same preset was fine.

[rd2rk]

On 4/16/2023 at 10:45 AM, acousticglue said:

Oddly, and I thought this was new cheaper guitar causing this (the pickups) but when I have Helix off sometimes at night and cut on, sound is darker, making pickups sound muffled, when switch preset is fine, when go back to last preset booted to is fine. I dont get this. But when I cut unit off again and went back to same preset was fine.

 

I'm not quite sure what you're talking about, but as it sounds like random weirdness I'm going to suggest a Factory Reset:

 

 

[acousticglue]

Thanks if I think or hear it happens again I will reset it

[theElevators]

On 3/26/2023 at 6:10 PM, johnbeamon said:

From the 3.50 Release Notes under "Bug Fixes in 3.50".

 

• When assigning block bypass to an expression pedal, Behavior > "Heel Down" or "Toe Down" could sometimes revert to "Toggle"—FIXED

 

This is not fixed. I have a block of presets in which I try to use this feature, because an auto-return/switchless wah is great. I powered on my unit yesterday, found all these Toe Down settings reverted back to Heel Down. I corrected them all, saved them, and found some of them changed AGAIN on second inspection. I corrected and saved them, rebooted the unit. They came up reset to Heel Down. I corrected and saved all of them. Copied them to a new set of Preset slots. Every one of them changed from my Toe Down spec to Heel Down between my fixing them and my pasting them into new slots.

 

This is NOT fixed. It's a valuable feature that I really want to use. But I'm having to pack an external switchless wah to manage a feature Line 6 says was fixed. Where's the QC in this bug report?

I knew it!  Thanks for the tip. 

 

This is exactly why I don't upgrade from 3.11. 

 

For me the bypass functionality based on percentage works great.  Ain't broke, no need to fix it. 

 

So, wah block is off in the preset; it turns on when EXP 2 is past 5%.  Lower than 5% it gets turned off.  If I don't want to use the wah in a certain snapshot, I set the mix parameter to 0% -- done.  Forget about this utterly useless "Heel Down" behavior. Line 6 really really over-complicated this. 

[theElevators]

On 4/14/2023 at 6:47 PM, jiml6 said:

Hey John,

 

I'm not able to repro this on Helix Floor. Which Helix device are you using? If you'd like to send over one of the problematic presets I'd be happy to take a closer look at it. Thanks!

I was seeing a bug that was ultimately caused by HX Edit running on a Mac on with Helix Firmware 3.15  In reality, altering one preset would apply the same (unrelated) changes to a different preset.  Nobody could replicate this bug on Windows.  It was literally altering unrelated presets.  And you wouldn't know if you broke a preset until you tested all your numerous presets. 

 

Staying on 3.11  thank you verrrrry much. 

[acousticglue]

Also for whatever reason the Template "two Tones A+B" when used for me the volume assign doesnt work for main pedal on Lite. I copy the template to presets User area and still no but the Pete Thorn preset does work

[datacommando]

On 4/17/2023 at 11:38 AM, acousticglue said:

Also for whatever reason the Template "two Tones A+B" when used for me the volume assign doesnt work for main pedal on Lite. I copy the template to presets User area and still no but the Pete Thorn preset does work

As mentioned by @rd2rk in reply to your earlier post - when weird stuff happens, perform a factory reset.

 

What you’re describing seems like general glitches, rather than bug specific. If these 2 different issues were actual bugs, we should expect more reports. 

 

Have you done a Factory Reset?

 

If you have, then provide more information regarding these problems, for example - your hardware device, your computer and OS, also are these issues repeatable after every restart, and/or do they still persist after a Factory Reset.

 

Your previous posts are a little too vague.

 

Hope this helps/makes sense.

 

EDIT: Update 1 hour later.

 

I have just fired up my Helix Floor and  checked the preset Template file 02C TwoTones A-B, and the Volume Block works as expected.

 

Regarding the Factory Preset 22B Pete Thorn Duo - If you check the Volume Pedal Block it has white square brackets surrounding the position parameter, which indicates it is controlled by a Snapshot. SS1 is Tone A, and SS2 is Tone B. My guess is the Preset 22B Pete Thorn Duo is just a modified version of the Template file. Unsurprisingly, that's exactly what Template files are for. Copy one into an empty slot and chop and change to suit your own requirements.
 

I don't think this is a bug.

Edited April 17, 2023 by datacommando
Added Update

[rd2rk]

@bbehrens - any word from L6 on that cab bug?

[jiml6]

@rd2rk @bbehrens 3.60 just dropped. Your issue was addressed in this build. 

[pauloportella]

Hi, I have a HX Stomp LX and I was able to update to the 3.6 firmware but after performing a factory reset I can't see the new presets with the Grammatico amp. I am holding C + D when powering up, and I can see on display the message that is reseting the factory presets, but nothing changes. 13B still has DIR: VH JumpJS. 

[jiml6]

On 4/25/2023 at 11:42 AM, pauloportella said:

Hi, I have a HX Stomp LX and I was able to update to the 3.6 firmware but after performing a factory reset I can't see the new presets with the Grammatico amp. I am holding C + D when powering up, and I can see on display the message that is reseting the factory presets, but nothing changes. 13B still has DIR: VH JumpJS. 

The factory presets with the Grammatico GSG are 15B and 15C. Let me know if you're still not seeing them and I'll be happy to help you troubleshoot. 

[pauloportella]

On 4/25/2023 at 8:25 PM, jiml6 said:

The factory presets with the Grammatico GSG are 15B and 15C. Let me know if you're still not seeing them and I'll be happy to help you troubleshoot. 

 

Thanks so much I can see them now, I was following the release notes. 
 

[johnbeamon]

On 4/14/2023 at 6:47 PM, jiml6 said:

Hey John,

 

I'm not able to repro this on Helix Floor. Which Helix device are you using? If you'd like to send over one of the problematic presets I'd be happy to take a closer look at it. Thanks!

It's all my presets, dozens of them in multiple setlists on two different Floor devices. I can add a Wah block to any Factory Preset, set it to Toe Down and 95%, and save it. It works while I'm on it. The Wah engages when EXP1 is on AND I'm cycling up and down the pedal range. I copy the preset, paste it into a new slot, and Toe Down will change to something else. It's reproducible. It's not a preset; it's all presets where I try to use this feature. As soon as I paste them, move them, or import them (which I do weekly between two devices), this bug appears. See the video. I've submitted the full version to Line 6, but this is a clip that shows a copy-paste action changing that setting.

[H3R3T1K]

Hi guys. I have a weird issue after the current update where some factory presets don't output audio. Not the 4CM preset issue. I'm running headphones right now. Also the bass cab blocks block audio from passing further down the chain. Bummer because I play bass. The legacy cabs work. Very weird.

 

This is after updating to 3.6 which gave me an error. Presumably because I had the Stomp connected to my MacBook via a hub because I don't have USB-A. Anyways after restarting it showed 3.6 installed on the Stomp. After discovering the issues I have done 2 factory resets to no avail.

[jiml6]

On 4/26/2023 at 11:58 AM, H3R3T1K said:

Hi guys. I have a weird issue after the current update where some factory presets don't output audio. Not the 4CM preset issue. I'm running headphones right now. Also the bass cab blocks block audio from passing further down the chain. Bummer because I play bass. The legacy cabs work. Very weird.

 

This is after updating to 3.6 which gave me an error. Presumably because I had the Stomp connected to my MacBook via a hub because I don't have USB-A. Anyways after restarting it showed 3.6 installed on the Stomp. After discovering the issues I have done 2 factory resets to no avail.

Which factory presets aren't passing audio? Also, is there any particular bass cab that is blocking audio, or is it all of them? Thanks! 

[UFODeathCult]

I've discovered a bug on the new bass cabs in the 3.6 update.

 

On the Epifani 1x12, the available microphones are the guitar mic selection, not the bass mics.

 

On the Ampeg 4x10 Pro, the available mics are also the guitar mics, but the image in HX Edit is for the bass mic selection.

 

It's a small error, but it makes it impossible to know what mic I'm actually using on these two bass cabs. A fix would be most welcome. Thanks!

 

This is on a Mac Mini, OS 10.15.7.

 

[jiml6]

On 4/26/2023 at 7:24 PM, UFODeathCult said:

I've discovered a bug on the new bass cabs in the 3.6 update.

 

On the Epifani 1x12, the available microphones are the guitar mic selection, not the bass mics.

 

On the Ampeg 4x10 Pro, the available mics are also the guitar mics, but the image in HX Edit is for the bass mic selection.

 

It's a small error, but it makes it impossible to know what mic I'm actually using on these two bass cabs. A fix would be most welcome. Thanks!

 

This is on a Mac Mini, OS 10.15.7.

 

Great find. It has been logged. Thanks!