cacibi

So I think this is a "Chase" issue. First, I did not realize that Chase is disabled when you zoom but, secondly, it seems that if I re-enable Chase after zooming it does not seem to scroll accurately and this is causing the view to "run off the road". If I load the song, make sure that chase is enabled, then play it - seems to work properly, but any zooming definitely seems to throw the Chase function off with regard to where it is tracking in the song. So seems like a combo of user error (me disabling chase) but also inconsistent Chase behavior when it is re-enabled and/or the zoom level is changed after loading the song.

So I have audio files that are approximately 4 minutes. 3 tracks for one song…all the same length. 
 

After import, the end marker is properly placed at the end of the audio files. Then AFTER the end marker, there is a huge black zone. There is extra space in the waveform/song view after the end marker and during playback the the song ends up in this dead zone. In other words, the position indicator/scroll of the waveform during playback eventually moves PAST the end marker into the black zone. The song ends where it should, but the song view is not properly tracking and it would be great to get rid of this useless, empty space in the song view. 
 

imagine that you are working in Logic and you positioned the project end marker at the proper location, but for some reason….there was still empty space AFTER the end marker.

I have a bunch of dead space (no waveform) after the end marker in my song in Showcase. Is there any way to trim this? The song length appears correct and I don't have dead space in my audio files before import. Seems like the end marker should resize the song view to the correct length but by the time the song finished, I am scrolling through no man's land.

Finally had some time today to set up a test using the Helix in a loop switcher so that I could quickly compare the engaged and bypass tone using a straight-thru signal path (no blocks).

What I found when engaging the input pad (on the preset input block) was that the makeup gain needed to compensate at the output block (to my ears) was +12db.

So - at least now I know where to start for unity gain when dialing in my presets using the input pad.

 

On 2/11/2026 at 11:31 AM, TimAndSmith said:

I have experienced the same thing and have just learned to live with it.  I always have a pad on these days and I think it makes everything sound more natural. I'm not playing with particularly high output pickups either - Jazzmasters, Gretsches with filtertrons, and a low output hum bucker guitar. So many folks play Strats with really low output pickups and like the amp driving a bit so maybe that's what they had in mind. While the output seems to have that same issue, the high end response is much improved and the new Agora amps seem way more dynamic and touch sensitive than the older HX models. I also like that you have an "input trim" that's adjustable rather than the set pad value in the OG Helix. That way you can dial input gain down to whatever you want to even out guitars when you need it. 

I do think it's a nice feature to have the input trim/pad available per preset. I usually turn on the pad then set my output block to +6db to compensate and the signal going into my amp at that point seems fine. I just wonder how many people get a Helix product and find the drives to be so over the top and amp gain to be so over the top.
 

If anything you would expect to encounter the reverse situation needing to boost at the input or early blocks to really get the drives and amps into crazy gain territory.

Experiencing the same thing with Stadium that I did with Helix Floor with regard to gain staging.

I am strictly using vintage output pickups, usually single coils, but every drive pedal or amp sounds WAY too aggressive unless I engage the global or preset pad. Also was running into clipping issues.

I honestly don't know how anyone hits the front end of this thing with hot output pickups, our without the pad engaged.

Received my replacement unit from Line 6 yesterday. Was very glad to see a new firmware release just in time.

I skipped the startup screen to disable automatic time sync and set the time/date on the unit manually as others have reported here that this fixed the "no QR code" issue during the setup process. After restarting and logging onto wi-fi - QR code was there and I was able to login and install 1.2.1 directly on the device.

I then proceeded to format and install new SD card (512GB Samsung SDXC card) and by following the manual instructions carefully (and maybe too literally at times) this was successful.

Next I took a breath and started the process during which the original unit was bricked: namely importing tracks to Showcase via the Stadium App. Again, I followed the manual instructions carefully and completed my first import with no issues. Bit of a drag that the unit does not display the track names as imported, and that tracks have to be renamed in all three Matrix views separately but....guessing this will get fixed/updated in future firmware.

I then created a basic setlist structure and imported some 3rd party presets. Next I started creating an IR folder structure and importing IRs.

So far, so good. It was a lot of anxiety to have the first unit fail, especially during Showcase import as that was a big selling point for me to purchase the unit in the first place. Logic Pro has become my main rehearsal for learning tracks since I discovered the Stem Splitter feature. So handy to be able to solo and reference the guitar parts or vocal harmonies along with creating loop points and markers. To be able to replicate that basic experience on my pedalboard and take it into the rehearsal space will be huge and the ability to make 3 custom mixes on top is beautiful. But it's a lot of money for me and not fun to hear the Arrested Development theme and think "I've made a huge mistake".

Thankful that Line 6 support took care of it by sending me a new unit and that they were willing to send advance replacement and glad to see issues starting to be patched up in the firmware releases.

The manual states that whenever exiting the Maintenance screen, the MicroSD card has to be unmounted then physically ejected. I know it's in the manual, but - is it really necessary to physically eject the card every time you exit the Maintenance Screen? Just seems counter to having a "screw in place" protective cover over the SD card slot.

Quote

To exit the Maintenance screen:
 

Tap the  Eject Micro SD Card button, tap OK in the “microSD card is unmounted” dialog, and then gently push the microSD card inward to physically eject it from the card slot.
 

Tap  Shutdown
 

As instructed in the alert dialog that appears, wait for the Stadium Footswitch 1’s LED to become unlit, then switch the Stadium’s power switch to off.
 

You can now power your Helix Stadium device back on normally and resume using it.

Also, my original unit is on the way back to L6 after going into an unrecoverable state while trying to import Showcase files via the Stadium App. 
 

I guess you would say I have an abundance of caution about trying this again on a non-OEM card.

So, non-rhetorical. 

On 1/18/2026 at 10:08 AM, silverhead said:

Be aware that the Stadium device ships with a microSD card already installed. Is that not working?

 

Is this a rhetorical question or are you actually having a problem with your own cards? Have you been able to format them using Stadium? If so, have you tried using them? 

I am aware that it ships with a card but, if you are going to start utilizing the Showcase feature to import multiple tracks per song for a good number of songs, 32GB is not going to last very long. 
 

Then you start adding in loops, preset clips, samples or whatever else it will hold in future firmware.

Not being versed on Micro SD cards (types, formats, what the numbers on the front mean, if they are made by Keebler elves...etc), I have this to work with from the manual:
 

Quote

Helix Stadium can utilize a microSD card with a minimum capacity of 32 GB, HC type, and U1 speed class (or higher).

I have two Micro SD cards at hand, photos attached, which are both XC but my pal...Google...says that XC cards should be backward compatible with HC.

I am assuming that, as long as I am able to successfully format a card in Maintenance Mode....it is good to go and that the worst that happens if you were to insert an incompatible card is a polite message?

I had a similar question just related to metering. Was going nuts looking for meters and finally found the block meters in the Focus view. But there is no metering on the output block unless you switch to the Matrix mixer. Any other metering or meter views I am missing?

I had the same sorts of issues (before my unit died) and I noticed something odd which was that, even though I had automatic time sync enabled, the unit was consistently displaying a time that was 10-11 minutes behind the network time. 

On 1/14/2026 at 9:48 AM, silverhead said:

Well, if you want to wait you'll still have to turn it on to get the new firmware. Might as well test it out first. If it's sane, try updating to the current firmware. Then you'll be ready to update to the next release comfortably when that happens.

 

I don't believe it was a firmware issue. I expect you just got a lemon. It happens.

I don't think it's just hardware or onboard firmware issues that people are experiencing. The device is obviously phoning home for various reasons including attempting account login. More than previous devices, given that there is onboard wi-fi, this thing is going to be communicating with Line 6 servers. Proxy captures are going to happen in the cloud, not on the device. I don't know if any processing of Showcase audio files is happening in the cloud or if it's strictly handled by the Stadium app. 

But I think that some of the issues people are experiencing with regard to firmware updates, etc. are not just happening on the device but on the server side as well OR there is more potential for issues related to computer security like connections being blocked by firewalls, etc.

I remember early on with my Helix floor unit, there was a period where I couldn't have a web browser open during firmware updates. And before the update process became pretty stable and easy through the Helix Edit app....it was a lot of reading and re-reading a long list of firmware update instructions for every release and it seemed like one wrong move and you were doing a hard reset of the unit.

Line 6 is going to ship me out a new unit. Still kind of freaked out that the thing just went dark in a (seemingly) non-recoverable way.

To be honest, I don't even want to turn the new one on until there's another firmware release but...we'll see. 

I did experience this also. Updated via Line 6 Central and still could not complete the setup portion for login to L6 account. No QR code, no 6 digit code, not able to enter login info manually - either during the startup setup screen or after bypassing and trying to enter in settings.

Oh it's going back...just not sure if it's going back for good.

Received my Stadium XL at 9am this morning, the unit is dead at 3pm. Spent the morning just trying to work through update issues. Still couldn't get it to show me the QR code or enter my account info after updating to 1.2 via Line 6 Central. Hooked it up to various gizmos (Powercab, audio interface, wedge monitor), started dialing in a vocal chain path then went to import my first song into Showcase, left the room during upload and when I came back - the unit was dark. Now....nothing, won't power up at all. 

Have reported to support and hoping there is some kind of magical recovery mode but - at the moment, seems like a pretty expensive boat anchor.

Not sure how to articulate this but a feature I find generally useful on other products is along the lines of "Update ALL Instances" functionality.

Say that you have a block saved as a favorite then, edit the block on an individual preset in a way that you want to save for all instances where the favorite block occurs (even in other presets). Or...you update a preset that is saved across multiple setlists but has the exact same preset name - you would be given the option to update all instances of the preset with the same name.

My Stadium XL just shipped so - no experience with using it but, I have been poring over the manual.

Seems to me, based on the MIDI implementation chart, that there are 122 (5-127) User setlists available for recall via MIDI. By routing the MIDI out back to the MIDI in on the unit (and disabling MIDI Thru), it seems like you could build a dedicated preset that would recall any setlist and then load a preset within that setlist?
 

I can't seem to find this global setting (last setting in Global Settings>MIDI/Tempo) in the manual: "Snapshot CC Send" On/Off.

I'm assuming this enables/disables instant CC commands assigned to Snapshots in Command Center? Searched the firmware updates and manual...can't seem to find the documented explanation.

Thanks

What are my options for a frozen headphone knob on a Helix floor?

Was thinking of trying some Deoxit/contact cleaner first - see if I can get it to move.

Saw another thread on user repair/replacement of the pot. Hoping not to go down that road, but I guess I will if I have to. Way beyond warranty repair.

Don't really use the thing but - also don't like have unusable knobs.

Can't believe there's finally a Princeton. My new favorite Helix amp.

Turned out to be user error on another piece of gear. I had disconnected an expression pedal that was controlling volume via MIDI CC and it defaulted to the lowest value. Dumb, dumb, dumb. 2.82 update went without a hitch (after all).

Still troubleshooting but: after just updating to 2.82 all presets (or if I try to create a new preset) are SUPER quiet after the update.

Not understanding where this massive volume drop is coming from.