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 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.

A reminder to all users that this forum is a peer-to-peer user forum. No one from Line 6, particularly not the developers, is required to hang out here. Some do occasionally out of personal interest but we as users shouldn’t count on it. Nobody here can fix a bug or implement a new feature. Accordingly, this is not the official place to make bug reports or feature requests. If you want your bug report or feature request to actually reach Line 6 you need to do something else. To report a bug, open a support ticket. https://line6.com/support/tickets/add.html To submit a feature request: https://line6.com/company/contact/productfeedback/

Hey fellow Helix/HX folks — long-time user here. Been gigging with a Helix since 2015, then switched to an HX Stomp later for portability. Wanted to share something I've been building. I kept wanting a preset editor I could open on whatever was in front of me — laptop, iPad, phone, whatever — without installing anything or having the unit plugged in. Couldn't quite find that anywhere, so I built it myself. Figured some of you might find it useful too. Helrig (helrig.com) — free, runs entirely in your browser: Drag in a .hlx from any of them — Helix Floor, LT or Rack, HX Stomp, Stomp XL, HX Effects, even Helix Native — or pull presets straight out of a .hxb backup or .hls setlist. Start from blank or load a sample to poke around Full signal chain and parameter editing, snapshots included Search blocks by their Line 6 name or by the gear they're modeled after — tube screamer, Fender reverb, JCM-800, whatever you actually think in Auto-detects the device on import and matches the DSP budget/footswitch layout automatically DSP budget enforcement like HX Edit — won't let you overbuild past what the device can actually run Hover a path's DSP icon to see the cost of every block on it, or open the full usage report for the chain — honestly my favorite feature; it's saved me from guessing more times than I'd like to admit Convert a preset between devices, and it tells you exactly what it had to change to fit — rather than quietly mangling it Undo and redo with a named history — "Add Deluxe Comp", not forty rows of "Edit" Share a preset with a link if you want to; the rest of your library stays private and you can revoke it any time Nothing gets uploaded — the file stays in your browser the whole time, no account needed There's an optional account that adds a cloud library — setlists, labels, version history — if you want presets synced across machines. Entirely optional; the editor is identical without it. Direct USB sync to the hardware is in progress but not live yet — right now it's file-in, file-out. Unofficial/independent project, not affiliated with or endorsed by Line 6 or Yamaha — just a fan-built tool made with a lot of respect for what they've built with Helix/HX, still the best guitar gear after almost 11 years. Rough edges still get fixed fast — if something looks wrong or a block/parameter shows up unlabeled, tell me and I'll dig into it. Feature requests welcome too, including "I wish HX Edit did X" type stuff — that's usually where the good ideas come from.

Hey everyone, we wanted to share a beginner-friendly tutorial series for the Line 6 Helix Stadium on YouTube that we’ve been working on for over half a year! The course is completely free! Yesterday, we published the final episode of the series, so now feels like the right time to post about it here. The full series contains almost 2 hours of Helix Stadium knowledge, so if you want to learn something new, understand the unit better, or simply see whether the Helix Stadium is the right fit for you, we’d love for you to check it out. Across the whole course, we cover everything you need to know: hardware and navigation, presets and setlists, blocks and signal flow, building your first tones, snapshots, routing and stereo, Song View and automation, controllers and footswitches, the Command Center, and finally global settings, USB audio, and maintenance. We also included a lot of practical audio examples, real-world use cases, animations, and graphics to make everything easier to follow, especially for beginners. We put a huge amount of work, time, and our own knowledge into this series to make the content as clear, practical, and reliable as possible. The series is available both as individual episodes in a playlist and as one full tutorial video, depending on how you prefer to watch. We’d genuinely appreciate any feedback. Let us know what you think - we really hope this helps someone get more comfortable with the Helix Stadium and make better use of it! :) Tutorial on YT:

First good size show with Stadium last night and it went great. New form factor was nice getting there (able to fit in my carry on). Love the touch screen capabilities and on site tweaks and levelling. Also liked the easy to get at mute on the XLR mixer matrix for front of house. Updated all my patches to use agora and they sound WAY better. Less digital artifacts and just more clarity and feel. Not just me - bass, vocals and others commented. Used showcase to import my stems and get ready. Great start and can't wait to see what's in store.

I can understand your disappointment. Of course, disappointment is a corollary of expectations. Recall that, late in development, Line 6 publicly polled users with the question “Would you prefer a more complete and finished product that will be released later, or a less complete product available sooner?” The clear user preference was sooner, with additional features coming later. Accordingly one should not expect a complete product at this point. You’re absolutely right that promised features like proxy capture remain unfulfilled, as expected. Will other features like preset spillover be added in a future firmware release? I certainly expect so, but I’m not putting any timing on that. Helix Stadium is still very much in its early development. It will, and already has, been much improved. For instance the Showcase feature was not released in v1.1; it arrived in v1.2. Also, v1.2.1 was released very recently, fixing some 50-odd bugs. I think anyone who owns a Stadium device now should consider themselves to be early adopters, complete with the associated bugs and glitches. You don’t have to use it yet. You can wait for several more months until it is more complete and less buggy. Most users responding to the Line 6 outreach wanted it sooner rather than later, and that’s what Line 6 did. Who knows what Stadium will become? Recall that the original Helix product has evolved significantly since its release. It is hardly recognizable now compared to that time. The same will happen with Stadium. As you point out it is currently unfinished. Of course, your feelings are your own and they are legitimate based on a certain set of (reasonable?) expectations.

I have read the Stadium online manual from beginning to end. I realize it cannot be in download format because of the embedded videos. So, whether that is good news or bad news it is, in my humble opinion, just news. I realized answers to about 80% of the questions so far, including my 60% of questions, are in the manual. There are few typos regarding XL versus no XL but Line 6 may correct them once the non XL ships. I, for one, will be sitting down for about a week going through each step of the manual. The various sub displays on the touch screen make it worth it for me. If I am not back in a week that means I wasn't able to shower after woodshedding and my wife isn't allowing me in the house until I go YMCA and shower there. I can only speak for myself in that, after reading the complete manual and checking the videos, it will be well worth the trouble for me. Wish me luck. jpd

I captured a bit of Steve Sterlacci's video: and imported into Logic so I could use Match EQ to learn more about the differences between Helix Floor and Helix Stadium Agoura amp models. Steve clearly demonstrates the long known issue with Helix Floor having a somewhat odd high-end emphasis (sometime call squirrels, fizz, ice-pick, etc.) that needed to be tamed with pretty aggressive high cuts in the cab block. The Agoura amp models don't see to have this emphasized and somewhat tiring high end. We can use Logic's Match EQ to get a better idea what EQ would be required to make Helix Floor more closely match the Agoura models, and maybe be better informed about how to EQ Helix Floor to tame the high end. The Match EQ graph is quite interesting: As we might have expected, there's additional high end in Helix Floor starting at around 1 kHz, gradually increasing to about 8 dB at around 6 kHz that Match EQ is cutting. What's surprising is the significant boost in the "air" frequencies about 6 kHz and up to 20 kHz. That could be part of the amp models, or the better hardware in Helix Stadium. Now I captured this off a YouTube video, so I don't expect the audio to be that great. And I only matched one sample from the video. So this might not be that accurate. But it perhaps gives us a starting point to know how a little more about how to tame the Helix Floor's high end. So try it, using a high cut at say 5 kHz, or parametric, graphic or even global EQ to match what Match EQ is suggesting. This might breath new life into your Helix Floor.

The Apple silicon chips have been out since 2020, after 6 years, L6 should really be releasing software to support this natively. even the latest helix stadium software is still not released with native builds. I haven't installed rosetta and don't plan to on my M3 macbook air, i have an old intel macbook from 2008 that still works and runs the software. I really don't understand why companies like L6 don't have modern software chains, this is basic stuff that should be addressed quickly - It's not exactly a surprise that they're doing this (did i mention the Apple silicon chips have been out for 6 years?).

Hi everyone, I am writing this post as a concerned Mac mini M4 user. Every time I open POD Go Edit, macOS repeatedly warns me that this software will soon lose support because it still relies on Intel architecture (Rosetta translation). Apple will eventually drop Rosetta entirely, and the POD Go community on modern Macs will be left completely stranded. We need an official statement or an update: When is Line 6 planning to release a native Apple Silicon version of POD Go Edit? Furthermore, the user interface (UI) feels incredibly outdated and clunky for modern desktop standards. Navigating the software feels like a chore rather than a helpful tool for musicians. The POD Go is an amazing piece of hardware, but the desktop software experience is severely lacking and falling behind the competition. Please, Line 6 team, give us a modern, native app that matches the quality of the pedalboard itself. Who else is facing these constant macOS warnings? Let’s bump this up so the dev team takes notice.

I played at an outdoor festival this weekend on a stage with a canopy, using a sunshade over the Stadium, with the brightness of the scribble strips set to 100%, and still I could barely read the scribble strips. The problem is two-fold. The OLEDs aren't nearly bright enough, and the glass picks up reflections so you have to move around to find an angle where you can read the text. The scribble strips for the active buttons were faint, but they could be seen. The OLED pixels for the inactive buttons are dimmed so they were nearly impossible to read even when I bent over for a closer look. The LED rings around the buttons could not be seen. Had it not been for the canopy, I believe that the Stadium may have been rendered unusable. I submitted a support ticket a while back about the poor visibility of the scribble strips. I doubt that they can turn up the brightness much without damaging the OLEDs, but there are some things that could be done to improve the visibility. My suggestion is that they could create a "performance" setting which eliminates dimming of the inactive buttons. Instead, all OLEDs would be at maximum brightness, and the active buttons would have the pixel colors inverted to designate the buttons which are active. Something similar to the attached concept image. They still wouldn't have the high visibility of an LCD display, but it would be an improvement. I love my Stadium, but I have a number of outdoor gigs this summer and if I end up in direct sunlight situation, the Stadium may be unusable. I play in three different bands and I'm one of those guys that creates a lot of song-specific presets, so memorizing what each button does in order to use the unit blindly is not an option. I really don't want to do it, but I plan to take my Boss GT-1000 as a backup to all outdoor gigs just in case the Stadium is impossible to use.

Why is there no option to have the preset BPM persistently displayed above the tap tempo switch like there was in Helix floor? I have looked everything in global settings as well as the same spot in the OG Helix Displays settings. Would love for this to be included in the next update, please!

Windows 11 considers this driver invalid and refused to switch 'core isolation' on, which MS considers a safety issue.

None of the manufacturer's recommendations fixed the problem. Considering that it appears to be a connection problem with Line 6's servers, I tried something simple: I disabled "Date Time via Wifi" and setting the time/date manually, and boom! It fixed everything instantly! Incorrect time zone prevents connection to Line 6 servers.

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

Quick update for anyone who lands on this — a fair bit has changed since I posted it, so I've refreshed the top post too. Biggest one: it handles the whole family now, not just Helix and the Stomps. HX Effects, Helix Rack, Helix LT, and presets made in Helix Native all open and edit properly. Rack and Stomp XL are flagged beta in the app — I built those from preset files rather than having the unit on my desk, so everything behaves the same, I just can't honestly say I've proven it against real hardware yet. It converts between them now. Point a Helix preset at an HX Stomp and it tells you exactly what it had to change — amp and cab gone if you're heading to HX Effects, snapshots past whatever the target holds (named, so you know which ones went), footswitch assignments with no switch to land on. If it still doesn't fit it stops and tells you how many blocks to pull rather than picking for you. That bit mattered to me — only you know which ones the sound actually depends on. You can pull presets straight out of a .hxb backup or a .hls setlist now, so you don't have to export them one at a time first. Sharing: post a link to a preset and anyone can open the chain, load it in the editor, or grab the .hlx. Rest of your library stays private, and you can kill the link whenever. Undo and redo got a proper named history — "Add Deluxe Comp", not forty rows of "Edit". And there's an optional account now that adds a cloud library — setlists, labels, search by the gear inside a preset, version history, a trash you can undo from. Emphasis on optional; the editor is identical signed out and still uploads nothing. USB is still in progress, still file-in, file-out for now. Rough edges and "I wish HX Edit did X" requests still very welcome — that's still where the good ideas come from.

Firstly, congratulations to the Line 6 team on the Helix Stadium XL. The Matrix Mixer, Showcase integration, independent output buses, and USB audio interface have made the Stadium one of the most innovative live-performance processors currently available. This proposal is intended to unlock one workflow that I believe would make the Stadium XL the definitive all-in-one live performance hub for professional touring musicians. ⸻ Current workflow Many modern touring musicians now use a laptop running Cubase, Ableton Live, Logic, MainStage or Reaper as the central show controller. The DAW simultaneously provides: • Backing tracks • Click tracks • Spoken cues • MIDI Program Changes • Snapshot automation • Tempo automation The Helix Stadium XL already receives MIDI perfectly over USB. The missing piece is flexible routing of USB audio returns. ⸻ Current USB Routing Currently: USB 1/2 ✔ Appears directly in Matrix Mixer ✔ Independent level ✔ Independent routing ✔ No DSP path required USB 3/4 Requires DSP Path USB 5/6 Requires DSP Path USB 7/8 Requires DSP Path This means additional DSP paths are consumed purely for routing audio rather than processing it. ⸻ Real-world example Professional live show Inputs Helix • Guitar • Bass • Vocal Cubase USB 1/2 Stereo Backing Tracks USB 3 Click USB 4 Voice Cue USB MIDI Program Changes Snapshot Changes Tempo Changes Desired Matrix XLR (FOH) • Guitar • Bass • Vocal • Backing Tracks (No Click) (No Cue) ⸻ Phones / IEM • Guitar • Bass • Vocal • Backing Tracks • Click • Cue ⸻ Current limitation Because USB 3/4 cannot be accessed directly inside Matrix: Click and Cue must consume one or more DSP paths. This reduces available DSP for: • Dual Guitar amps • Bass processing • Vocal processing • Parallel effects • Additional routing ⸻ Proposed Feature Expose: USB In 3/4 USB In 5/6 USB In 7/8 as Matrix Mixer sources. Exactly like USB 1/2. Each should provide: • Level • Pan • Mute • Solo • Assignment to: • XLR • 1/4” • Phones ⸻ Even cleaner implementation Instead of adding three additional Matrix channels: Simply allow the existing USB Matrix source to choose its source. Example: USB Matrix Source ○ USB 1/2 ○ USB 3/4 ○ USB 5/6 ○ USB 7/8 This would require almost no UI expansion. ⸻ Additional Enhancement Allow multiple USB Matrix channels simultaneously. Example: USB 1/2 Stereo Backing USB 3 Click USB 4 Cue USB 5/6 Playback Stem Each independently routable. ⸻ Why this matters The Stadium XL is uniquely positioned to become: • Guitar Processor • Bass Processor • Vocal Processor • USB Audio Interface • Playback Engine • MIDI Show Controller • Monitor Mixer inside one device. No additional interface. No external mixer. One USB cable. One pedalboard. One MacBook. ⸻ Competitive Advantage Many touring guitarists currently carry: • Guitar Processor • Playback Interface • MIDI Interface • Small Mixer The Stadium XL already contains almost everything required. This firmware enhancement would allow many musicians to eliminate: • Additional USB interfaces • Playback mixers • Extra cabling resulting in: • Faster setup • Fewer failure points • Easier travel • Simpler stage footprint ⸻ Why this fits the Stadium philosophy The Matrix Mixer already supports multiple non-DSP sources including: • USB 1/2 • Bluetooth • Aux • Showcase playback • Click • Count-in Extending Matrix support to additional USB return pairs would be a natural continuation of this architecture and would greatly enhance the Stadium’s role as a complete live-performance hub. ⸻ Final Thoughts I’m a professional touring musician building my live show around the Helix Stadium XL. My goal is to use a single USB connection from Cubase to carry: • Backing tracks • Click • Cue tracks • MIDI Program Changes • Snapshot automation while using the Stadium XL as the only stage processor for guitar, bass, vocals, monitoring, and FOH routing. This enhancement would make that possible without additional hardware and would elevate the Helix Stadium XL into a class-leading solution for modern live performance. Thank you for considering this feature request and for continuing to develop such an innovative platform.

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.

The Variax community has shown extraordinary patience, but that patience is running out. We've been waiting for the D10 interface since October 2025. We heard expectations of an April 2026 release. Four months later, we're still waiting, with no product and little meaningful communication. These aren't casual customers asking for an update. These are some of your most committed, long-term supporters who have invested heavily in the Helix/Variax ecosystem and kept faith in the platform. What many of us want more than the product itself is honesty. Tell us where things stand. Tell us what's gone wrong. Tell us if the project is delayed or canceled. What we shouldn't have to deal with is month after month of uncertainty and silence. Loyal customers deserve better than that.

Anyone else having compatibility issues with Windows and the Spider remote app? I cannot connect the device at all. Its clearly connected for sound as my laptop plays sound through it just fine, and the settings on the amp itself work fine but I cannot get the two to talk to each other. I have uninstalled and reinstalled, done all the usual stuff. It was working fine a couple of weeks ago but now wont connect at all. I did note that when I re downloaded the app, Windows had flagged the download as being unsafe (or words to that effect) so dont know if that has anything to do with it?

The way I read it, some CCs are RESERVED for GLOBAL FUNCTIONS. These are called when CCs are sent on MIDI Channel 1. Use MIDI Channel 2 for USER ASSIGNED CCs.

Are all of your computers Windows 11? A recent update (maybe several) caused the problem. On one of my W11 boxes the problem was caused by a ".net Framework" update (KB5092427). Rolling back to a restore point previous to that update and preventing Windows Update from reinstalling it fixed the problem. On another W11 box I didn't have a similar restore point and simply uninstalling (KB5092427) didn't fix it. On my last remaining W10 box it's not an issue, USB MIDI works fine.

I would be happy to have a phone or video call with you. If you give me contact information I will follow up to arrange the details.

Capture was taken with the same settings on the amp as in the preset. Let me know what you think. Best, Tim Rockerverb VS.hsp LRS Orng Rock Gain 5 DI.clone

For anyone hitting this post searching for how to run Helix Stadium on Linux, I've figured out one way to do it - but it only works if you have Wifi setup on the Stadium Install Steam Download the Helix Stadium installer In Steam go to Library > Add a Game > Add Non-Steam Game and select the downloaded installer exe Find the entry in your Steam Library and click Play, the installer should show up. Go through the install steps choosing the defaults Once that's done you'll need to find the directory that Steam puts file under. For me it was ~/.steam Under that directory you need to find where it installed Helix Stadium. For me it was ~/.steam/steam/steamapps/compatdata/{the most recently created folder}/pfx/drive_c/Program Files (x86)/Line6/Helix Stadium/Helix Stadium.exe. Copy the full path to the EXE In Steam right click on the entry for the installer and choose Properties... Rename it to Helix Stadium Change target to "{path to the exe above}". For me it was "~/.steam/steam/steamapps/compatdata/{the most recently created folder}/pfx/drive_c/Program Files (x86)/Line6/Helix Stadium/Helix Stadium.exe" Change Start In to "{path to the exe above but without the exe filename at the end}". For me it was "~/.steam/steam/steamapps/compatdata/{the most recently created folder}/pfx/drive_c/Program Files (x86)/Line6/Helix Stadium/" Close the Properties window Click Play and Helix Stadium app should start I had to cancel the auto connect, and manually type in the IP address, then click Connect (this needs to be done at the start every time) Once I did that it works as expected! Hope that helps somebody.

All, I was making this too complicated ... I WAS WRONG - for those who read the two responses I just deleted. So after much trial and error it runs out the instant command (thunderbolt) feature in command center is much easier than I thought for sending MIDI commands via Snapshots. Or as Mark said in the movie "Renaissance Man" ... "Too easy drill sergeant!". Unlike the OG Helix Floor were I had to use a instant command for each snapshot, in the Stadium I start with snapshot one. Then I go to command center and select just the first instant command thunderbolt. For my amp I will only have to use MIDI channel one using CC as my command selection. I will start with my mesa JP-2C channel one which is CC#20 and set it for snapshot control (in the Stadium app it is a right click on CC# label then use the slide bar to enable)(on the Stadium itself you will see it pop-up when you touch the CC# label if enabling touch). 64 will be my on value and I am testing various wait commands currently using 2 ms; not sure but I may just set it to zero later after some final tests. Then I just activate the snapshot I want to change the CC# value for, make the change, and done. So you only need one instant command in my scenario with variable CC# YMMV. It may seem like more work to go between home change snapshot then back to command center or you can have the Stadium at your computer/laptop while working on this for a little less work. It almost felt like an Easter Egg until I read and read and then read again within the manual and then the lightbulb turned on in my pea brain. <darn it> jpd

Kind of defeats the purpose of a modeller doesn’t it?

This biggest point here is this: Line 6 asked the community if they would be willing to wait or get it earlier - most said they could ride it out and get the updates as the bugs were worked out . . . it sounded like most wanted the unit sooner rather than later (I know I did). Since I'm not using it to gig with at this time, I'll push thru the problems for now. Syphus

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!

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

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 connected the send 1 from my Stadium to the input for a stage monitor I have on hand. I set the FX loop 1 output to instrument because line level was too loud. Then I set the output for the tuner to send 1. When I used the tuner there is no output to FOH and the monitor gave me my ""on stage" audio. Adjusting the level output on the monitor, I was able to have a very controlled output volume to listen to my tuning as well as if I wanted to "test" a part without going through the board. If you have something like a Behringer EUROLIVE B105D (or smaller) and a On-Stage SSAS7000B it could be a solution for about $150.00 without having to bend over. Just a thought. jpd

My levels are about the same. I wouldn’t worry about it unless you hear something you think isn’t right. I pay more attention to the signal level indicator in the Output block; if that turns red it means there’s clipping. Also, you can test the output level meter (the one on the right thwt you refer to) in the Amp block. If it behaves like a normal level meter it might change colour to orange and then red as you raise the amp’s Drive/Gain, Master, and/or Channel levels. I don’t know if it actually does change, but if you can make it change colour then you can be confident everything’s OK as long as it stays green.

Yes, custom setlists is the way to go for live events. Be aware, though, that the implementation of setlists is completely different in Stadium vs. OG Helix. There is a big conceptual change, and I think some bugs that still need to be worked out. The following is aimed at all readers here, not you specifically….. Conceptually, the USER setlist is now the only place where the actual presets live. A custom setlist is a list of aliases (pointers) to the USER setlist presets. Read the associated section in the online manual for clarification. This is still early days for the new mindset and implementation. I have experienced and reported some behaviours that I think are bugs: - when you Export a preset from the USER preset view it creates the associated preset file on your computer, as expected. When you Export a preset from a custom setlist view it creates a copy of the alias on your computer. If you’re not careful you can overwrite the actual preset on your computer. I think Exporting presets from the setlist view should be disabled; I can’t see any use for saving a single alias in a file. I can see a use for exporting/saving a setlist of aliases. - I have also experienced duplicates. I think there should only be a single copy of any preset name. I think any bracketed duplicate preset name is the result of a bug. If it’s a different preset it should have a different name; if it’s actually a duplicate of the same preset it shouldn’t exist. That’s the whole idea of the new implementation. My suggestion at this point, until some bugs are resolved, is to edit and Save presets only from the USER setlist view. The interaction between the presets themselves in the USER setlist and their aliases in custom setlists is where I think the bugs live. This will require careful attention and some extra touches (on the device) or mouse clicks (in the app/Librarian) for a little while to make sure you are in the USER setlist view but it should reduce the unexpected behaviours. I may end up eating my words here. If there is a valid reason for duplicate presets to exist in the USER setlist I would like to hear it. Meantime I encourage everyone experiencing duplicate preset names to open a support ticket to report it. The more info and evidence Line 6 has of these bugs the more likely they will get fixed sooner than later.

When are we going to get a printable file version of the manual? Some of us like to read and understand things to make better use of the unit's features. Especially with the upgrades coming for Showcase and Proxy. The on screen stuff is great and all but something of this depth and complexity needs a manual.

Hope this helps as well - In the list view for amps (not legacy amps) there will be a thin gray line and any amp above is Agora and those below are HX.

STFW means Search the F*&$ Website! I just want to highlight that Line 6 has taken a new approach to the product manual for Helix Stadium. It is not a downloadable PDF file. Instead, it is its own integrated, cross-referenced, well indexed, searchable website that includes links to videos where appropriate. It also includes the Helix Stadium app ‘manual’. The Support -> Manuals area provides a link to this new ‘manual’. I strongly suggest you check it out. For your convenience… https://line6.com/helix-stadium-manual/ We all know that it is common etiquette in user forums to do at least some research for existing answers to questions, especially basic operational questions, before asking in the forum. This new approach to the manual makes that very simple. So, in future, rather than suggesting that someone RTFM I will just say (politely, of course) STFW.

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.

I discovered this software bug while attempting to program the expression pedal to turn the WAH block ON as soon as it begins to rock back. Helix OG has this capability and so does Stadium, however currently there is a bug that prevents it from functioning properly. This drove me nuts when I tried to set it up because it worked sometimes but not all time, then I finally figured that there's a software bug preventing it from working properly. The Objective: I have a song where I need to quickly toggle the WAH on and off and its not practical to do a hard press of the toe button between every ON-OFF cycle, so the effect can be easily accomplished by programming the expression pedal to turn the WAH ON automatically by rocking the expression pedal back. When the pedal is returned to the toe-down position the WAH block turns off. This action can be assigned in Stadium by selecting the WAH block, then going to Menu>Bypass/Control, set the Parameter to "Bypass", Switch to EXP 1, Position 99%, and Wait to 0. The toe-down position is 100%, so when the pedal is rocked back, the WAH block turns on as soon as the pedal crosses the 99% mark. The Bug: When the assignment is created as described above the pedal appears to do exactly what it should. The preset is saved with the WAH block in an OFF state. The problem is that when you leave the preset and then return to it, the first time that you rock the pedal back, the WAH block does not turn ON as its programmed to do. You can rock the pedal all the way back to the heel-down position it it still doesn't turn on, BUT when you return the pedal to the toe down position the WAH now turns on. The ON-OFF state is now reversed from what it should be. Now when you rock the pedal back the WAH turns OFF instead of ON, so moving the pedal has no effect. When you return the pedal to the toe-down position the WAH turns ON. With the pedal in the toe-down position, you can manually toggle the bypass state of the WAH block to OFF, rock the pedal back and it turns on as it should, but if you leave the preset and return to the preset. it will once again reverse to ON-OFF state from what it should be the first time that you use it. This bug isn't related specifically to the WAH block. Any block that it programmed to be triggered on and off by the expression pedal will reverse its programmed state the first time you attempt to use it after opening the preset. The Workaround: While trying to figure out what was going on, I discovered that it is only the very first bypass assignment that you program within the preset that doesn't work properly. if you program additional blocks to also turn ON and when the pedal is rocked back they will function as they should, even after leaving the preset and returning to it. So here is my workaround: I deleted the WAH block to clear its assignment, then added a GAIN block to the preset and set the gain to 0, so it has no impact to the signal whether its on or off. I created an assignment to turn the GAIN block ON and OFF with the pedal motion. Next I added the WAH block and created its expression pedal assignment. I saved the preset and now when I return to the preset and rock the pedal back, the GAIN block does not change bypass states as it should, but this block is transparent to the signal so it doesn't matter. The WAH block does turn ON and OFF as its supposed to because its assignment isn't the first one created within the preset. I submitted a Support Ticket for this bug and the tech replied back that he was able to duplicate the problem so he has notified the folks in software. He also said he was surprised that this hadn't been reported already. I wanted to create this thread in order to share my workaround just in case anybody else besides me has been pulling their hair out trying to get this function to work properly.

Hi Helix Stadium XL Team, I own the Helix Stadium XL and often have it on my desk when working with it and not using in a live playing situation. I do this because like many of us, I'm not able to continuously lean down to use it while on the floor. I know I can use the Helix App, which I also use and think is really well done! When I'm working with the Stadium XL on the desk, I can use my 8 switch MIDI foot controller on the floor and between what I can reach over and physically tough on the XL and what I can do with the MIDI foot controller, I can simulate just about everything I want to do when testing things out to be ready to use the XL in a live situation when I move the XL to the floor. One big missing feature is having the ability to map switches on my MIDI foot controller to directly to each FootSwitch on the XL using CC MIDI commands (ie: MIDI CCx for FootSwitch 1 on the XL, etc). I see that this feature was available in prior Helix version, but seems to have been explicitly removed from the XL. I realize I can map midi from the foot controller to blocks that are assigned to foot switches, but what I'm talking about is the ability to map a foot controller switch directly to a specific Foot Switch on the XL, as was available in prior Helix models. Any chance you will bring this back? Thanks, Dan

Since your device is new you have no personal/ custom presets and hence no need to perform a backup first. However the backup is a mandatory part of the firmware update procedure, which you will appreciate when you DO have custom data. A firmware update does not overwrite any of the existing presets in the device, neither custom nor factory presets. It does not automatically install any factory presets. So if you want any new factory presets you should perform the recommended factory reset, which does install them. However, it also deletes any custom presets. That’s where your backup comes in. My standard firmware update procedure is: 1. Perform the firmware update, which includes the mandatory pre-update backup. 2. Perform the factory reset, which includes installing the factory presets associated with that version of firmware 3 Restore your backup file created in Step 1, but selecting not to install setlists 1, 2, and 8 (the factory presets). After those three steps you will have the new firmware, the new factory presets, and all your custom presets, Global Settings, IRs, and Favourites that were on your device before the update.

1) Besides the input impedance there is an input gate in the input block. Disable it when you compare the effect of rolling back the guitar's volume pot. 2) If you want unity gain in your 4CM patch (which means the amp's input receives the same level that it would get without HX in the chain) set Input Level, Send/Return and Output Level to INST in Global Settings > Ins/Outs. Use default FX loop block settings in your 4CM patch and crank the VOLUME knob. 3) Here is how you A/B test the actual impact of the HX Stomp to the sound of your amp: HX Stomp has an analog bypass (aka true bypass) that you can use to compare the impact that the HX has when switched in. To do this right you need to do the following steps: create an empty patch double check that the input block and output block settings are default settings set Input Level and Output Level to INST in Global Settings > Ins/Outs set Global Settings > Preferences > Bypass Type to Analog set Global Settings > Preferences > Tap Function to AllBypass crank the (physical) VOLUME knob use a short cable between HX Out and the amp's input Now you can compare the actual impact of the HX Stomp to the sound of your amp toggeling between Analog Bypass and the empty patch using the Tap footswitch in Stomp Mode. 4) HAVE FUN!

Aha …. I think I’ve sussed this out (I only just noticed this glitch). It seems that when importing a preset the volume pedal doesn’t copy over properly. Try clearing the volume block and then adding it back in! Bit of a nuisance but worked for me. Let me know if it works for you

You’ve obviously put a lot of time and thought into this.For maximum effectiveness (I.e. to have it noticed by actual Line 6 developers) you should repeat it in the Product Feedback area, which is here: https://line6.com/company/contact/productfeedback/

A total noob with a cave of forgotten gear? Find the error.