Helix Bug Reports

[bwQuestion]

42 minutes ago, phil_m said:

There isn't a way to save settings for individual blocks.

 

You got it.  The "block" is what everything in the unit is based on and there is no way to save one to which you have made a change without putting it in a preset and saving the preset.  That is a software deficiency, but it often gets put in the "feature request" category.

[ashtonlouie]

1 hour ago, bwQuestion said:

 

You got it.  The "block" is what everything in the unit is based on and there is no way to save one to which you have made a change without putting it in a preset and saving the preset.  That is a software deficiency, but it often gets put in the "feature request" category.

I was just thinking yesterday it would be really nice to have block presets.

[CurveBound]

With 2.9, I hear a "static click" noise when switching between IRs now.

[qwerty42]

4 hours ago, bwQuestion said:

 

You got it.  The "block" is what everything in the unit is based on and there is no way to save one to which you have made a change without putting it in a preset and saving the preset.  That is a software deficiency, but it often gets put in the "feature request" category.

I don't really agree with your commentary on this, but FYI, V3.0 will have that capability. Pasted from TGP from phil_m: "User model defaults are kind of self-explanatory... If you want to have the default settings for the Litigator be at certain values when you plop it in a preset, you can save the settings you like as the defaults.

The Favorites is kind of adjacent to that, but there will be a new main block category called Favorites where you can save up 120 (was it 120 or 128?) of your favorite block of any type and name them whatever you want. I could create a Favorite called "Phil's Space Echo" using the Cosmos Echo, for instance, and then plop that in whenever I want it. So rather than having to navigate through the menus to find that block, I'd just go to the Favorites menu, select it and move on. So if you wanted to create a preset using your favorite settings, it would be super fast."

[SaschaFranck]

8 hours ago, PeterHamm said:

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.

 

Well, it's clearly broken. Those telling me it's not on their Helixes may feel free to post a video of it working.

[molul]

32 minutes ago, SaschaFranck said:

 

Well, it's clearly broken. Those telling me it's not on their Helixes may feel free to post a video of it working.

As it seems to be a minority problem, it would make more sense that those who say it's undoubtedly broken upload that video, so those who don't have that bug (apparently) can say "oh, yeah, if I do that I'm having the same problem" or "nope, it doesn't happen to me".

 

Honestly, I don't know what to check. As I said, it works exactly the same as before.

[SaschaFranck]

50 minutes ago, molul said:

Honestly, I don't know what to check. As I said, it works exactly the same as before.

 

Tap a tempo, check whether the delay tempo is the same as what you tapped.

[molul]

1 hour ago, SaschaFranck said:

 

Tap a tempo, check whether the delay tempo is the same as what you tapped.

It definitely is. As I said, it works exactly as before 2.90.

[SaschaFranck]

13 minutes ago, molul said:

It definitely is. As I said, it works exactly as before 2.90.

 

Would you do me a favour and record a small video snipplet?

[PeterHamm]

The tap tempo thing is being fixed now. Since none of us are really going places or playing out much right now, I am guessing y'all can wait a few days...

[molul]

2 hours ago, SaschaFranck said:

 

Would you do me a favour and record a small video snipplet?

I could, but, and I mean no offense, it would be pointless ^_^U I mean, I'm not trolling you with false info (it would make no sense at all), and what happens is:

 

-I press tap tempo a few times

-Play a bit

-The delay works as expected

 

And anyway, this video would not fix your unit.

 

As it's been said, this is not happening to everyone. It's not that we can't identify when a delay is working or not xD

 

However, if you want me to try what you're experiencing, I'd gladly see a video of yours and then try to reproduce it here if it's any different from what I'm doing :)

[MonkeyXT]

For the record, to add to the data on user experiences:

Two evenings ago I updated my Helix Rack/Control from v2.82 to v2.90, following the release notes' instructions to the letter (using the new HX Edit pathway to acquiring the update, etc.).

It was the first time I had any real issues during an update (practically a comedy of errors which saw me re-doing the process 3 complete times); the end result was that my Helix was afflicted with the Volume Knob glitch - it wasn't controlling anything, no matter what steps I took to reboot, change the settings, etc.

In fact, on the last reboot attempt I made, the volume came on sky high, higher than it had on previous reboots.

There may have been other issues which I didn't even get far enough to investigate, like the tuner glitch, which I know that my good friends' Floor ended up with - he was also in the process of re-doing the installation.

 

Last evening I simply wiped the slate clean yet again, and re-did the update procedure - important to mention, with only one difference in the methodology of the process (same computer, USB cable, port, etc. - the only functional difference being that I had to use the Updater application to re-flash after I factory reset the unit again, something that HX Edit 2.90 does not have a pathway to doing).

 

I've not spent much time investigating the latest greatest from this new version, but I can certainly say that the REVV Purple channel amp is a fast favorite - I've already bonded previously with the REVV Red channel model as well.

 

As is being often reported, I do believe I'm seeing the tap-tempo misbehavior issue, for which I'm looking forward to a hot fix, but in general it's not a feature I actually use all that often or critically - I generally set my tempo manually.

 

Kudos to Line 6 for a feature-rich update, delivered during - to say the least - challenging circumstances.

The end result was that it all appears to be working as expected.

 

[ramosric]

Well, a bit disappointed today, i had the same volume knob issue that has been reported, basically it will get stuck at a certain level, you might reboot the unit and it will be fine but when you turn off and on again a few times the issue will come back. I tried all suggestions:

- several power cycles

- restoring from backup

- downgrading to 2.82 and then back to 2.9

- full factory reset

and no..... nothing works as the issue keeps coming up, it might seem fine for a bit but then after a few power cycles there it is again....

 

so i decided to go back to 2.82 and wait for the bug fixes, i wouldnt want to risk playing live with this issue, its too much of a deal breaker for me. 
so hopefully they fix it before we are all out gigging again!

 

for those asking, you need to use the Line6Updater to go back to 2.82. I had to do a full reset again since my unit got stuck rebuilding one preset but after a restore from back up in 2.82 it is now working fine as it was before...

[Trl0126]

22 hours 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.

 

 

I got in touch with Line6 support. The fix was to turn off the Helix then press and hold FS6 and 12 (Mode and Tap tempo) while turning back on to manually put the helix into update mode. I was then able to finish loading the update through Lin36 updated.

[SaschaFranck]

1 hour ago, molul said:

I could, but, and I mean no offense, it would be pointless ^_^U I mean, I'm not trolling you with false info (it would make no sense at all), and what happens is:

 

-I press tap tempo a few times

-Play a bit

-The delay works as expected

 

And this is precisely what I'd like to see. End of story.

[molul]

4 minutes ago, SaschaFranck said:

 

And this is precisely what I'd like to see. End of story.

Well, I already replied to that. Up to you! ;)

[molul]

9 minutes ago, Trl0126 said:

I got in touch with Line6 support. The fix was to turn off the Helix then press and hold FS6 and 12 (Mode and Tap tempo) while turning back on to manually put the helix into update mode. I was then able to finish loading the update through Lin36 updated.

Glad to hear that! ^_^

[SaschaFranck]

26 minutes ago, molul said:

Well, I already replied to that. Up to you! ;)

 

No, there's absolutely nothing up to me. You don't want to prove the tap tempo function is working properly.

[silverhead]

6 minutes ago, SaschaFranck said:

 

No, there's absolutely nothing up to me. You don't want to prove the tap tempo function is working properly.

 

I haven't noticed anything wrong with mine. Can you please post a video of it not working? That might help me explore mine further.

[molul]

7 minutes ago, SaschaFranck said:

 

No, there's absolutely nothing up to me. You don't want to prove the tap tempo function is working properly.

Ok man, whatever. You don't seem that interested in being helped, so I won't actually bother from now. I tried!

[SaschaFranck]

10 minutes ago, silverhead said:

 

I haven't noticed anything wrong with mine. Can you please post a video of it not working? That might help me explore mine further.

 

No idea how that would help you, but I'll do just that later on.

[SaschaFranck]

10 minutes ago, molul said:

Ok man, whatever. You don't seem that interested in being helped, so I won't actually bother from now. I tried!

 

Well, the functionality is broken. By now, this is officially approved. No idea how you think you could help me with a function that is officially broken.

[molul]

4 minutes ago, SaschaFranck said:

 

Well, the functionality is broken. By now, this is officially approved. No idea how you think you could help me with a function that is officially broken.

Lol, you tell me. You were the one asking me to record a video xD

[SaschaFranck]

37 minutes ago, silverhead said:

 

I haven't noticed anything wrong with mine. Can you please post a video of it not working? That might help me explore mine further.

 

Here we go. You can see the differences of the tap results in the Helix display. The delays themselves react accordingly, so there's no need to play through them for this demonstration (if you wanted, I'd do that as well).

Fwiw, it's acting like that regardless of which global settings I chose.

 

[SaschaFranck]

33 minutes ago, molul said:

Lol, you tell me. You were the one asking me to record a video xD

 

Of course. Because I simply don't believe it's working correctly anywhere.

[silverhead]

Thanks for the video.

 

I've done a little experimenting with how the Tap Tempo actually works. We could debate whether or not that is 'correct' but here's what I found:

- the function calculates the tempo based on only the last two taps in any sequence of taps. It does no averaging based on a sequence.

- it calculates the interval between the last two presses, not releases, of the tap button

 

By pressing the button once (not twice) you can see the current tempo. Readers, please do your own experimenting and correct the above if necessary.

 

So in terms of your video I think the only taps that matter are the last two. The first 16 are irrelevant. So the question becomes: is it possible that your last two presses of the button were actually a tempo of around 110 rather than 100? That's both hard to say from the video and also hard to get exactly right when using your foot to tap the tempo in real time (which is how the feature was designed to work). Seems to me that if you want an exact, precise bpm you should use the bpm setting, not the Tap Tempo button. Using the button is generally good enough for live play, especially since you can correct it immediately by pressing again if it starts to drift.

 

So, is the above implementation 'correct'? Who's to say - it is what it is. In any case, it appears Line 6 is investigating and will have a fix if there's an actual problem.

 

 

 

[SaschaFranck]

Just now, silverhead said:

I've done a little experimenting with how the Tap Tempo actually works. We could debate whether or not that is 'correct' but here's what I found:

- the function calculates the tempo based on only the last two taps in any sequence of taps

 

According to some Line 6 guy (I don't remember whom it was and can't find a link), tap tempo is supposed to work exactly the same as on Boss units, calculating an average tempo out of the last 4 taps (only in case there are that many taps). I was in doubt about that, but that's what has been said.

Anyhow, with 2.9 I am getting faster tempos when using the tap tempo switch all the time, doesn't matter whether I tap more often or not, it's always faster. And it wasn't like that with 2.82.

[SaschaFranck]

5 minutes ago, silverhead said:

- the function calculates the tempo based on only the last two taps in any sequence of taps. It does no averaging based on a sequence.

 

Ah, found it, see the post of Line6Nelson in this thread:

You may see my response as well - yes, it's sometimes glitchy, but still, I am always getting faster tempos with 2.9.

[silverhead]

7 minutes ago, SaschaFranck said:

 

.. tap tempo is supposed to work exactly the same as on Boss units, calculating an average tempo out of the last 4 taps (only in case there are that many taps). ..

Well that's clearly not how it is working. To demonstrate, tap the button three time with the interval between the final two taps noticeably different from the interval between the first two. You'll see that only the last two are calculated.

 

EDIT: Actually it may be calculating the average of the three. My mistake. Further experimentation required. In any case, any problem will soon be fixed I expect.

 

[tenorkeith]

Just updated to 2.9 and now my volume knob is not working. Is this being worked on? This is for the floorboard.

[PeterHamm]

16 minutes ago, SaschaFranck said:

You may see my response as well - yes, it's sometimes glitchy, but still, I am always getting faster tempos with 2.9.

 

Again... KNOWN problem... hot fix is coming in days, not weeks.

[PeterHamm]

7 minutes ago, tenorkeith said:

Just updated to 2.9 and now my volume knob is not working. Is this being worked on? This is for the floorboard.

check globals.

Also, turn the unit off and back on again 2 or 3 times (let it fully boot up).

I've heard stuff like this happening only on the first few boots. Again... did not see this in my testing, sorry.

[SaschaFranck]

30 minutes ago, PeterHamm said:

 

Again... KNOWN problem... hot fix is coming in days, not weeks.

 

I realized it's a known problem. Some others however don't seem to...

[tenorkeith]

OK, so I've rebooted it about 10 times. Sometimes the volume knob doesn't work at all, and sometimes it lets me turn it one way or the other about a 1/4 turn before freezing. Once, it let me go up and down about four times before it quit working. So something's definitely wrong. Should I re-load the update or just go back to 2.8 until this gets fixed?

[PeterHamm]

Just now, tenorkeith said:

OK, so I've rebooted it about 10 times. Sometimes the volume knob doesn't work at all, and sometimes it lets me turn it one way or the other about a 1/4 turn before freezing. Once, it let me go up and down about four times before it quit working. So something's definitely wrong. Should I re-load the update or just go back to 2.8 until this gets fixed?

I would definitely try re-loading first.

 

[SaschaFranck]

49 minutes ago, silverhead said:

EDIT: Actually it may be calculating the average of the three. My mistake. Further experimentation required. In any case, any problem will soon be fixed I expect.

 

 

See, this is why I said it was glitchy (in the other thread). I tried exactly what you've suggested and sometimes it really seemed like a proper average tap tempo calculation, sometimes it was way off. However, in general things were just working fine for me - just not with 2.9 anymore. So let's hope there's indeed a hotfix coming soon.

[bontarou]

Dear all,

I am Japanese and so sorry my humble English.
I am facing the same (maybe) vol problem with 2.90.
Helix-Floor, tested Main Vol only (phone vol not been tested), Footswitch=Preset mode, 1/4 out, FRFR.

(1) Trial-01 (Helix floor is turned off)

Set Vol=0 (around 7 oclock), turn it on and boot, helix wake up at preset 10C (for e.g.)
but nothing can be heard, Level meter is working.
sometimes preset change does not even work, like hang-up. You cannot to anything.

(2) Trial-02 (Helix floor is turned off)

Set Vol=not zero e.g., 3 (around 10 oclock), turn it on and boot, you can hear the sound of helix preset 10C.
Tweaking vol, but it does not change, sound level you hear stays te same. Sometimes you cannot do preset change, tuner mode, etc.

(3) Trial-03 (Helix floor is turned off)

Set Vol=not zero e.g., 3 (around 10 oclock), turn it on and boot, you can hear the sound of helix preset 10C.
NEVER TOUCH VOL KNOB.
Preset change (e.g., 10C->10B->10D whatever), then into Stomp mode, turn on-off some of your effect chain,
then into tuner mode (tuner mode = sound-muted), then get out of tuner mode to come back to previous mode (Stomp or Preset).

 

Vol Ctrl is working :-) as normal (hopefully)

 

 

(4) Trial-04 (Helix floor is turned off)

Set Vol=not zero e.g., 3 (around 10 oclock), turn it on and boot, you can hear the sound of helix preset 10C.
NEVER TOUCH VOL KNOB.
Preset change (e.g., 10C->10B->10D whatever), then into Stomp mode, turn on-off some of your effect chain,
Skip tuner mode and tweak the vol. but it does not change, sound level you hear stays the same.

 

 

I have tried above 4 cases 5 times each and as for vol behavior, it was reproduced.
I hope my Trial-03 helps some of you for the time being.

 

[52dmk]

Just to add to the Tap Tempo issue;

There's also an issue with the bpm display on tap button showing the correct bpm.

 

In the video below, i'm connected to a helix floor with usb and running HX edit.

I tap in the tempo in HX edit (which is registered correctly and changes the bpm for fx using bpm), however this is not displayed in the tap scribble bpm until i touch the footswitch (touch, not press).

 

Tap video

 

Not sure if it helps debugging at all, or if it's a separate issue.

 

[MGblade]

https://www.dropbox.com/s/mas719tcrp08ch4/20200423_185138.mp4?dl=0

 

here is a video of the tap tempo problem, as you can see i tap a +- 105/110 bpm on my mouse in edit.

but when i tap with either the tap tempo switch or my external tap switch it taps +- 50 to 80 bpm faster, its all over the place.

i did switch from transparent to authentic and vica versa in global settings.

 

(sorry for the bare feet) 

[MGblade]

is there a hotkey for the tempo switch in edit?

 

got it it is "T"

 

so as a temporary fix i now have set the tap tempo switch as a hotkey for edits tap tempo.

 

sorta works now