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!

@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

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

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.

Anyone else having this issue? My home network is very stable(retired IT guy). Windows 11 PC that’s up to date with patches.

Thank you, Kfletcha! That sequence does seem to work, although I had to try it a few times for some reason. I've rebooted twice and "the song remains the same". Very cool!

Hey, what a coïncidence, I just build an app to create a preset on Windows or MacOS using AI to craft the sound, see this post : I also thought about a mobile version, but how will you push your preset to the device ?

Very much appreciate it, Dennis! I do now have this fixed and let me pass this along in case this happens to someone else. I kept connecting the XL via USB to my PC to try and get everything manually downloaded. For those of you who don’t know this the Helix Stadium app immediately connects you with your device when you turn it on, but that isn’t the ACTUAL main menu. There’s another option to select from a list of devices. When I clicked on that option it brought up a screen showing Helix Stadium…not XL. When I clicked on a second icon for XL it gave me the message that I was about to overwrite software. I’m not sure how this happened, but it appears the wrong software was loaded on the unit and when I opted to overwrite it with Helix XL, the download immediately started and as soon as it was finished the QR code popped on the XL and I was logged in immediately. For those of you who have this problem in the coming days when you get your preorder. If your QR code or manual log in isn’t working on the XL, connect with a USB and make sure that your XL actually has the XL software on it…not the regular Stadium.

You can also do this using Snapshots if you don't want to waste a FS.

I just had the same problem. I had two cabinets inline on one of my patches. When I selected that patch, it went silent. Switching to other patches doesn't bring the sound back. I tried many different patches. I was able to bring it back by switching to another patch and rebooting. As soon as I went back to the patch with the two cabinets, silence. I removed one of the cabinets on that patch and saved it. Then rebooted again. That seems to have cleared it up for me. Fortunately, I don't normally use two cabinets inline so I'm hoping to avoid this problem in the future. I don't have time to log an issue, but may later when I have time to reproduce the problem.

I suggest you open a support ticket to report these issues directly to Line 6. Similar issues have been discussed here and reported already but the more reports Line 6 receives the more likely it is they will be fixed reasonably soon. Line 6 generally releases firmware updates for new products in a timely manner to fix critical bugs.

I have a Thon case for my Helix. They are good cases with 2 minor problems: the feet need to be glued in properly, otherwise they will fall off (easy fix). The other: on the old Helix, the case is upside-down. When you carry the Helix, its weight rests on the foam where the space is cut out for the cables. As a result, the weight of the Helix bends that plastic fooam, and the Helix slides down, further damaging it. The handle should have been on the other side of the Helix. I solved this on mine by gluing an extra piece of foam to support the weight--easy.

”macOS v14, Sonoma, 64-bit (Intel® and Apple Silicon processor types are supported)˝ 
This is what the manual says.

I run strats and teles with no issues. I use various microphones and alter their position to adjust the tone, and experiment with cabs. It is normal to roll off the top end with global EQ, or on a desk if going direct, to remove high end info with a LPF, and low end with a HPF, as an amp in the room does not reproduce this. Where you set these is a matter of taste. I also use a tight Q notch to dip around the 3-4k mark, and a small mids notched boost to sit in the mix. What might seem extreme, may in fact be normal. When I ran a powercab+ I also reduced the gain of the tweeter, as I found it harsh. Here's an old discussion about this, but some recent videos about the stadium have suggested it removes some of the problematic frequencies already.

Just compared the file contents of the original (problematic) file with the second one I recreated from scratch and noticed that the snapshot settings for all of the blocks is populated with null after the first three Snapshots (which work correctly), instead of true or false as opposed to the Preset that is working properly. I did create the preset with the Stadium App (as that is still my preferred method) so I can not report whether it was the App or Stadium XL that created the problem. But once the preset is created with these null values then I think that it can not be corrected unless you edit the file (perilous and error-prone at best) or just re-create the Preset from scratch as @bverdon suggested. Either way, it is definitely a bug. For further clarification: Original (problematic) Preset: the "snapshots" element is each block records "false, false, false, null, null, null, null, null" The re-created Preset: the "snapshots" element is each block records "false, false, false, true, false, false, false, false" I typically expect true/false to be binary unless there is another purpose being used for the value. This would lead me to believe that those blocks are not being set properly and may either be turned on or off depending on the last snapshot loaded (or another internal array).

Yes. Helix was essentially a guitar pedal. "Guitar pedal" is only part of what Stadium is or can be. I suspect there are many more musicians who take requests, or who select songs in real time rather than follow a strict setlist than Line6 realizes right now. I think as more people start to use Showcase this will become evident. After all, the type of player who takes requests - singer/songwriters, duos, nursing home performers - form a natural market for a feature such as Showcase. Stadium is much more than a guitar pedal, even though most of the marketing focus has been in that direction.

First time posters need moderator approval. I guess none of them (including me) were alerted to your earlier posts because they were in an existing topic. Now that you’ve started a new topic I was alerted to it. Apologies.

This should be a priority, and besides maybe the separating of vocals from guitar, there’s not much that needs added. Auto tune, harmonizer, doubler or chior, and a de-esser, everything else could be pulled from the guitar effects, but it doesn’t seem to be getting mentioned much.

I have the same problem with the conflict between Windows 11 Memory Integrity and the L6PODHD564.sys driver for my POD HD500. I was going to buy the Helix but not so sure anymore.

Spider V is a modeling amp and has full range speakers. Modelers are made to tweak. You have to when you have cabinets, amp models, eq's, drives with EQ's. Prior versions of Spider's were not based on full range amplification. Models tweaked for a guitar speaker. That is what Boss did with Katana. That is what they did with BlackStar ID amps. I followed the video ideas on using parametric eq with Spider V. It helped resolve many of my sound tweaks. It's on Youtube. I posted the link here. Once you learn to use this in presets, the amp will really come alive. Katana is too one trick pony for me. I bought one. I Didn't like it. I won't argue about it. I needed an amp with all the versatility of the Spider V, or Amplifi. Spider V had all the options I need in controllers, and the built in wireless was the deal maker. My Spider V also has great sound from the XLR outputs to our pa board. That output is stereo and sounds incredibly full. We haven't really used my amp loud because we like the XLR out sound. It is much easier to work with our band, and we don't have loud amps mic'd we have to contend with. This way, it's more like my modeler, but it has the amplification that can get loud if I need it to. Spider V has a lot to offer to any player that needs the versatility and routing that I do. Here are links for eq use

I'm getting error code 8000200B and i'm pretty sure there are no pop up blockers or anything running. and it's still not working? are the servers down or something?

These videos crack me up. Doesn't matter how many of them you watch, or who made them. ALL modelers can be made to sound good, or like garbage. However, trying to extract some sort of objective truth from that which is entirely subjective, is a fool's errand. You either like a piece of gear, or you don't. And much of it rests on whether or not you know what you're doing, and are willing to put the time in to learn how to get that unit (whatever it is) to produce the sounds you hear in your head. Put me on the track at the Indy 500, in a car with a couple of million dollars worth of race-tech engineering in it, and I'll still come in dead-a$$ last...but it wouldn't be the car's fault. It'd be because I'm not a race car driver. Same thing applies here.