Line 6 Helix Stadium bug thread

[DanRad]

I hate being the Debbie Downer in the main Stadium thread posting bug reports — and it hasn't been clear whether many of the reports are getting notice. So I thought a dedicated thread to bug reports might be a good idea, at least until a few more of the kinks are worked out. Feel free to tell me it's not. I'll get it started with the outstanding bugs I'm most keenly aware of.

HX Stadium App Save Bug: When editing a preset in a setlist in the desktop app, when you hit Save, it takes you back to the main user folder. This had been a problem when saving on the unit, but that was fixed with 1.2. TEMPORARY FIX: Edit from the desktop, but save from the unit.

MIDI On Start-Up Bug: This one's tough to replicate, but occasionally (maybe every three or four reboots), MIDI functions do not work on startup, but work fine after a reboot.

Wireless Bug: The wireless connection to the desktop app drops often. After a time, it will not reconnect without rebooting the unit. Others had this problem all along, but for me, it got much worse after 1.2. TEMPORARY FIX: If you determine the IP Address for the Stadium and connect through that, the connection appears to be far more stable.

 

[EOengineer]

I wouldn’t necessarily expect anything mentioned on these boards to be on L6’s radar. They’re around but it’s not an official support channel. Can’t you submit bugs through the support section of their site? Or try joining the beta?

 

[DanRad]

I wouldn’t necessarily expect anything mentioned on these boards to be on L6’s radar. They’re around but it’s not an official support channel. Can’t you submit bugs through the support section of their site? Or try joining the beta?

Digital Igloo is here a lot and has paid attention to bug reports. One of the first bugs I found was resolved by another L6er. I did apply for the beta team.

I think beyond opening a ticket — which doesn't seem appropriate in any of the bugs I mentioned above — I don't think Line 6 has a bug reporting mechanism.

 

[EOengineer]

Digital Igloo is here a lot and has paid attention to bug reports. One of the first bugs I found was resolved by another L6er. I did apply for the beta team.

I think beyond opening a ticket — which doesn't seem appropriate in any of the bugs I mentioned above — I don't think Line 6 has a bug reporting mechanism.

Yup we’re frequently engaged with them here, I just don’t think there is necessarily a commitment that things posted here end up getting tracked on their side. In other words this issue could fall through the cracks. You might want to search around…I know a couple folks have posted links to the beta application around here.

 

[DanRad]

Yup we’re frequently engaged with them here, I just don’t think there is necessarily a commitment that things posted here end up getting tracked on their side. In other words this issue could fall through the cracks. You might want to search around…I know a couple folks have posted links to the beta application around here.

I have applied for the beta team, as I said.

It just seems like having a dedicated bug thread might be helpful — especially with the main thread going off on so many tangents recently.

 

[EOengineer]

especially with the main thread going off on so many tangents recently.

 

[AlbertA]

If the intention is to bring it to Line6 purview (and have them fix it) submit a ticket to them.

Why is Helix Stadium Talk thread not appropriate? a bug in helix stadium is helix stadium talk.

Digital Igloo is here a lot and has paid attention to bug reports. One of the first bugs I found was resolved by another L6er. I did apply for the beta team.

I think beyond opening a ticket — which doesn't seem appropriate in any of the bugs I mentioned above

Why not though? If you want them fixed - the best way is reporting to their ticket system.

— I don't think Line 6 has a bug reporting mechanism.

Yes they do: https://line6.com/support/tickets/add.html

 

[Chocol8]

Bug threads not on the company forum don't get read and TRACKED like bug report tickets. You really need to create tickets in their system so the guys writing the software (NOT DI) see them and can keep track of them until they addressed.

 

[Orvillain]

This won't get read by anyone whose responsibility it is to deal with it, sorry. Expecting Digloo to do it is a bit much imho. Sorry to be a downer.