Leaderboard

Sharing this because I went crazy trying to figure it out, and maybe it’ll save someone else some time. A few days ago, I tried logging into Line 6 Helix Stadium, but the QR code never appeared. The manual login didn’t work either. To make things worse, the HX Stadium App kept crashing, and I couldn’t update it from my computer or through Line 6 Central. Ironically, those were the two options the manufacturer recommended when I contacted support. Since I work in tech, something didn’t add up. Everything pointed to the app not connecting to the server, which explained why the QR wouldn’t generate. Then I thought: “What if it’s the time zone?” I tried something simple: Disabled automatic time synchronization Set the time manually And… BOOM! The QR popped up instantly, and I was able to log in without any issues. Hope this helps someone out there.

I will be taking a two week hiatus from music starting this week. Hope you all have a great Christmas and a fun filled entrance into 2026. This will be the first year I did not applied for any music jobs during the end of year and first of year since 1967. My present to my family and myself is to be present this whole period. If I do not appear active for the next few weeks I am not being rude. Maybe you all and the Line 6 staff you may read this have a wonderful time this season! jpd

If you are on Windows, please look in Device Manager and let us know if you see 'Helix Stadium Bulk Transfer' listed under 'Other Devices.' You may see a blue question mark inside a white circle associated with it. That means the Line 6's Windows USB driver didn't load which will explain the Stadium app crashing every time you attempt to connect to the Stadium XL. I have a support ticket submitted for this. For me personally, it is a moot issue at this point since I decided to order a MacBook Air to work around the issue.

Just received the THON (Thomann) case for my Stadium. I love their cases - have been using one for many years. Built like a tank AND cheaper than the backpack :). It can be operated from inside the lid. It has room in front (where the vents are) and the unit sits suspended by foam sides about 2 cm in the air, so there is plenty of room for heat dissipation underneath. There is also room behind the unit, for the power cable.

please check to see if you have it set (global settings) to automatically assign the block to a footswitch. If this is set to manual, then adding a wah or volume will not work correctly until you make their assignments manually. easiest fix is to delete them, turn on the automatic add and add them again. Hope that helps.

Yes. In your Stomp XL preset use separate amp and cab models (not an integrated amp+cab) and place a SEND block between the amp and cab blocks in the signal chain. Connect the SEND output to the amp’s cab input. Connect the main outputs to FOH. Make sure the output and input levels match. You can position any FX blocks before or after the SEND block depending on whether you want them to be heard in your onstage cab or not.

Yes. That’s what I did: backup factory reset restore backup delete songs reimport kind of a pain but it’s still working for me!

Great discussion. Being able to recall songs via midi (with an associated Preset) will be critical for me (and I suspect others). I may delay purchasing the Stadium until I know this feature has been added. In my small acoustic duo, I use OnSong on an iPad to send PC changes to my devices (BeatBuddy, HX Stomp, and Rc500 looper (backing tracks)) for each/every song. I then use a Morningstar MC8 to control these devices while performing the song. My intent is/was for the Stadium to replace the HX Stomp, RC500, and Morningstar (smaller footprint and less complexity). I go into every gig with a pre-built setlist (in OnSong), but invariably every show is different and we make changes on-the-fly depending on the vibe in the room, audience requests, etc. In those situations, all I need to do is select the song in OnSong, and it loads the beats and/or backing tracks and presets across all my devices - no menu diving, no tap dancing. I get that I could build Setlists (presets) or Playlists (songs) in Stadium, but those don't seem to easily allow for flexibility when ad-hoc set list changes are taking place. The internal Set Lists/Play Lists probably will work fine for larger shows with pre-defined lists that won't likely change. For smaller acts, we're going to need flexibility to call up songs (with associated presets) in a much more flexible manner. Showcase has such promise to help smaller acts add new elements to their shows and I hope Line6 can incorporate features that meet the needs of both large and small acts/performers.

I spent a lot of time going through the settings the Tone War guy suggested for all the metal amps and got those where they sounded great. I came across this by accident looking for different blocks to try...At the very end of your final chain get a stereo model of the Bass DI (located in the Dist section) put the Bass and Treb at 4-5 and the level to suit, this will give your preset a full rich low end def and sparkle presence no EQ or Comp can do. Try it you will be adding it to your presets asap. I have no idea what it was intended for but man it fixes the punch and feel of the real amp that is missing.

Harrumph! I love a good forum storm-off...;)

Here’s the only difference I did which has worked for me. Hope it works for you too. Delete songs (maintenance menu) backup (maintenance menu) factory reset (maintenance menu) restore backup (maintenance menu) reimport (Stadium App)

I have logged this issue and am currently working with Line 6 support. So far, they have confirmed that there are some known issues when exporting presets to Stadium. I have found that creating a preset exclusively on the Stadium and not using the Stadium App has not produced the issues that I have seen on the Stadium App, including this one. I have successfully created two inline cabinets (both using File files), and have been able to use Snapshots to change the IR files with no problem on the Stadium (I don't believe that this can be done reliably in the Stadium App until they resolve the Cabinet/Snapshot issues we are seeing.

I have rebooted the stadium after this happened. I can recreate the issue with my presets as well just by booting it up and then switching between specific presets I have. No sound coming from the unit and matrix mixer shows sound graph (the green leds that would usually show a signal) but they are all at the same half way level with no sound coming out and not input from the guitar. If I reboot, everything comes back and I get normal sound again and normal input readings. I then play for a little bit, and then swtich presets and it happens again over and over again. I am opening a support ticket as well but was wondering if anyone else has had issues with this one? It's a pretty bad bug and makes me nervous about playing this live right now.

Agreed with you all. I am still trying to figure out how the preset management is better now in the Stadium over the Helix. I assume that it would have something to do with Showcase and saving songs. But for now, it is just confusing to me. But what I DO understand is that I have half of the preset storage capacity on the Stadium as opposed to the Helix. I know that I might be able to use multiple SD cards. And 512 presets is still more than enough for any particular show. Still, I found myself swapping out Set lists on the Helix pretty regularly for Preset Development, Play-Along Set Lists, Sunday Set Setlists, Christmas, Top 100 songs, Bass Guitar Set lists, recording, etc. But this only allowed me to at least always have a backup of a set list that I needed to offload in order to create a new one or bring another one in. Remember, we could have 8 Setlists of 128 songs! So far, I have had to reset my Stadium back to Factory several times due to buggy issues and that has only made preset management MORE problematic trying NOT to lose presets that I had created so far (which is not very many yet, either. Remember to ALWAYS SAVE (like the early days of Windows!)

I think we’re going to see improvements in how setlists are implemented in a future firmware update (but I have no basis for that expectation; purely speculation). The idea of using aliases with a single copy of a USER preset is a good one, imho, but the current implementation is a bit confusing to me. Like you, I also see no point in having a setlist file on my computer that has nothing but aliases. I also don’t understand the frequent appearance of a numbered suffix. e.g. (1) behind a USER preset’s name when importing setlists.

I submitted all this to the product feedback. My set lists are per band as well. So I see what you're saying but I don't see it being a problem at least for my personal scenario. Especially as I won't be using showcase at all. the SD card thing just seems like a lot of hoops to jump through. I'm currently still of the opinion that the old Helix way of doing things was actually better, but I'm trying to adapt to the new way to make sure it's not just a case of "familiarity" vs. "new." It used to be so simple and easy to just swap in/out setlists which also included the presets.

It's a small fix I know but I didn't realize how much it was interrupting my workflow until working on a setlist today and finding it fixed! Thanks Line 6! It used to be that if you were in a setlist, and did a tweak and saved a preset, that it took you out of the setlist and to wherever that preset was saved in the User Presets. Now I can make a tweak, save it, and still be right where I was in my setlist! The tiny "quality of life" stuff like this makes a HUGE difference!

I built this satellite board for use with my Stadium XL with a space for the future Expand D-10 I guessed the size of the D10 box by scaling to the size of the known ethercon connector in one of the pix. If anyone at Line 6 knows, here are some questions… 1. what are the actual dimensions of the D-10? (found this on Thomann Dimensions: 40.6 x 138 x 99.7 mm) 2. is the D-10 phantom powered by the Stadium Nexus port or by the USB-C port? 3. what is the current draw of the D-10? thanks! Joe

@rwanderingThanks for the info… I am guessing that you are right that the D10 will receive power from the Stadium XL. Also, I found the D10 dimensions on the Thomann website - Expand D10 dimensions: 40.6 x 138 x 99.7 mm

Yes, there is an editor that runs on Mac. The program/app is called Stadium.

If you know of any easy ways to view all of the Block assignments at a glance, then put them here. You could easily view all of the block "BYPASS/CONTROLLER ASSIGN"ments in the HX Edit App as there was a panel devoted to it. I could easily see all 23 (just kidding, 2 or 3) blocks that might be assigned to a footswitch. I hope that they include that in the Stadium eventually.

In the Stadium Global Settings -> Ins/Outs set the XLR Out Level to Line. The default setting is Mic which explains why that’s what you’re getting.

The issue was confirmed and reproduced by line 6 support. fingers crossed!

That's a known bug. Will be fixed in a future firmware release. You should open a support ticket to report it anyway.

Nevermind, I figured it our. After selecting a set list via the touchscreen, you also need to actually load a preset from that setlist. Once you do that all the scribble strips update to reflect the setlist. I thought I just needed to select the setlist name and the scribble strips would update.

This has bee posted before. In summary: 1. when building presets, make sure your overall volume for a blank preset is around the same as the actual preset you are creating to avoid clipping. 2. set up XLR volume to be Mic level and disable the volume knob, so it's fixed. This will go to the FOH and will never change the level, because you don't want to confuse the sound guy by having different volume levels. 3. use the volume knob to only control 1/4" out which is your monitor mix, or in my case which is going to a power amp (Mooer Baby Bomb) into a 12" speaker cab.

I think one of the most frequent “write your requests down on a $10 bill” situations could be the solo singer/guitarist playing to relatively small crowds, where the atmosphere can be a bit more intimate and an audience relationship can be established. MIDI Song selection, driven by an app on an iPad or whatever, would be very helpful. For that situation, with or without MIDI Song triggers, I would really like to see a re-introduction of a feature I loved in the old POD X3 Live device: Lock Tone 2. On Stadium it would be called Lock Path B. The idea is that you could maintain your vocal tone with the Mic input on Path B while switching presets for your different guitar tones on Path A. I’m going to submit this as a feature request (again). I did submit this request for OG Helix but….. Come to think of it, OG Helix has a Preset Spillover feature that is essentially a “Block Path B I’m using if for spillover” implementation. Might be feasible to tweak it for “Lock Path B I’m using it for vocals”.

That’s available now in the Command Center. Here’s a clip from the manual…. The Song command category is supported by all source controller types other than expression pedals or X-Axis/Y-Axis controllers. This category includes Song View commands to control song transport functions, navigate between existing songs, or select markers within the current song. This can be a convenient way to load and play songs directly from your preset, without having to change to the dedicated Song View screen.

Then I hope this is something that gets addressed in a future update. As a performer, I cannot be bending down and scrolling through Songs to load them...or clicking the arrow buttons 20 times to get to the 21st song in my list. Being able to recall both Presets and Songs via midi is a must. Or, maybe an option would be to use and Instant Command to load the Song when you recall a Preset? I did see that you create Set list of Songs. Are Song and Present Setlist different? Or, can a Setlist contain both Songs and Presets?

Can’t do that yet. I say ‘yet’ because I know it’s been requested and one implementation method is just a matter of providing a Save to Clip option in the Looper. No idea when, though.

Having updated to 1.2 I am coming across myriads of unwanted snapshot bypass and snapshot control. Most of the presets were imported when I was on 1.1, and the amps now also have snapshot control assigned in addition to the Expression control that was there originally. This was apparently a bug in 1.1 which has been fixed in 1.2. What is still happening is inconsistent copying/pasting of blocks with control assignments. When copying and pasting in the editor, the assignments disappear. This also often happens when using the touchscreen on the Stadium. However I have found that saving the original block as a favourite (using the touchscreen and not the editor), and then creating a new block from the favourite, does usually work and preserves the control assignments.

I'm wondering if the Stadium will have any or updated vocal effect integration similar to Headrush. I have been waiting for Line 6 to do this with my current Helix Floor but I guess it's never been a priority. I'd like to have a single unit to handle vocals and guitar that uses all new tech.

ReverendLove, Yes & Agree!! The perfect world.

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.

Update: it's a known issue. Phone support walked me through updating using USB-C to USB-C connected cable to my Mac, as described in another post (just in case any one else runs into this). Once updated and rebooted it showed QR code and 6 digits but didn't need it, just signed in with my username and password. Downloaded the stadium app and all working.

Place the cab/IR at the end of the signal chain (before the Output Block) and place a SEND (to the amp) before the IR.

The one area I'm finding lacking so far is Preset management. In the OG Helix I had a setlist for each band and could easily offload or reload sets by band as necessary. My current method in Helix Stadium is that I group all User Presets by band, batch color them by band as well, and alphabetize within band groups. Then I can easily just save one band's presets to my PC to make room to load another band's presets if need be. I play and sub in a lot of projects and also lots of one-off shows, and make a preset per song so that the Helix is also my setlist, so they can build up fast. To that end, 3 things I think could vastly improve management. 1. Folders within the User Presets. Then I could have a folder per band. 2. since set lists are just "aliases" pointing to a user preset, being able to rename ONLY the alias would be super helpful. That way if I have 10 songs that just use my "Marshall Plexi" preset, I can rename them for each song while also have them all just pointing to the same preset. As it is now, I just have to have 10 redundant copies of the same preset if I want them to be named for 10 different songs. 3. If I save presets from the setlist to my PC, it only saves 0K "alias" and not the actual preset, which I can't see why I would ever want to do. It seems like it should save the actual preset to my PC. There very well may be better solutions as well, this is just what I've thought of while figuring out my workflow.

I would like to see an option to remove the Tap Tempo function from the Tuner button. I know it’s just a matter of time before I’m at a gig and I unknowingly double-tap the Tuner button when accessing the tuner, thus sending the Tempo way out of whack from where it was set on the patch. I only use Tap Tempo on a few of my general use patches. Every other patch is song-specific with the tempo set exactly where it should be, so it would be nice to be able lock the tempo on those patches and prevent it from inadvertently being changed if I happen to be tuning.

I only use Mac with my Stadium and editor. Works perfectly.

Yes, you can't do line level into the XLR inputs.

Reset your helix to factory defaults (after update). of course, back up first, and restore after. A bug is a bug, but this might resolve it for you. You may have to redo from scratch what you had issues with. For instance, to get around the showcase audio issue, I had to delete my tracks and reimport them.

ive been trying since the update was released to submit a ticket for THIS VERY ISSUE. you cant.. their site is broke too.

Solving this problem was a big plus.

Follow the Support tab at the top of this page, then hit Contact Support, then Support Ticket.

Also, make sure you don't have the installer for 1.1 still mounted.

Hey, brother; hope you had a great holiday! It's been fixed. Yes, the workaround was to save between every snap, but that shouldn't be necessary, and it's not now with 1.2. I did end up submitting an official bug report through the support function, and it's one of the top bug fixes in the release notes. So this should no longer be a problem. I know your reply is a couple weeks old, but I'm just writing this to close the loop for posterity :)

The manual only states it must be formatted using the Helix Stadium process using its maintenance screen. You may want to call support for an exact answer. jpd

A brief audio gap is unavoidable as a new preset is loaded using a single DSP processor. This isn’t just a Helix or Line 6 issue; it’s a technical reality. It takes a few ms to load new data into one fixed memory space and all computers/processors experience it. Helix is able to avoid this beause it is a dual processor device. Line 6 has implemented a feature called Preset Spillover in Helix that eliminates the gap. However, it’s costly from a DSP perspective. It requires that a user sacrifice 50% of DSP capacity - one of the two processors and the dual-path preset structure. When this feature is enabled a new preset is loaded into the unused processor/path while the used processor continues to operate. Hence no gap. The Preset Spillover feature is not (yet?) implemented in Helix Stadium.

Plus one for this!! I'm considering a Headrush for this reason, but if Line6 announce vocal effects (autotune and harmoniser), I'll wait

https://www.thegearpage.net/board/index.php?threads/helix-switch-cleaning.2352841/page-2 Happy to report I just used Deoxit 5 on the OUTSIDE of the footswitches, sprayed directly onto the shaft on the lowest setting possible, and actuated the footswitch 40-60 times; vacuumed over the switch with a handheld Dyson, and let a 20" box fan airdry the switches out for 2-3 hours. The first round got 10 out of the 12 switches working perfectly again, the Tap/Tuner + Snapshot/Preset/Stomp buttons (the two I probably use the most) needed a second round. I have a MIDI controller to remotely use the tap tempo, and it looks like everything is 1:1 on my footswtich presses on the Tap Tempo again :) Doesn't seem like there's any need to pull everything apart like in the video and on the thread. I'm glad I saw the guys post on the 2nd page.