Helix Bug Reports

[otnooishphoo]

11 hours ago, PeterHamm said:

Latest firmware? I haven't seen this. Which models may I ask?

 

I just updated to 2.82 it seems to be elephant man for sure, its 1/8 note for 1/1 1/2/ 1/4 1/8 and then it starts working correctly as you get smaller.  Then you hit the dot/trip in between its the same one for each until you  pass the 1/8th setting as well.. very weird.

i'll make a video of it today when i get a chance.

 

 

 

[PeterHamm]

11 minutes ago, otnooishphoo said:

 

I just updated to 2.82 it seems to be elephant man for sure, its 1/8 note for 1/1 1/2/ 1/4 1/8 and then it starts working correctly as you get smaller.  Then you hit the dot/trip in between its the same one for each until you  pass the 1/8th setting as well.. very weird.

i'll make a video of it today when i get a chance.

 

 

 

Not a bug. a feature... I'll explain.

The elephant man delay won't do longer delays,  just like the original. So when you try and tap a longer delay, it goes to some fraction (1/2 or 1/4 depending) of the note value that it can handle.

If you want the elephant man delay sound, but with longer delay times, you can do what I do, which is use the Adriatic delay.

[otnooishphoo]

Hmm, that weird i seem to remember it working before...

there are a couple other that did the same thing, i suppose thats just a feature too?

 

ohwell.

 

time for a timeline I guess.

 

 

why can it do the slower dot/trip ones in between? its 1/8 is the limit?

 

just curious..

 

also wish the delays all had a way to force into repeat, like a strymon where you can hold the bypass down and it will go forever.

 

[PeterHamm]

9 minutes ago, otnooishphoo said:

Hmm, that weird i seem to remember it working before...

there are a couple other that did the same thing, i suppose thats just a feature too?

 

ohwell.

 

time for a timeline I guess.

 

 

why can it do the slower dot/trip ones in between? its 1/8 is the limit?

 

just curious..

 

also wish the delays all had a way to force into repeat, like a strymon where you can hold the bypass down and it will go forever.

 

Well, in the case of elephant man, I think the Adriatic can be set to nail it, so it doesn't matter. I use Adriatic.

They made the models behave exactly like the original pedals, limitations and all. That's why it can't do the slower delays.

[otnooishphoo]

Ohwell.  I'll make do... i just thought for sure that it was doing 1/4 at one point...

 

[HonestOpinion]

On 2/4/2020 at 11:00 PM, MatthewMcGhee said:

This has happened to me as well for months now. They just tell you to do a global reset but that still doesn’t solve the problem. Mine completely locked up the other day. I had to do a power cycle. I’m on the newest firmware and did a complete reset a few weeks ago. 

 

It's possible you have one or more corrupted presets. I would take note of which preset(s) are involved when this happens to see if that is the issue although it could be something else.

[michalaase]

Anyone at all has a stable, bugfree experience of 2.82 ?

Numerous issues has been «reported» here since august-september last year, but all I see from Line 6 is «Do a clean install» or «You must have bugs in your presets».
I've tried the «clean install» option about 8 times now - and it still has issues - even with only factory presets. … And yes, I followed the instructions, point-by-point, every time!
About my own presets ... they all work fine in 2.71 without issues at all, so why do they crash under 2.82 ??

Just wondering why Line6 take so long adressing these issues.

[PeterHamm]

3 hours ago, michalaase said:

Anyone at all has a stable, bugfree experience of 2.82 ?

Numerous issues has been «reported» here since august-september last year, but all I see from Line 6 is «Do a clean install» or «You must have bugs in your presets».
I've tried the «clean install» option about 8 times now - and it still has issues - even with only factory presets. … And yes, I followed the instructions, point-by-point, every time!
About my own presets ... they all work fine in 2.71 without issues at all, so why do they crash under 2.82 ??

Just wondering why Line6 take so long adressing these issues.

My experience actually has been bug free (except beta builds of course). And that's a surprise because my presets are pretty intense and complicated.

[phil_m]

9 hours ago, michalaase said:

Anyone at all has a stable, bugfree experience of 2.82 ?

Numerous issues has been «reported» here since august-september last year, but all I see from Line 6 is «Do a clean install» or «You must have bugs in your presets».
I've tried the «clean install» option about 8 times now - and it still has issues - even with only factory presets. … And yes, I followed the instructions, point-by-point, every time!
About my own presets ... they all work fine in 2.71 without issues at all, so why do they crash under 2.82 ??

Just wondering why Line6 take so long adressing these issues.

 

I can't say it's been completely bug free as I still encounter the occasional bug now and then. All of those have been really minor, though. I've been using 2.82 since whenever it first was released, and I've not had any real issues. I have presets that I've used going back to the very earliest firmware versions. I really couldn't say why you're having issues with your presets.

[HonestOpinion]

12 hours ago, michalaase said:

Anyone at all has a stable, bugfree experience of 2.82 ?

Numerous issues has been «reported» here since august-september last year, but all I see from Line 6 is «Do a clean install» or «You must have bugs in your presets».
I've tried the «clean install» option about 8 times now - and it still has issues - even with only factory presets. … And yes, I followed the instructions, point-by-point, every time!
About my own presets ... they all work fine in 2.71 without issues at all, so why do they crash under 2.82 ??

Just wondering why Line6 take so long adressing these issues.

 

My experience with 2.82 has been relatively bug-free(although I would be shocked if there weren't a few in there, outside of those already listed by Line6) but depending on your usage, and the presets you have retained through your various upgrades, your experience may be different.

 

Regarding your problems with the factory presets, have you upgraded to the latest factory presets?  As you are probably aware this requires the extra step of doing a global reset as detailed in the firmware upgrade notes.

 

The enormous number of parameters, different blocks, routing, loops, IRs, MIDI, CV control, etc make the possible permutations for presets and snapshots very extensive. Whenever a product like this goes through firmware upgrades there is always the possibility that certain combinations possible in a preset have not been accounted for properly in the upgrade process. If this were the case and I am not saying it is, this is strictly guesswork, it is possible that you may have some presets, or even a subset of presets if you were creating them from a template, that don't play well with the new firmware. There is also as always with a computer the possibility that some presets or even an entire setlist got corrupted. 

 

I would also say that until we stop seeing presets rebuilt upon the next restart after they are imported or even just copied from another location it is probably a best practice to restart your device and let them rebuild before editing them. Very inconvenient! This could just be a clerical problem with the firmware not setting a flag properly when a preset is copied/imported or it could be that the preset actually needs to be rebuilt with a device restart before editing. I have yet to see Line6 provide any guidance on this although it has been occurring for years now.

 

Finally there is the possibility that you have some other firmware, hardware, or even stable power issue on your particular device causing lockups.

[Splitcathode]

Snapshots Changing Value In HX Edit. Helix LT 2.82...  Over the last couple of firmware revisions I have experienced mainly amp block snapshot values changing, not during performance but during creation in HX Edit. I could never find a cause and I hit save after nearly every parameter change during creation, did not seem to help. But in 2.82 it seems worse. Today I copied a Gray Flanger block from another preset that already contained snapshots attached to 3 of the parameters and pasted it into another preset I was creating. It seems it corrupted every block in the recipient preset that already contained snapshot controlled parameter. I sometimes use several snapshots per block so it was a mess and a lot of work to be redone.

[pipertalks]

I'm having a frustrating issue with the helix command center sending program changes to my Voicelive. For each patch on the helix I have a different preset loaded on the VoiceLive. I don't want this to change between snapshots. The duplicate PC send is OFF. However, when I switch between snapshot 1 and any other snapshot (not between the others - eg. snapshot 2 to 3 doesn't do this) it still resends the program change telling the voicelive which preset to be on. I wouldn't mind this normally however the voicelive cuts the guitar for a split second while itresets the preset. Not something I want in a live setting as I switch snapshots frequently during songs. If anyone has had this happen I'd like to know if there's a solution. I had this issue on 2.8 and its still present in 2.82. Would rather not downgrade further and lose the Revv amp which I use a lot. Thanks!

[PANDAPANDELO]

I got a HX Stomp from Amazon, and it works sometimes, then it stops. Not the Stomp, itself (everything seems to work, it don't freezes or shuts down), but the signal stops. Its dead quiet. It even the Tuner don't detect anything. Everything is plugged right, and everything is updated.

 

It's a brand new unit (as far as I know), that I got from Amazon... but I'm from Brazil! I asked my mother in law to bring it to me from the US, in a little vacation she had over there. And now I'm really frustrated, because I could create a preset (and it made my acoustic guitar sounds like heaven), then it stopped. It's intermittent. Sometimes it's ok, then it don't. Hahahahha.

 

I have already used that stuff of turn it on holding the buttons 2 and 3, the 1, 2 and 3... everything that I see online.

 

Other thing that I noticed is that the Stomp, when it stops working, makes even the videos I'm watching in youtube freezes! That's crazy! But it only happens when it is plugged in the USB por of my macbook air. The problem happens with or without the USB connection.

 

Do you guys know what could it be? I've created a ticket, and I'm waiting to the Line 6 folks to answer me. I'm scared of the unit be damaged, in someway, and I have to send it to the USA to have a new one... this process would take me about 3 months (1 to go, and 2 to come a new one, if I'm lucky).

 

And sorry if this is not the right place to talk about this. I'm new in the forum, and I'm kind of lost. Sorry for my bad english, too! 

[phil_m]

26 minutes ago, PANDAPANDELO said:

I got a HX Stomp from Amazon, and it works sometimes, then it stops. Not the Stomp, itself (everything seems to work, it don't freezes or shuts down), but the signal stops. Its dead quiet. It even the Tuner don't detect anything. Everything is plugged right, and everything is updated.

 

It's a brand new unit (as far as I know), that I got from Amazon... but I'm from Brazil! I asked my mother in law to bring it to me from the US, in a little vacation she had over there. And now I'm really frustrated, because I could create a preset (and it made my acoustic guitar sounds like heaven), then it stopped. It's intermittent. Sometimes it's ok, then it don't. Hahahahha.

 

I have already used that stuff of turn it on holding the buttons 2 and 3, the 1, 2 and 3... everything that I see online.

 

Other thing that I noticed is that the Stomp, when it stops working, makes even the videos I'm watching in youtube freezes! That's crazy! But it only happens when it is plugged in the USB por of my macbook air. The problem happens with or without the USB connection.

 

Do you guys know what could it be? I've created a ticket, and I'm waiting to the Line 6 folks to answer me. I'm scared of the unit be damaged, in someway, and I have to send it to the USA to have a new one... this process would take me about 3 months (1 to go, and 2 to come a new one, if I'm lucky).

 

And sorry if this is not the right place to talk about this. I'm new in the forum, and I'm kind of lost. Sorry for my bad english, too! 

 

Is it running the latest firmware? Even it is, I would try re-installing it if you haven't.

[PANDAPANDELO]

4 hours ago, phil_m said:

 

Is it running the latest firmware? Even it is, I would try re-installing it if you haven't.

Yes! It is the latest firmware. I will try to reinstall everything tonight. Thank you, Phil!

[flop54]

hello,

 

Despite the 2.82 firmware, i continue to have the same bug.

 

Sometimes the helix don't send midi clock. I have to return to the global parameters and change the parameter (because it is set correctly) and set with the good parameter again and it works again.

[burningyen]

Hey guys, just found out about this thread. Sorry if these are repeats, but I ran into these bugs after updating from 2.71 to 2.82:

 

1) In synth blocks, my attack and decay settings were lost and defaulted to longer than I originally programmed them.

2) In synth blocks, footswitches that I programmed to be momentary became latching.

3) In synth blocks, after I correct the footswitch assignments back to momentary, sometimes when I press one programmed to momentarily turn synth blocks on, the bypass states of the blocks invert, so instead of normally off they become normally on.

4) The update erased my Variax settings.

5) When I try to enter a stomp assignment to toggle between 2 different Variax models, on the Helix screen the little parameter indicator bars move as expected as I turn the knobs, but the model names listed above those bars aren't correct and the two names often appear stuck on the same model name even though the indicator bars show that two different models are selected. I have the Helix connected to my Macbook running both HX Edit and Workbench HD. Everything is updated to the latest version.

[pinetrax]

Yes, i had the same problem with the variax models not displaying correctly, on top of that, i want the 2 different guitars to have different settings for the tone knob, i set it to force the tone knob to different positions, but it doesn’t change the tone knob settings at all.

[jbuhajla]

Floor model running 2.82 running 10 stomp mode. Foot switch 10 was assigned to change four different amp parameters. Foot switch 9 was blank. Used the capacitive touch on 9 and 10 simultaneously to switch positions. When I hit OK screen goes blank, screen backlight still on, unit is completely frozen but still outputting sound when I play. Had to cycle power to get back to where I was. Tried to swap 9 and 10 again, locked up. It was repeatable every time. 
 

I had to go in and manually set foot switch 9 on each of the 4 amp parameters to move them to FS9. 

[thedoctormo]

Regarding the bug related to corrupted presets when importing them, I think I found something reproducible.

 

I exported 100+ presets from the Helix.  Then, I imported the same 100+ presets into a different set list on the Helix.  There were several presets that had corrupt preset names.

 

To reset the situation, I copied a bunch of 'New Preset' presets and pasted over all the 100+ presets I just imported.

 

Then, I imported about 20 presets at a time.  By reducing the number of presets during an import operation, I was able to import without any issues.

 

It appears the issue may be related to the number of presets being imported within a single operation.

 

I hope this is useful.

mike

[UndeadKernel]

There is a memory corruption bug that has to do with changing preset configurations (including loading a preset).

I have seen the same problem of presets having corrupted names after just editing the colors of the Snapshot footswitches of a preset.

 

[Magnus-Pleshardt]

Hey

I have this problem with my HX effects where the function that lets you look at all parameters to an effect all at once (done by touching the given effect button for 1 sec) keeps popping up. This is happening without me holdning my finger on it at all. It sucks, because when im just in stomp mode, where i can turn on my effects, it just keeps going to that one effect's parameters so that I can't turn on the other effects and I have to press mode to get back to them. This often happens continuously, where it just keeps popping up.  

Anyone got an solution to this problem?

[ukurum]

Hi all,

 

I do not know if a HX Edit bug count as a "Helix Bug" but here it is; if your mouse primary button is set as right (for left handed like me) you can not interact with (drag) the block to create a parallel path. While I agree that this is a left handed first world problem, please fix it, is so annoying to be forced to change the mouse setting every single time.

 

Cheers,

Ulas

[piererequiem]

Hallo guys

I have HELIX LT and I have updated Firmware from 2.2.1 to 2.8.2. 

Now I have problem,   all of my created sounds have after upgrade lower gain

Can you help me with this problem please?

 

Piere

[phil_m]

2 hours ago, piererequiem said:

Hallo guys

I have HELIX LT and I have updated Firmware from 2.2.1 to 2.8.2. 

Now I have problem,   all of my created sounds have after upgrade lower gain

Can you help me with this problem please?

 

Piere

 

Did you create a backup and restore from backup after doing the upgrade?

 

If you didn't the Global Settings will reset to their default settings, so it could be something related to that. There really shouldn't be any changes in the sound of anything when you update.

[jbuhajla]

On 2/4/2020 at 9:48 PM, otnooishphoo said:

Tempo Sync Delays are broken on multiple delay models.  1/1 1/2 1/4  etc are ALL always 8th notes.

 

 

some delay models have a max delay time of around 350-400ms, no mater what tempo you tap. 

[terpdude]

I can't get HX Edit 2.82 to open. When I run the program, it opens with what looks like a capture of my desktop with the menu bar at the top. If I try to select anything in the menu, it closes. I've updated everything, I have the latest drivers for my video card. I submitted a ticket to support, but they couldn't figure it out. This is really frustrating. 

 

Windows 10 64 Bit

8GB RAM

Intel i7

NVIDIA GTX 960

[richardantonelli]

Tried searching for this but didn't find anything here...unless I'm searching incorrectly.

 

I just got my THIRD helix...used off of reverb. It's on 2.82. Being familiar with it, I started building my presets to use 4 cable method, as I had in the past too. However, the looper is not working correctly.

 

No matter where I place it in the chain, as soon as I hit record, I lose all volume from the snapshot I'm on. I can slightly hear sound when playing but it's VERY minimal. Playback is the same after recording. In order to get sound back, I have to go to a different snapshot and then back into the original snapshot and remove the looper. This does not seem to happen in presets where I would use a Helix amp and cab or IR (I use this as my direct or backup rig) but I mainly use 4CM for most applications.

 

Has anyone else had this issue? I've tried reinstalling 2.82 so far with no luck. This morning, I'm going to do a complete factory reset on everything (after backing up my work) and hope that will do the trick. I wanted to post this here in case others are having this issue. I did open a support ticket but I'm not expecting a response soon as I know the team is running on low capacity right now.

 

UPDATE: OK, this seems to be midi related. I'm using a Synergy Syn-2. I have the helix changing channels via midi. Whenever I engage the looper, it's sending a command to the Syn to change the channel to bypass. I'm still trying to figure out how to control that with the looper. Any ideas?

[phil_m]

5 hours ago, richardantonelli said:

Tried searching for this but didn't find anything here...unless I'm searching incorrectly.

 

I just got my THIRD helix...used off of reverb. It's on 2.82. Being familiar with it, I started building my presets to use 4 cable method, as I had in the past too. However, the looper is not working correctly.

 

No matter where I place it in the chain, as soon as I hit record, I lose all volume from the snapshot I'm on. I can slightly hear sound when playing but it's VERY minimal. Playback is the same after recording. In order to get sound back, I have to go to a different snapshot and then back into the original snapshot and remove the looper. This does not seem to happen in presets where I would use a Helix amp and cab or IR (I use this as my direct or backup rig) but I mainly use 4CM for most applications.

 

Has anyone else had this issue? I've tried reinstalling 2.82 so far with no luck. This morning, I'm going to do a complete factory reset on everything (after backing up my work) and hope that will do the trick. I wanted to post this here in case others are having this issue. I did open a support ticket but I'm not expecting a response soon as I know the team is running on low capacity right now.

 

UPDATE: OK, this seems to be midi related. I'm using a Synergy Syn-2. I have the helix changing channels via midi. Whenever I engage the looper, it's sending a command to the Syn to change the channel to bypass. I'm still trying to figure out how to control that with the looper. Any ideas?

 

The looper controls send out the MIDI CCs associated with them when you use them. It sounds like the Synergy is responding to those CCs. Try going to Global Settings>MIDI/Tempo and setting the MIDI Base Channel parameter to a different channel. Assuming you're using Instant Commands and/or footswitches to change channels on the Synergy, that setting won't affect those, but it should make it so the looper commands are sent out on a different change than the Synergy is set to.

[Klaim]

Hi
Here are two bugs I saw in the last 48h. My Helix floor was bought new around September, it's under 2.82, I upgraded as soon as I got it.
The main particular common thing is that I let the Helix on the whole day in both cases (about 5-6 hours after using it, I tried to use it again) - before, until few days ago, I always turned it off when not used, on only when used.

Also in all cases, HX Edit was open and the Helix connected to the laptop running it.

 

1. Freeze in the looper: I'm in the looper display, I try to get out but it doesn't respond. None of the switches does. Playing guitar does work. In doubt I turn it off and on and it works again.
Unfortunately I didn't think about checking if the non-switch buttons were working but I did assume so because the unit was still processing sound correctly.

Also note that the laptop have some driver/device issues and sometime bluescreens and that day, it did bluescreen not long before I got locked in the looper display.

2. Suddenly, no more reverb: At lunch time today I recorded a video of me doing a guitar workout with the Helix, then I realized there was some issue with the recorded audio and decided to fix that at night be checking the audio setup. I did just that, started 1h ago. About 20 minutes ago I was using a custom preset and playing when suddenly the reverb went off. I do NOT mean that the reverb block was off, it was ON, but I could hear it suddenly not being there in the audio signal. To fix this one, I just reloaded the same preset and that fixed the issue.
The reverb block in this preset was Ganymede.

Both issues happened while manipulating the same preset but I don't think it's related?

 

I fear that in live situation these issues might appear (I will not be in live before next year so it's not an immediate problem).

Are these problems well known? I couldn't find similar reports so far. Unfortunately these look very hard to reproduce...

Firmware/Editor: Firmware 2.82; HX Edit 2.82
OS: Windows 10
Global Settings: Not sure what to point exactly

[phil_m]

1 hour ago, Klaim said:

2. Suddenly, no more reverb: At lunch time today I recorded a video of me doing a guitar workout with the Helix, then I realized there was some issue with the recorded audio and decided to fix that at night be checking the audio setup. I did just that, started 1h ago. About 20 minutes ago I was using a custom preset and playing when suddenly the reverb went off. I do NOT mean that the reverb block was off, it was ON, but I could hear it suddenly not being there in the audio signal. To fix this one, I just reloaded the same preset and that fixed the issue.
The reverb block in this preset was Ganymede.

 

This is a long-standing bug. If you stay on one preset for a long time, the reverb block(s) will stop working after a few hours. I don't know what the actual time is as I've never tried to measure it, but it seems like it's at least three hours.

[Klaim]

8 hours ago, phil_m said:

 

This is a long-standing bug. If you stay on one preset for a long time, the reverb block(s) will stop working after a few hours. I don't know what the actual time is as I've never tried to measure it, but it seems like it's at least three hours.

 

Thanks, at least knowing that one can easily avoid the issue in live context.

 

Do I understand correctly that this is not announced to be fixed in 2.90?

[jbuhajla]

12 hours ago, phil_m said:

 

This is a long-standing bug. If you stay on one preset for a long time, the reverb block(s) will stop working after a few hours. I don't know what the actual time is as I've never tried to measure it, but it seems like it's at least three hours.

I haven't noticed this one. I leave my Helix on for days at a time and no issues with reverbs not working. Maybe certain reverbs?

[phil_m]

3 hours ago, Klaim said:

 

Thanks, at least knowing that one can easily avoid the issue in live context.

 

Do I understand correctly that this is not announced to be fixed in 2.90?

 

I’m not sure. I haven’t run into in the beta for 2.9 that I can remember, but I haven’t really been explicitly looking for it.

[phil_m]

10 minutes ago, jbuhajla said:

I haven't noticed this one. I leave my Helix on for days at a time and no issues with reverbs not working. Maybe certain reverbs?

 

It may be. I think it’s a particularly elusive bug, so that may explain why they haven’t killed it yet.

[PeterHamm]

I leave mine on for days and days sometimes, too, and haven't had this reverb issue. Not with a release version or beta version of software.

 

[SaschaFranck]

Excuse me for the OT post, but sorry, leaving any kind of electronic device on for days is possibly as bad as it gets in terms of environmental caretaking. Things such as that really don't go well with me at all. Call me an old hippie (I sort of am), but you don't even have to be an old hippie to understand how bad this is.

[Klaim]

2 hours ago, SaschaFranck said:

Excuse me for the OT post, but sorry, leaving any kind of electronic device on for days is possibly as bad as it gets in terms of environmental caretaking. Things such as that really don't go well with me at all. Call me an old hippie (I sort of am), but you don't even have to be an old hippie to understand how bad this is.

 

That can be challenged:

I've worked on console games and it is indeed difficult to make a software that doesn't crash after 48h (it's even harder when it's not on console and not games). But it is possible as it is a hard requirement on consoles.

However, the requirements are not the same than for a musician's tool which is not running on a laptop. For things that are basically live performance hardware, one would expect to be able to spend a full day with the thing on, or at least a big bunch of hours.
(I have a looper pedal that have some random issues like that too, I can't use it for live because of that)
 

And in my specific case, both issues happened after a few hours (less than 5), not after days.

 

[SaschaFranck]

12 hours ago, Klaim said:

 

That can be challenged:

I've worked on console games and it is indeed difficult to make a software that doesn't crash after 48h (it's even harder when it's not on console and not games). But it is possible as it is a hard requirement on consoles.

 

See, I wasn't talking about a testing environment. In any such environment, longtime stress tests are required. But there's no need for a normal user to keep a device such as the Helix switched on for days. It's just a stupid waste of energy.

[PeterHamm]

1 hour ago, SaschaFranck said:

 

See, I wasn't talking about a testing environment. In any such environment, longtime stress tests are required. But there's no need for a normal user to keep a device such as the Helix switched on for days. It's just a stupid waste of energy.

In many studios, they leave their gear on 24/7, because they know that most failures occur on power up and power down.

At home, generally, it's a good idea to turn stuff on, but Helix is not sucking down that much electricity.