silverhead

I would open a support ticket to get the official answer from Line 6.

Yes. The app update is to provide file transfer compatibility with the newly released Helix Stadium Native plugin. There is no update required to the Stadium firmware.

Open a support ticket to get an official response.

Check that your XT Input and Output settings match your physical environment. See manual for details. Otherwise open a support ticket for info on how to update your firmware or further problem identification.

I believe the free version of Cakewalk Sonar includes an amp modeling plugin called TH3.

Yes, this also happens on my Stadium Floor device. You can open a support ticket to report the bug.

In the maintenance screen you can bypass the “eject card” dialog by choosing the Shutdown button and following a brief instruction. That will leave the card in place for the next startup.

As the saying goes... if I had a nickel for very time I did something like that..... I still think it's worth opening a support ticket about the unlit state. It could be a design decision as rawkbob suggests, or it could be a bug. Line 6 will tell you which it is.

I see this too. The switches are not lit - but for me they are operational. Pressing the unlit Transport switch does indeed enter Transport Mode. I think the unlit status is a bug that you might want to report by opening a support ticket.

This is not meant to detract from the feature request but the Showcase feature already exists and may address some of the request. You can import the audio stems from your DAW into a Showcase Song. The Song tracks are available in the Matrix Mixer. You can also add a click track and use the various Song Flags to control MIDI and other things. The intention of the Showcase feature is to turn the Helix device into exactly what @maxxlines describes in this quote from him (with no USB cable required): “The Stadium XL has all the hardware capability to be the ultimate single-cable live performance hub.”

I’ve been thinking about this some more because I was very confused in the beginning about the behaviour when editing presets in the USER preset area vs, a custom Setlist. I think that what you describe about getting a second preset also named Song 1 is actually a bug, especially if it exists in the USER preset area. I think there should never be two presets with the exact same name in the User presets area. You might want to consider reporting it via a support ticket. I think the quote from the manual I provided above that begins with ‘as a general guide’ is actually more than that: right now it seems to me that it’s the way to avoid confusion, apparent bugs, and inconsistencies in the implementation of the new approach to presets and setlists that was introduced with Stadium. When you select a preset in a custom Setlist (an alias meaning not an actual preset) you are actually viewing/seeing the underlying preset in the USER presets area. When you then edit and Save the preset, the change is applied in the USER presets area. All aliases to that preset in other custom Setlists now point to the changed preset. I found it confusing until getting used to it. I know it’s different and you prefer the previous duplication of actual presets in custom Setlists but it is what it is.

That's why it's good practice to copy/edit presets only in the main USER preset area - not in a Setlist. A custom setlist that you have created, like your Set List 1, is used to select and order presets from the main USER preset area - not for editing/copying them. Remember - presets in a custom setlist contain aliases to presets in the USER area. They are not themselves different presets, hence editing them and expecting them to behave like different presets is bound to be problematic. Here's a quote from the manual: As a general guide, use the USER PRESETS folder to create your presets, and reserve setlists for placing those presets in a specific order for your performances, rehearsals, and recording sessions.

See the Downloads link at the top of this page. In the Choose Software field select Helix Stadium.

I’m not sure exactly what ‘this ticket’ refers to but this post itself is not a support ticket. To submit an official support ticket to Line 6 you need to follow the Support link at the top of this page.

I see, and the Stadium implementation is different in that it maintains only a single copy of a named preset; no duplicates and enforced change propagation in Setlists. Many people like this. Of course you can get different ‘versions’ using Snapshots but not in the way you mean. But the OG Helix didn’t offer ‘versioning’ of presets either. It just allowed you to have different copies of presets with the same name in different Setlists. Did you not have to maintain your private versioning system anyway? I notice that Stadium will append a number to the name of a New/Copied preset when it recognizes a duplicate name. For example, you can have different ‘versions’ of the same preset with “<preset name>” and “<preset name>(1)” in the User preset area. Stadium essentially gives it a different name with what could be considered an embedded version number. You could then include different versions in different Setlists while maintaining all versions in the User area. You can also include version information in the Info field of each preset. Can that help you with managing versions?