Leaderboard

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:

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.

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.

Further to the above: I also have ToneX, Genome and THU. That gives me access to 4 of the 6 major players in the capture/profile world. Proxy through Stadium Native NAM through Genome (though Genome isn't necessary, I could just use the FREE NAM player, but it's nice to have it.) ToneX THU Rig Libraries All with a choice of (potentially) 1028 different Helix pedalboards and using Helix as MIDI controller and Reaper as DAW/VST HOST. What a wonderful world we live in!

Before the "along came poly" release, I had one song that needed standard D tuning. I used the regular transposer "simple pitch" for it and it sounded just fine. It is not the "poly" effect, but it can definitely transpose multiple notes at the same time, absolutely no problem. If you just play distorted chords, lots of power chords, it will work fine. For all your shimmering clean stuff, you can forget about it, it will be glitchy. So the old transposer is just a little bit less accurate, but works just fine. Try it. Regarding the poly capo, yes it does take up a lot of DSP, but I managed to rearrange all my stuff on the Helix: moved stuff around and down to the 2nd line, so I can have a reasonable preset with all the necessities no problem. I played with a singer who often changed keys, so I always had a poly capo in every preset just in case. I like it, it does have some latency, but for 1-2 semitones it works great. Your last option is to get the drop pedal or something similar. People say they work great.

Best YouTube resource I know of https://www.youtube.com/@JasonSadites Best local resource, your ears and playing with (all) things, including order of things, splits, joins etc, expect to find some uncoventional things that work really well and conventional that don't. Think like a recording engineer. Frankly everything else is opinions based on likes/dislikes and gear configurations. My meat may well be your poison, and lead you down a rabbit hole you don't need. Other than that there is about 10 years worth of dicussion in these forums about all of these things, so do some searching, work out who's opinions align with yours or not. My opinions/approaches: 1. I swap out cabs with every amp I use until I find what I want. I use all stock cabs, no IRs. Once I have a cab thats close I change mic's and move them until I have the sound I want. I ALWAY use more than one cab and different types to get the overall tone I want. 2. I don't use global or cab EQ, I use mic placement, and tune the overall sound for the room using the desk. IE very standard recording technique, get the source sound as good as possible with the least interferance/processing. I always fine tune a tone in the mix (I get multitack live recordings from practices/gigs and listen then adjust in real time). 3. Use a metering tool in a DAW or hardware to get ballpark levels, and tune with your ears in the mix - perceived volume is different to measured. That will involve not just gain, but EQ and/or compression. It takes time and you build experience, there's no shortcuts. I run a patch per song across 80+ songs, each with snaps so have got it down now, but it took a while to get there. 4. Not asked, but expect to need to tune patches differently for live vs recording/monitors and/or accept compromise. Your playback system colours your sound more than anything else. What sounds good to you on stage (often) sounds crap in a mix. Just like with analog gear.

Absolutely! Please find the individual tutorials linked by episode below: Episode 1 – Helix Stadium Tutorial #1: Hardware, Touchscreen & Navigation Basics | Noise Harmony Episode 2 – Helix Stadium For Beginners #2: Presets, Setlists & Templates Explained Episode 3 – Helix Stadium For Beginners #3: Blocks, Amps & Effects Explained Episode 4 – Helix Stadium For Beginners #4: Build Your First Preset From Scratch Episode 5 – Helix Stadium For Beginners #5: Snapshots Explained – One Preset, Many Sounds Episode 6 – Helix Stadium For Beginners #6: Routing, Splits & Stereo Explained Episode 7 – Helix Stadium For Beginners #7: Song View & Showcase Automation Explained Episode 8 – Helix Stadium For Beginners #8: Controllers, Footswitches & Bypass Explained Episode 9 – Helix Stadium For Beginners #9: Command Center & Instant Commands Explained Episode 10 – Helix Stadium Tutorial #10: Global Settings, USB Audio & Maintenance Explained | SERIES FINALE

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.

Not ideal but you could pick up an old laptop that runs an old OS that is compatible with the original Workbench program that is compatible with your Variax 700. That will allow you to create alternate tunings and store them with the model in your V700. The Helix LT will never be fully compatible with your V700 but in some cases it will successfully store and recall V700 models in LT presets. However this is not supported and may not work for you.

Now that you've excluded the power supply from the list of possible causes two things come to mind that you can give a try: 1) You mentioned you reseated the "main" ribbon cable. The HX Effects actually contains two primary ribbon cables: The wide main ribbon cable connecting the main processor board to the display/footswitch board. A smaller, secondary ribbon cable that specifically routes power and control data to the upper scribble strip/LCD assembly. If the main processor tries to boot, queries the secondary display board, and receives a short circuit or no response due to a bad connection, the bootloader will crash and force a reset loop. Open it back up. Disconnect both ribbon cables. Clean the gold contact fingers on the ends of the cables using 99% Isopropyl Alcohol and a Q-tip. Ensure they are seated absolutely straight and deeply into their Molex plastic collars before locking them down. 2) Because you just did an update while the unit was in a semi-broken state, it is possible there is a corrupted global settings file or "problem preset" causing a boot crash. Even with blank screens, you can force a hardware reset using the physical switches: Turn the unit OFF. Press and hold Footswitch 6 (top right switch) and the TAP switch simultaneously. Turn the unit ON while holding those down. Keep holding them for about 10-15 seconds. If it successfully clears the state, the boot loop might stop, allowing the displays to spring back to life. Good luck finding the cause of the issue, share if you find it.

Beats silence.

Hey! Just saw this. This is wonderful. I have something similar but it exports to excel as I have a LOT of helix files and wanted to just be able to scan my directories. But they are not as detailed as yours. It looks like you have exposed EVRY Helix setting. I just wanted to let you know that this is really handy for me since my Helix recently died (terminal firmware update that Line 6 has, so far, no good fix for). I have a Stadium now but I have to fire up my DAW (Reaper) in order to see my presets (since HX Edit will not run without detecting the Helix). This handles the Split paths and Everything. I hope that You put something similar together for the Stadium since it is very similar in file structure already. Great Job. I hope that I don't have to pay for this anytime soon!

I'm still confident that there's a third option: It's been delayed much longer than anticipated but it has not been scrapped. I don't believe they are now planning to leave Variax users stranded and just don't want to tell us.

Dear Support, can you pleas give an answer to this question. POD Go Edit 2.50 is designed for INTEL processors. When it will available for Apple chips? Thank you. Best regards Michael

Time to open a support ticket.

Done :)

There may well be a firmware update in the next few days, as there could always be. But it would have nothing to do with v1.3.3 of the app. That was released solely for preset interoperability with the initial release of Helix Stadium Native. It does not require a firmware update.

I've been doing this for years, so the below is Real World experience. DON'T SELL YOUR HELIX! You can't get a quality AI and MIDI Controller for what you'll get for your Helix in today's market. Also, how else can you get 1028 pedalboards? And simple Snapshot control? Keep your Helix as a controller for Stadium Native. I've been playing with this all day using my Helix Floor and Scarlett 18i20. GREAT FUN! Just get an Audio Interface like this: https://reverb.com/item/100017686-focusrite-scarlett-6i6-usb-2-0?bk=eyJhbGciOiJIUzI1NiJ9.eyJqdGkiOiI3M2M0MzdlMC05NzRhLTRjOTktYjMxMS0zMDE4MzRkMzgzYWYiLCJpYXQiOjE3ODU5MDIyMzMsInVzZXJfaWQiOiIiLCJzZXNzaW9uX2lkIjoiMWQwOTU4NDItMTMzNy00ZWEzLWI1MmYtYjc3YWNiYzg5NjE1IiwiY29va2llX2lkIjoiYzk2NDg4MjItMDBmNC00MzU3LWE5ZjAtYWU2YTRiYzQ4NDc3IiwicHJvZHVjdF9pZCI6IjEwMDAxNzY4NiIsInNvdXJjZSI6Ik5PTkUifQ.R1eeojWAS0GsOnnfMkDykzyhsO-TKRJS3AzTLhZmxUM SPDIF (minimizes latency) and MIDI DIN ports are the important parts. LINE INPUTS in addition to the INSTRUMENT INPUT is also useful (see below). Avoid trying to do any of this via USB from Helix as the possibility of USB Ground Loops and noise from switching power supplies like you find in Laptops is a PITA to track down. I've compared using the FX in Helix vs in Stadium Native and there's virtually no difference I can hear. I created a Preset Template in Stadium using my usual parallel Delay/Reverb and LA Studio Comp and assigned the Stadium Delay and Reverb to a Preset Template with CCs in Helix. This allows you to have 1028 pedalboards and you avoid needing to make MIDI assignments for every effect in every Stadium preset. You also have simple control over Snapshots. Now, if you MUST have Preset changes, you'll either have to assign them manually in Reaper or get a MAC and use whatever DAW/HOST application uses the AU plugin format, as VST3 does not handle presets the way that VST2 did. Manual assignment in Reaper is annoying, but not difficult. If you decide to go this way I can explain it to you. If the AI you get has LINE INPUTS in addition to the Instrument Input you can take the audio from streaming apps like Spotify from the HP Out on your computer and record it along with your playing - you're part of the band!

Mine is stuck on a blank green screen. I entered my login info, switched to another screen, and came back to find it blank. I can't tell if it's still authorizing or not. Meh! Update: It registered and started the plugin after rebooting the computer. I did not have to reenter my login info. Guess it was just a server overload. HTH

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.

To get to the metronome, hold down FS6 (MODE). You can stop/stop the metronome from there (I think this is called "More Mode" or "Transport Mode"?). You can save a metronome setting per preset but you have to go back to that FS6 "more mode page" to turn the metronome off/on. I would like to be able to assign a foot switch to turn the metronome on and off within a patch (from the STOMP A or STOMP B configuration). That way, within a patch, I could do all my sound switching and still be able to turn the metronome on/off. Is there a way to assign the metronome on/off to a foots switch? If not, how is the best way for me to request this feature? I would find this setup useful at times in band rehearsal situations.

Long time Line6 owner here. I would like to know when Apple silicon versions of the Pod Go Wireless are going to be available. I keep getting pop-up messages that support for Intel apps is ending soon. Any word on development? Worried that my apps will stop working. Thanks

Hate to make it worse for you, but Sweetwater is now saying expected in December. I'm pretty bummed about this, too. I've never owned any piece of gear as long as my JTV, and I can't use it anywhere near as much as I would like because of battery sourcing issues (you can't find an official battery any more, and I'd rather not risk frying the electronics with something from Amazon). Every pushed back date makes me a little bit more sad.

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

Late in the thread, but I just bought a pedaltrain board and flight case used off of Craigslist. I use two external EPs plus an external volume control with my XL, so I actually had to go with a 32" iteration. The case alone is probably forty pounds, but I've had too many incidents with baggage throwers to want to f around with it anymore. Fortunately the case has wheels.

I feel so stupid!! Now I realise that they are actually working! I don't know what I was thinking. I guess I was too much comparing the screen to the Stadium XL tutorial! I apologise! Thank you for your responses <3

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

The OP is asking about controlling two amp parameters with the switches: channel and hi/lo. I may be over complicating things or maybe I just don’t understand but I think that requires 2 TRS cables and switch assignments in the XL: one for Control A/B to control channel selection, and one for Control C/D for hi/lo selection. I’m not sure how you get both of those cables/signals into the single TRS jack on the amp while maintaining differentiation. EDIT: I think I misunderstood how the Control jacks work, and dandesy and maxxlines are correct. I now think you only need one TRS cable in a single Control A/B jack and assign two switches in Command Center for Control A (channel) and Control B (hi/lo). Sorry for any confusion I may have caused.

I like the way that when you update a preset, it updates that preset in all set lists (since it is a pointer)... Would like to see that as an option for the blocks as well. If you are making edits through the HxEdit Stadium software, after you hit save, reselect the preset in the setlist (which is still on the left) and it pulls in the setlist on the device. So I hit save, then double click the preset on the left (in the setlist) and the floor device has the current set list available.

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

I have progress but not complete success yet, and some important info that I originally thought might not be important. This started with a shot of Fireball getting kicked onto the unit. Wiped it off at the gig, didn't seem like a lot of liquid but it probably got in around the displays and maybe footswitches. (This was near the end of the night and the unit kept working through the last couple of songs). At home the following day when it didn't work right, I opened it and discovered the disconnected ribbon cable (possibly caused by my singer shaking the unit after wiping it) and assumed that was my actual/ only issue. After posting this I did notice sticky areas and in addition to your 2nd ribbon cable suggestion I cleaned the boards and the displays with isopropyl (once or twice over with a soaked toothbrush) and let it dry for a day. Today the displays are working again and I thought I was all good but it's still stuck in a boot loop. I tried a reset (tap +6) and another force update using line 6 updater. It updated to 3.8 but still keeps rebooting. I think I'll try to clean it more thoroughly (also will use 99%, this was 91%). AI suggests I may be screwed at this point (component fried) but it's worth a try.

Thank you sir! Oddly, when I plugged everything in this AM and opened Workbench HD, it saw and connected to my JTV immediately. Go figure!

Check your global settings. If you have the expression pedal 1 and/or 2 persist by snapshot, then if you change snapshots it will reset to what the expression pedal value was when you saved that snapshot. That's a feature on the OG Helix. I used to hate that feature, but now I actively use it. I used to have the expression pedal persist by preset. Meaning that if I switch to a different snapshot, the expression value doesn't reset and remains where I left the physical pedal. So worth double-checking that.

Yes, there probably will be another update at some point because Line 6 has said so. But the timing is not, and likely will not be, known in advance. And OG Helix units have already been left behind in terms of features, capability, DSP capacity, touch screen, etc. …. and that will continue.

Some time ago I submitted feedback requests for the heel-down tuner as well as reversing the colors of the scribble strips, but for anybody else who thinks these are important issues to be addressed I suggest that you chime in as well as it may help to move a solution higher on the to-do list. I'm really surprised that there aren't more people barking about the brightness of the display because they are next to impossible to see outdoors. At the full brightness setting, the active scribble strips are barely legible, and the dimmed inactive scribble strips washout completely. My guess is that the brightness cannot be increased without burning out the OLEDs, however simply reversing the colors would make them much easier to see. My suggestion was to reverse the color of the active scribble strips for higher visibility. The inactive strips would have the text illuminated on a black background, but the brightness would be increase to full intensity so that they can be seen. better Something like the attached image. It would also be nice to have an option to separate the tuner from the tap tempo button. I set all of my time-based effects to the tempo and its too easy to accidentally double-tap the tuner button when activating the tuner, in which case the tempo is changed to some random value. Moving the tuner to the heel-down position of the expression pedal is a very logical way to activate it. Volume goes down, tuner goes on. My Boss GT-1000 is setup this way. Some people might be happy with the shared tuner/tap tempo button which is fine, but it would be easy enough to give us an option for activating the tuner in another manner.

The official method for bringing feature requests like this directly to the attention of Line 6 is here: https://line6.com/company/contact/productfeedback/

…. and also make sure your firmware is up to date. I recall there were some Flag issues in previous releases.

Having been Line 6 user for over 12 years, I am writing my first ever post on this forum to say thank you. Thank you very much! After going round the houses for hours and trying many things, this was the solution that finally got my JTV connected to my computer. For me, I skipped step one as I am not on a Windows 11 version that has those bitlocker settings. I followed all the other steps and it still worked like a charm. From what I've read in various recent posts on this topic, I suspect this "fix" may work for many others.

This seems to be a question about gain staging, which is a whole world of its own. In the digital world there is an opportunity for clipping and harshness to occur at virtually all points in your signal flow, especially if you increase a block's Level parameter above 0db. This can potentially overdrive the input of any following block(s) causing clipping and harshness. The Stadium's Output block will tell you if/when clipping is occurring, as described in the manual. If it is, you need to identify which block(s) in the signal chain is causing it and reduce the output level of that block. In my experience the best way to do that is to bypass all blocks and listen to the effectively dry incoming signal. If the Output block still shows clipping then you need to reduce the level of the incoming signal from external equipment, or address it in the Input block by lowering the Trim parameter. After all blocks are bypassed and the Input Trim is reduced if required, then you begin to turn the processing blocks ON one at a time. I generally begin with the amp . If that introduces clipping at the Output block you need to lower the Gain, Level, or Master level - or perhaps the Tone stack levels - in the amp block. These interact with each other so you may need to adjust more than one. Then I move on to the cab block which can introduce fizz and harshness. Experiment with mics, and Hi/Low cut levels. Once the Output block is no longer clipping with amp/cab active, and you don't find the tone too harsh, you can move on to other blocks in the preset. Continue to activate them one at a time. If clipping appears at the Output block, lower the levels in the offending block. Rinse and repeat until your preset no longer shows clipping at the Output block. Tedious? Yes. But learning how to properly gain stage your signal path is a critical part of preset and tone development. The art of Gain Staging is not specifically a Line 6 or Stadium topic. It's a general audio engineering art/skill. Google and/or your favourite AI agent can help you learn more.

You can assign the same switch as the Bypass controller for both overdrive FX blocks. Manually turn both blocks ON (or OFF) and Save the preset. Henceforth the assigned switch will work as a toggle to turn both overdrives on/off with each press of the switch.

Hi, My V60 has been serving me perfectly for 2 years now but over the past week neither my computer connection or my phone connection has identified the amp. I've tried different cables, different adapters and nothing works. The only differences are my Spider has been updated to 2.05 and my phone app is 2.0 but there is no update for the phone app. Any ideas?

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.

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

I really wanted to use the Stadium XL for my upcoming tour to enjoy the new Agoura amps, but for now, I have to put it aside. To be honest, it is quite disappointing and I never expected this feature to be missing, as it was such a helpful part of the original Helix. I have a repertoire of about fifty songs, all automated via DAW using global MIDI footswitch emulation. For my specific workflow, Snapshots are not a solution. I need granular control mid-song, where different combinations of blocks turn on and off at specific moments. Re-programming all fifty songs with individual MIDI CCs for every single block would be a massive amount of work. Instead of sending one command to toggle a footswitch that controls multiple blocks, I would have to send up to five separate messages every time. Furthermore, even if I wanted to redo this work, the interface makes it difficult. When I touch a footswitch, the screen only displays two of the many assigned bypass or parameter functions. This makes it impossible to see everything assigned to a single switch at a glance, further complicating the process. This functionality is very important for my setup and how I perform. Line 6, please consider bringing global MIDI footswitch emulation back to the Stadium XL!

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

I would rather go the 4u rack size with the big screen for a rack version!!!

Well, I’d give you 100 to 1 odds that it will….. Makes no sense to include a VDI input on the D10 if all it does is supply power to the Variax. And a phrase I recall Eric Klein saying in the launch video when talking about the D10 is something like ‘We’re not going to abandon our Variax and PowerCab owners.’ But, as you say, that’s not 100% confirmation.

I created a patch for fun that was intended to be versatile using snapshots & foot-switches to go from cleans to rock all in a single patch. It's free, it's on Custom Tone (that has descriptors) & the cleaner tones might suit. There's a sound clip too and there's even a funk riff at the beginning: https://line6.com/customtone/tone/5101684/

I had the Helix floor in a pedalboard with many other pedals (now I've the rack, so this is story from the past). Looks cool, but it's gonna be a boat anchor with a humongous footprint. I ended up splitting in two separate sections because there were to much weight, to much torsion on the board and to much movement between velcro and pedals, etc... Was an overdone thing for me. If you plan to add many pedals to this board, I would suggest to keep the helix floor out of it. Helix floor is already a pedalboard, and you could find useful to have the option to use the two parts alone, in situations where you don't need the entire arsenal. My probably useless 2C. :)

This is the link to the Gearbox download. I have it installed on a Win 10 laptop and it still works for me. I see they state, "OS: Windows XP, Windows Vista, Windows 7, Windows 8" but it works for me on Win 10. GearBox Gearbox Installer Version 3.72Released 3/16/10 Works with: GuitarPort POD Studio GX POD Studio KB37 POD Studio UX1 POD Studio UX2 POD X3 POD X3 Live POD X3 Pro PODxt PODxt Live PODxt Pro TonePort DI-Gold TonePort DI-Silver TonePort GX TonePort KB37 TonePort UX1 TonePort UX2 TonePort UX8 This version of GearBox includes drivers which support Windows 7. This single installer includes a complete software package for GuitarPort, TonePort, PODxt and POD X3 devices. It includes the GearBox application (v3.72), device drivers (v4.0.2.3) for all supported devices, the Line 6 Monkey intelligent updater (v1.33) and Control Panel (v3.41). See the GearBox manuals page for step-by-step installation instructions and detailed setup info for use with many recording applications. Full release notes are available here. For owners of eligible Line 6 hardware (other than TonePort DI Silver or Gold Plug-in Bundle or TonePort UX8) plug-in processing requires the purchase and activation of a license from the Line 6 Online Store. OS: Windows XP, Windows Vista, Windows 7, Windows 8 ( 68.00 MB ) Get Download