Line 6 Helix Stadium bug thread

[AlbertA]

can someone please try this: global / footswitches and change the second mode to snapshots. (mode 1 stompA/mode 2 Snapshot) I did this and now I have bootups where the the footswitches are unlit and non responsive. reboot sometimes brings them back..sometimes.
changed it back to the default (stompA/preset) and it boots normally.....mostly

I have a running ticket for many issues.

Have you imported IRs recently? There’s an issue with that

 

[dean701]

Have you imported IRs recently? There’s an issue with that

there certainly is an issue with that. I just can't tell if my above steps are related to that or not, so I was hoping someone could try it. There are many issues compounding each other.

 

[dws2384]

can someone please try this: global / footswitches and change the second mode to snapshots. (mode 1 stompA/mode 2 Snapshot) I did this and now I have bootups where the the footswitches are unlit and non responsive. reboot sometimes brings them back..sometimes.
changed it back to the default (stompA/preset) and it boots normally.....mostly

I have a running ticket for many issues.

I’ve run mine in that mode since day 1 and not had issue. Think it might still be the IR’s

 

[dean701]

I’ve run mine in that mode since day 1 and not had issue. Think it might still be the IR’s

thanks.

Most of my issues began when I imported impulse responses. that's my workflow. I am totally fine with the FAS sounds but they all revolve around IRs. That's my preference. I want to give L6 my business so if I can get presets on the Stadium to sound close with the same IRs then I am good with it, but it has to be a stable system.

Perhaps it's the underlying conversion engine on Stadium or perhaps the topology of scanning IRs on boot but there are definitely some lingering things going on.
- when importing large amounts of IRs in nested folders, boot times are much longer, boot stalls, full on boot freezes at the banner screen, and overall sluggishness even after boot
- I removed the nested folders and put 2000 IRs in a flat file system, still issues, sluggish at times. Boot times were better but not as quick as an empty device
- with all IRs installed, I changed stomp mode from default (stompA/preset) to (stompA/Snapshot) from then on, most boots failed to activate the footswitch lighting and their functionality. I attempted to toggle it back to default but the encoders seemed sluggish or unresponsive, IMO there is something going on in the background that is bogging it down
- when putting it back to StompA/preset and rebooting it still randomly boots with or without footswitch functionality
- it seems to freeze up momentarily at random times.

Like I said all of this started when I imported IRs but those are important to me so I'm letting L6 attempt to remedy things. I do not plan on removing them unless there are a few that are problematic. Are some impulses corrupt? Was there an error in conversion for some? Is there a lingering background process still spooling causing other processes to struggle? Perhaps

On a positive note: The L6 support team put my image on 1.2.1 (like mine) and were able to reproduce my issues. They then put it on a soon to be released fw version and they stated it seems to be good/fixed.

 

[dws2384]

thanks.

Most of my issues began when I imported impulse responses. that's my workflow. I am totally fine with the FAS sounds but they all revolve around IRs. That's my preference. I want to give L6 my business so if presets that are close to my FAS presets sound close enough on the Stadium using these same IRs, then I am good with it, but it has to be a stable system.

Perhaps it's the underlying conversion engine on Stadium or perhaps the topology of scanning IRs on boot but there are definitely some lingering things going on.
- when importing large amounts of IRs in nested folders, boot times are much longer, boot stalls, full on boot freezes at the banner screen, and overall sluggishness even after boot
- I removed the nested folders and put 2000 IRs in a flat file system, still issues, sluggish at times. Boot times were better but not as quick as an empty device
- with all IRs installed, I changed stomp mode from default (stompA/preset) to (stompA/Snapshot) from then on, most boots failed to activate the footswitch lighting and their functionality. I attempted to toggle it back to default but the encoders seemed sluggish or unresponsive, IMO there is something going on in the background that is bogging it down
- when putting it back to StompA/preset and rebooting it still randomly boots with or without footswitch functionality
- it seems to freeze up momentarily at random times.

Like I said all of this started when I imported IRs but those are important to me so I'm letting L6 attempt to remedy things. I do not plan on removing them unless there are a few that are problematic. Are some impulses corrupt? Was there an error in conversion for some? Is there a lingering background process still spooling causing other processes to struggle? Perhaps

On a positive note: The L6 support team put my image on 1.2.1 (like mine) and were able to reproduce my issues. They then put it on a soon to be released fw version and they state it seems to be good.

Well, sucks that it’s screwing up your workflow but at least you crashed it and found a bug they are working to fix

 

[dean701]

pulled it down to 80 or so IRs and it seems stable. When the new code releases, I'll try some madness again.
The IR browser needs improving though. at least have a search function.

It really is a great sounding unit.

 

[molul]

Loading 2000 IRs on Helix reminded me of those retro games players who load thousands of roms on the Raspberry pi.

It's an interesting behavior: they don't play 85% of those roms, they try 10% for 2-3 minutes, and they play the remaining 5% a reasonable amount of time, although they don't enjoy too much because they've played those few games so many times and it's more a mechanical repetition.

In the end, the joy is in knowing they have "The Collection Of Collections" in a box, and not in playing videogames. I won't judge, but I find it very amusing.

 

[Digital Igloo]

On a positive note: The L6 support team put my image on 1.2.1 (like mine) and were able to reproduce my issues. They then put it on a soon to be released fw version and they state it seems to be good.

Any chance one or more of those IRs was something really long, like convolution reverb-long? IIRC, there was a bug where the conversion wouldn't properly truncate Cab IRs that were clearly not within the expected length range of Cab IRs.

 

[dean701]

Any chance one or more of those IRs was something really long, like convolution reverb-long? IIRC, there was a bug where the conversion wouldn't properly truncate Cab IRs that were clearly not within the expected length range of Cab IRs.

remotely possible but unlikely. Your crew received the full copy of my backup with all IRs included. I was expecting them to come back that an IR was corrupt or, like you said had a problem on import, My other vendor units don't have a problem with it if so. Regardless It seems to be better on the upcoming code. I'll PM you the ticket # in case you care.

 

[Digital Igloo]

remotely possible but unlikely. Your crew received the full copy of my backup with all IRs included. I was expecting them to come back that an IR was corrupt or, like you said had a problem on import, My other vendor units don't have a problem with it if so. Regardless It seems to be better on the upcoming code. I'll PM you the ticket # in case you care.

I care but CS communicates directly with QA and engineering, so I'd be a casual observer, that's all.

 

[dean701]

lol

Loading 2000 IRs on Helix reminded me of those retro games players who load thousands of roms on the Raspberry pi.

It's an interesting behavior: they don't play 85% of those roms, they try 10% for 2-3 minutes, and they play the remaining 5% a reasonable amount of time, although they don't enjoy too much because they've played those few games so many times and it's more a mechanical repetition.

In the end, the joy is in knowing they have "The Collection Of Collections" in a box, and not in playing videogames. I won't judge, but I find it very amusing.

you can judge. I don't mind. I spent 15 years buying and collecting IRs plus Mikko plus the GGD offerings....and I make my own....and CabLAB...
just bought some mirrorprofiles this week. It takes away time from kicking old ladies.

 

[molul]

lol


you can judge. I don't mind. I spent 15 years buying and collecting IRs plus Mikko plus the GGD offerings....and I make my own....and CabLAB...
just bought some mirrorprofiles this week. It takes away time from kicking old ladies.

View attachment 60220
View attachment 60221

I mean...

 

[Chocol8]

lol


you can judge. I don't mind. I spent 15 years buying and collecting IRs plus Mikko plus the GGD offerings....and I make my own....and CabLAB...
just bought some mirrorprofiles this week. It takes away time from kicking old ladies.

View attachment 60220
View attachment 60221

1.6 MILLION IR files? Organized into nearly 65,000 folders? I think you have crossed well beyond the point of forum counseling and into the realm of professional help needed!

 

[dean701]

1.6 MILLION IR files? Organized into nearly 65,000 folders? I think you have crossed well beyond the point of forum counseling and into the realm of professional help needed!

 

[dean701]

not a bug but related to the last post. I wanted to share this little tidbit for those IR mental cases like myself. I used XLN audio XO to attempt to catalog IRs. It's general purpose is to organize and group similar drum samples (snare / kick /tom) to help catalog. It wasn't really designed for cab IRs but it did a half decent job. Warm and woody to the left, thin and bright to the right, rooms seem to be at the bottom.

 

[DanRad]

For what it's worth, the poor support rep I was talking to about the desktop app save bug was so confused. He kept insisting it was supposed to dump you back into the USER folder when you saved a preset. I told him DI had confirmed that wasn't expected behavior when it happened on the unit, and I just wanted to ensure that they realized that, while the bug had been quashed on the unit, it remained in the app. He finally talked with DI directly, then said, "I am not sure where the confusion is. He already knows about the bug, as you said. So how can I help with this? He says it will be fixed in a future update."

For what it's worth, I hadn't gotten any confirmation from DI that he knew about the application bug (I think he was on a well-earned vacation), but I told the support rep I'd been told the best way to report a bug was to open a ticket, so I did.

So this save bug is fixed in 1.3 — sort of.

If you are scrolling through a setlist on the desktop editor, change a preset and save it, the desktop editor stays in the setlist — but on the unit, the preset pops back into the USER folder (I can tell because the preset number changes).

Honestly, it's not a huge issue. I can just select the next preset in the setlist from the desktop editor. But it's odd for the desktop editor and the unit to be out of sync like that.

 

[DG80]

Is anybody else who uses a load box getting a background 'fizz' on their proxy captures?

Here's a quick audio clip of what I'm hearing on all of my captures, regardless of amp or load box used. It's especially obvious when rolling off the volume. This is an AFD100 on 9/10 with an SG and Arcane Phil X humbucker sized P90s:



It was slightly better with 1.3.1 but it's still there. Raised it with support but I want to confirm others are getting this as well.

 

[molul]

Is anybody else who uses a load box getting a background 'fizz' on their proxy captures?

Here's a quick audio clip of what I'm hearing on all of my captures, regardless of amp or load box used. It's especially obvious when rolling off the volume. This is an AFD100 on 9/10 with an SG and Arcane Phil X humbucker sized P90s:



It was slightly better with 1.3.1 but it's still there. Raised it with support but I want to confirm others are getting this as well.

Not sure what I should be paying attention to. On a casual listen, I don't find any problem or weirdness.

 

[EOengineer]

Is anybody else who uses a load box getting a background 'fizz' on their proxy captures?

Here's a quick audio clip of what I'm hearing on all of my captures, regardless of amp or load box used. It's especially obvious when rolling off the volume. This is an AFD100 on 9/10 with an SG and Arcane Phil X humbucker sized P90s:



It was slightly better with 1.3.1 but it's still there. Raised it with support but I want to confirm others are getting this as well.

Loving that Marshall crunch at the beginning of the clip.

Not sure what I should be parking attention to. On a casual listen, I don't find any problem or weirdness.

Probably best demonstrated with a clip of the OG amp to compare. I think what I’m hearing is what sounds a bit like inter modulation distortion on the tail of some of the notes but I’m on my phone.

 

[DG80]

Not sure what I should be parking attention to. On a casual listen, I don't find any problem or weirdness.

Check it out at 10, 14 and 20 seconds. When the volume is rolled off, there is a distinct buzz / fizz behind the note, almost like the gain is still on full but just lowered in volume.