Helix Bug Reports

[SaschaFranck]

6 minutes ago, PeterHamm said:

with tap tempo, a few things.

Bare feet confuse the buttons (as do fingers pressing), because of the touch capacitance.
Some models don't have long enough delay times and automatically speed up.
I think TT works best when you are NOT connected to a computer as well.

 

I tried with shoes, the tap tempo switch isn't capacitive anyway, it always worked just fine when connected to a computer and all delays are affected, hence including those with sufficiently long delay times.

 

Edit: Was wrong, the tap tempo switch is capacitive (never noticed before). Yet, as I tried with shoes, it should be no issue.

[MGblade]

14 minutes ago, PeterHamm said:

with tap tempo, a few things.

Bare feet confuse the buttons (as do fingers pressing), because of the touch capacitance.
Some models don't have long enough delay times and automatically speed up.
I think TT works best when you are NOT connected to a computer as well.

definitly a bug, didnt have any problems with 2.82 

when tapping in edit(right top corner) it works but when you tap on helix you can see it go haywire.

[52dmk]

Tap tempo is definitely not working correctly.

If I tap along to a 135bpm metronome the tapped bpm is around 160bpm.

If I set helix bpm manually, it's fine.

[PeterHamm]

7 minutes ago, 52dmk said:

Tap tempo is definitely not working correctly.

If I tap along to a 135bpm metronome the tapped bpm is around 160bpm.

If I set helix bpm manually, it's fine.

Igor just pointed out that this IS a known issue, they are working on it as we speak. I'd expect a pretty quick hot fix.

[pinetrax]

Well, step temple seems to be working for some of you and not for some of you, Maybe the problem is the combination of different amps and affects along with the delays you have, try a new preset with just the delays and see if they don't work

[SaschaFranck]

How could such an obvious thing such as the tap tempo madness slip through in testing?

[52dmk]

9 minutes ago, pinetrax said:

Well, step temple seems to be working for some of you and not for some of you, Maybe the problem is the combination of different amps and affects along with the delays you have, try a new preset with just the delays and see if they don't work

Tried with a blank preset, a single simple delay, problem is still there.

I don't think problem is with delays, as they work fine when manually set, or if you manually set the bpm.

The issue is with the tap tempo being significantly out in its calculated bpm.

[52dmk]

1 minute ago, SaschaFranck said:

How could such an obvious thing such as the tap tempo madness slip through in testing?

One wrong or missing character in code is all it would take.

[Alex_Schcs]

1 hour ago, molul said:

Could you post a video of the problem? To me, it works exactly as in previous version, but I might be overlooking something. Seeing what's happening to the bugged unit might help.

 

Sure, heres is a link with some videos (they are too big to add with the coment)

https://drive.google.com/open?id=18Oul94Rjd1oyLJRgM4CPCLrJkJJtJSLY

[SaschaFranck]

22 minutes ago, 52dmk said:

One wrong or missing character in code is all it would take.

 

Well, sure - but that's why you test carefully before release.

[ppoceiro]

Hi people!
So there's a bug with the tap tempo and delays in the 2.90 update. And probably a few others.

That's quite unfortunate of course but it's L6!

They are aware of it. They are fixing it as fast as they can and given the current conditions we are all in I think they deserve some appreciation on their hard work.
Yes in normal conditions it's that kind of bug that affects many users but I'm very happy they could release this update with very nice implementations and new effects and a new amp for me to play with in these difficult times.

I don't bother if this or other bug somehow slipped through the beta testing. My Helix didn't blow up so all is fine!
And by the way this update was one of the smoothest so far for me.
So thank you L6 and all the beta testers for your work and stay safe!
You deserve some love from all of us!!
And stay safe everybody. Go ahead and obsess with the new meters!
Cheers

 

[MGblade]

I went back to 2.82 for now.

it's great to hear they are fixing it as we speak.

no complaints here 

[molul]

1 hour ago, Alex_Schcs said:

 

Sure, heres is a link with some videos (they are too big to add with the coment)

https://drive.google.com/open?id=18Oul94Rjd1oyLJRgM4CPCLrJkJJtJSLY

Wow, it looks really bad. If I were you, I'd contact Line 6 as soon as possible.

[PeterHamm]

I actually reported tap tempo issues during beta testing, but they were erratic, and for some reason in the most recent build seem to work fine here for me.

I have had issues with bare feet, and with tap tempo while connected to the computer, but in normal play, right now, seems to be working fine.

They are on it.

[molul]

1 hour ago, SaschaFranck said:

 

Well, sure - but that's why you test carefully before release.

They might have tested it, and had no problems like other users (I mean, I think my tap tempo works as always, but I haven't seen a video showing the problem, so I might have the issue but I haven't noticed).

[Alex_Schcs]

7 minutes ago, molul said:

Wow, it looks really bad. If I were you, I'd contact Line 6 as soon as possible.

 

Yep, i will do that, were i supposed to do it? 

 

PD. Thank for the attention bro.

[chasingMango]

5 minutes ago, Alex_Schcs said:

Yep, i will do that, were i supposed to do it? 

https://line6.com/support/tickets/add.html

[Alex_Schcs]

13 minutes ago, chasingMango said:

https://line6.com/support/tickets/add.html

 

Thanks!

[Trl0126]

I just attempted to do the 2.9 firmware update.  I am doing the update through Mac Catalina.  I didn't see the note on updating through the Helix Editor software so I tried to update through the updater.  As the update was loading my computer went into sleep mode.  I received instructions to reboot my Helix and try to start the update again.  When I turn my Helix off then on again it got stuck on the boot screen below and I cant for the life of me figure out how to get the computer and Helix to communicate with each other again. Any suggestions? Because I am using a 2019 Macbook Air all I have is Thunderbolt 3 connections so I have to connect the Helix through a hub.  I have been able to connect the Helix with Helix Edit via the hub previously so this would not appear to be the issue.

 

 

[ashtonlouie]

15 hours ago, Alex_Schcs said:

Hi guys, i have Helix LT, when i use an empty preset all works fine and smooth, but when i use an existing preset all works slowly and with a lot of retard using the tuner, the meters, traveling into the menus... I dont know if its a bug or something, but i dont know how to fix that because its so hard to work like that. Using the tuner is crazy, it needs like 2 or 3 seconds to show the note that you played (applicable to the meters too)

Tuner is broken. Ever since I updated I'm having the same crazy delay of note recognition on the tuner. What I've noticed is that if I leave the tuner open for 10-20 seconds it goes back to normal and is usable (thank god). Still very annoying though.

 

EDIT: Just confirmed my tap tempo is borked too. I'll tap it, it'll flash (too slow) for a couple seconds, then start flashing (too fast) from then onwards.

[Alex_Schcs]

13 minutes ago, ashtonlouie said:

Tuner is broken. Ever since I updated I'm having the same crazy delay of note recognition on the tuner. What I've noticed is that if I leave the tuner open for 10-20 seconds it goes back to normal and is usable (thank god). Still very annoying though.

 I never had issues with the tuner until now, but it looks like a problem with the implementation of the meters because both of the have the same issue, it takes like 3 secons to show the signal that the helix recives.

 

Here i uploaded some videos where you can see what happens: https://drive.google.com/open?id=18Oul94Rjd1oyLJRgM4CPCLrJkJJtJSLY

[molul]

36 minutes ago, Trl0126 said:

I just attempted to do the 2.9 firmware update.  I am doing the update through Mac Catalina.  I didn't see the note on updating through the Helix Editor software so I tried to update through the updater.  As the update was loading my computer went into sleep mode.  I received instructions to reboot my Helix and try to start the update again.  When I turn my Helix off then on again it got stuck on the boot screen below and I cant for the life of me figure out how to get the computer and Helix to communicate with each other again. Any suggestions? Because I am using a 2019 Macbook Air all I have is Thunderbolt 3 connections so I have to connect the Helix through a hub.  I have been able to connect the Helix with Helix Edit via the hub previously so this would not appear to be the issue.

 

 

Does your Helix boot? Anyway, I'd try doing a factory reset and then try to connect again.

[Ovationdave]

IR's Not Working......

I turned in a support ticket because I am not able to load any IR's. I have one IR (that appeared blank) in slot #1 (that I can NOT seem to clear), the rest will not work at all. If I grab 10 IR's and do an import, it will start loading them, fill in the names for each IR slot, then at the very end it flashes a message in HX edit and all of them return to the < EMPTY >. Very frustrating!

 

I reloaded 2.82, all import/export/copy/clear works fine with all IR slots when importing single or multiple IR's.

 

So, unfortunately I went back to 2.9 again, same issue. If I assign the empty IR to a block, I am unable to delete it without the error in the image below, but if I "Clear all Blocks", then "Undo", I am able to delete the IR block. Go figure.....

 

UPDATE. Turns out it was user error, as somehow I did not have HX Edit updated, and was still running 2.8. Once corrected the IR's upload worked fine.

 

As embarrassing as that is, I left it in case someone runs into a similar issue.

 

 

[SaschaFranck]

1 hour ago, molul said:

They might have tested it, and had no problems like other users (I mean, I think my tap tempo works as always, but I haven't seen a video showing the problem, so I might have the issue but I haven't noticed).

 

Come on, it has already been kinda officially acknowledged, how are they doing that in case none of their testing units suffered from it?

[molul]

5 minutes ago, SaschaFranck said:

 

Come on, it has already been kinda officially acknowledged, how are they doing that in case none of their testing units suffered from it?

As a developer, it's easy to explain: they received bug reports, checked what settings the problematic units had, and found a testing case that reproduced the problem, that wasn't taken into consideration in their QA department so far. 

It happens more usually than you might think, and everywhere, especially in complex software with so many possible combinations of either modules or settings.

[PeterHamm]

QUESTION FOR YOU GUYS WITH THE TUNER!

What unit? What input are you using?

Reason I ask is that I have had NO problems with the tuner in any of the 2.9 betas (and of course not the final release either). 

Love to help if I can.

[PeterHamm]

33 minutes ago, Ovationdave said:

I turned in a support ticket because I am not able to load any IR's. I have one IR (that appeared blank) in slot #1 (that I can NOT seem to clear), the rest will not work at all. If I grab 10 IR's and do an import, it will start loading them, fill in the names for each IR slot, then at the very end it flashes a message in HX edit and all of them return to the < EMPTY >. Very frustrating!

 

The update was fairly smooth, and I was glad to get some new stuff to play with during the lockdown (thanks for that L6), but I may have to go back to 2.8 if I can't get this working. :-(

Is your Helix AND your HX Edit at 2.90? That sounds like you are running an old Edit.

[jotacaster]

I have a problem with the tuner on the HX Stomp.
Was working fine yesterday after the update.
Now I can go to the tuner screen but sound still goes through and no indication of the tuning, no matter the settings.

[Ovationdave]

1 hour ago, PeterHamm said:

Is your Helix AND your HX Edit at 2.90? That sounds like you are running an old Edit.

 

I think your right. I thought it was updated but after checking it appears it was still @ 2.8. I hope it is something this simple. So I am updating again right now. I will let you know.

 

Thanks Peter!

 

Yep, that corrected it. I can't believe I missed that. Just and ID10T error. Thanks again. I will go delete my ticket!

[SaschaFranck]

1 hour ago, molul said:

As a developer, it's easy to explain: they received bug reports, checked what settings the problematic units had, and found a testing case that reproduced the problem, that wasn't taken into consideration in their QA department so far. 

It happens more usually than you might think, and everywhere, especially in complex software with so many possible combinations of either modules or settings.

 

Ok, I usually don't like saying so, but I have around 2 decades of audio software betatesting on my belt. So, I do know there's plenty of chances for software to be released while there's still some bugs (a lot easier to sort them out inside a closed, hardwarebased ecosystem such as the Helix, though, as you have to deal with way less variables). Fine.

But then there's "showstoppers". Bugs that you won't allow to get into the wild. IMHO, the messed up tap tempo functionality absolutely qualifies as a showstopper (in fact, for me it would be if I was playing live - which I only ain't because of C19, otherwise I'd instantly roll back to 2.82). So, how comes 2.9 is released as is, though? Either Line 6 doesn't care. I doubt that. Or they haven't aquired proper betatesting personnel (no idea about those, but I do at least sort of doubt it, too). Or there's simply not enough testers. IMO that's the most likely scenario. I mean, in this thread alone there's several people having tap tempo issues - how comes none of the testers were running into these issues? Because apparently there's not enough of them to cover all likely scenarios.

 

[ociosu]

LT gets frozen if I switch turner on shortly after it has finished boot.

Or

Tuner does not work, if switched on shortly after boot.

 

If I wait about 20 secs before turning on turner, then it seems there is no problem.

[molul]

1 hour ago, SaschaFranck said:

 

Ok, I usually don't like saying so, but I have around 2 decades of audio software betatesting on my belt. So, I do know there's plenty of chances for software to be released while there's still some bugs (a lot easier to sort them out inside a closed, hardwarebased ecosystem such as the Helix, though, as you have to deal with way less variables). Fine.

But then there's "showstoppers". Bugs that you won't allow to get into the wild. IMHO, the messed up tap tempo functionality absolutely qualifies as a showstopper (in fact, for me it would be if I was playing live - which I only ain't because of C19, otherwise I'd instantly roll back to 2.82). So, how comes 2.9 is released as is, though? Either Line 6 doesn't care. I doubt that. Or they haven't aquired proper betatesting personnel (no idea about those, but I do at least sort of doubt it, too). Or there's simply not enough testers. IMO that's the most likely scenario. I mean, in this thread alone there's several people having tap tempo issues - how comes none of the testers were running into these issues? Because apparently there's not enough of them to cover all likely scenarios.

 

That certainly looks like a question that you'll only get answered by asking Line 6 support.

I don't really care. I'm happy with the product and support so far. Releasing an update during this crisis is amazing, and I can bear with normal bugs, moreso if they're handled the very day they're reported. 

Maybe the Helix is not for you and you might be happier with another multieffects unit :)

[PeterHamm]

2 hours ago, SaschaFranck said:

 

Ok, I usually don't like saying so, but I have around 2 decades of audio software betatesting on my belt. So, I do know there's plenty of chances for software to be released while there's still some bugs (a lot easier to sort them out inside a closed, hardwarebased ecosystem such as the Helix, though, as you have to deal with way less variables). Fine.

But then there's "showstoppers". Bugs that you won't allow to get into the wild. IMHO, the messed up tap tempo functionality absolutely qualifies as a showstopper (in fact, for me it would be if I was playing live - which I only ain't because of C19, otherwise I'd instantly roll back to 2.82). So, how comes 2.9 is released as is, though? Either Line 6 doesn't care. I doubt that. Or they haven't aquired proper betatesting personnel (no idea about those, but I do at least sort of doubt it, too). Or there's simply not enough testers. IMO that's the most likely scenario. I mean, in this thread alone there's several people having tap tempo issues - how comes none of the testers were running into these issues? Because apparently there's not enough of them to cover all likely scenarios.

There are enough testers, but apparently most of us didn't have this issue.

For the record, I did, and I did report it.

They will fix it fast.

[Alex_Schcs]

4 hours ago, PeterHamm said:

QUESTION FOR YOU GUYS WITH THE TUNER!

What unit? What input are you using?

Reason I ask is that I have had NO problems with the tuner in any of the 2.9 betas (and of course not the final release either). 

Love to help if I can.

 

I have the Helix LT, i tried ussing multi  and guitar input.

[SaschaFranck]

1 hour ago, molul said:

Maybe the Helix is not for you and you might be happier with another multieffects unit :)

 

Well, I'm pretty happy with the Helix. But I'm obviously not happy with an update breaking an essential feature.

 

23 minutes ago, PeterHamm said:

There are enough testers, but apparently most of us didn't have this issue.

For the record, I did, and I did report it.

They will fix it fast.

 

Seriously, with a bug like that, this shouldn't have been released.

[PeterHamm]

50 minutes ago, SaschaFranck said:

 

Well, I'm pretty happy with the Helix. But I'm obviously not happy with an update breaking an essential feature.

 

 

Seriously, with a bug like that, this shouldn't have been released.

Keep in mind it is not affecting everyone. I think I was the only beta tester who had a problem, and I have a reputation for being super picky and finicky about that particular feature.

[dan5150]

Just updated to 2.90. 

The first issue I am seeing is that I am no longer able to configure my buttons to snap/stomp, actually, I can't the snapshots to display on any of the buttons. :-( 

[bwQuestion]

In relationship to the tap temp.  For what its worth.  Mine is all over the board.  I have a Boss digital metronome, a Roland FA-06 keyboard, an EMU MP7, and the Helix that have tap tempo.  Before the 2.9 update I could use the tap on each one to get everything sync'd with no issues.  After the 2.9 update, the Helix tap is not usable.  A consistent tap of 120bpm will show everywhere between 126 and 136bpm.  A consistent tap of 80bpm shows between 93 and 96.  Its hosed unless you dial it in manually, which means it is no longer usable.

 

I will have to look into downgrading back to 2.82.  Not really a bad thing since I still can not save an edited block, which is not a feature request by the way, it is a deficiency in the software.   That comment was not for the end user, it was hopefully for a Line 6 person to see.

[phil_m]

32 minutes ago, bwQuestion said:

In relationship to the tap temp.  For what its worth.  Mine is all over the board.  I have a Boss digital metronome, a Roland FA-06 keyboard, an EMU MP7, and the Helix that have tap tempo.  Before the 2.9 update I could use the tap on each one to get everything sync'd with no issues.  After the 2.9 update, the Helix tap is not usable.  A consistent tap of 120bpm will show everywhere between 126 and 136bpm.  A consistent tap of 80bpm shows between 93 and 96.  Its hosed unless you dial it in manually, which means it is no longer usable.

 

I will have to look into downgrading back to 2.82.  Not really a bad thing since I still can not save an edited block, which is not a feature request by the way, it is a deficiency in the software.   That comment was not for the end user, it was hopefully for a Line 6 person to see.

 

The tap tempo thing will be address with a hot fix, probably within the next few days.

 

As far as saving a block, what exactly do you mean? There isn't a way to save settings for individual blocks.

[ashtonlouie]

8 hours ago, PeterHamm said:

QUESTION FOR YOU GUYS WITH THE TUNER!

What unit? What input are you using?

Reason I ask is that I have had NO problems with the tuner in any of the 2.9 betas (and of course not the final release either). 

Love to help if I can.

I'm using LT with Multi input.