Leaderboard

Hi, Just wanted to confirm that the issue is now resolved! The registry workaround didn't work, but I downloaded Microsoft's Windows MIDI Troubleshooting and Repair tool: https://github.com/microsoft/MIDI/releases Interestingly, the tool showed that Windows was still running Mode 0 (Windows MIDI Services) despite the registry changes. I switched to Mode 1 (Legacy MIDI) using the tool, restarted Windows, and Workbench HD immediately connected to my Variax through the Helix Rack! The nice thing is that I can simply switch back to Mode 0 when I'm finished using Workbench HD, so there's no need to permanently disable the newer MIDI functionality, allthough it would be nice if you can point me to a more permanent solution so I don't have to restart my pc. Thanks again for pointing me in the right direction! Hopefully this will help others experiencing the same issue with Windows 11. cdegardin Oct 12, 01:16 AM Hi, there was a Windows 11 update for MIDI2.0, which led to some applications and MIDI ports not working anymore (like Workbench HD) But HX Edit was not affected by this. If you do this workaround Workbench HD should connect again : 1. Open Registry Editor (regedit.exe) 2. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 1. Create a new DWORD (32-bit) Value named: UseLegacyMidi 1. Set its value to: 1 1. Restart Windows. It should now connect https://microsoft.github.io/MIDI/kb/how-to-change-api-mode/ In Helix Rack, make sure to enable MIDI over USB in the Global Settings/MIDI&Tempo WOrkbench HD can connect via Helix Rack, but not Line6 Central (even if you see the Variax, updates are not possible that way, this is normal) Best regards Line 6 /Ampeg Support Europe

Thanks. So I’m not going crazy…. at least not yet …. just a little slow on the uptake ;-) I haven’t used IRs since the OG Helix new Cab engine was released so I missed that change.

Again...you can change what IR is loaded per snapshot. This is a screen shot from the online manual link I posted above. It was available on the OG Helix devices, also. Audio dropout was always minimal on the OG devices in my experience. I haven't tried on the stadium yet, so I can't tell you if it's noticeable or not.

agree with you

Just want to check the basics….. You don’t mention your Variax model. Is it JTV or later? If not you need to be using the original Workbench program, not Workbench HD.

The Line 6 Central app allows you to install older firmware versions.

I've never come across something that doesn't work because the MIDI is too intensive; and they publish the setlist and song MIDI info against each song, so it's clearly designed to select a setlist and song within that list. I've submitted a bug report, definitely worth you doing it too, the more they get the more likely they are to fix it

Good day Stadium XL Friends --- I know this has been mentioned numerous times, at least back shortly after launch, but could some attention be given to try to 1) try to fix whatever keeps dropping my WiFi from Stadium XL to Edit, or 2) make it possible that we can have continuous USB connection so we don't drop connections. It always happens when you're really trying to get some stuff loaded for a gig, or some other project that works easier for many of us when we are connected to Edit and not wanting to manually do several items. For example, I'm on a 1 Gig line that usually will report speeds around 700-800mbps, thus you would think there's plenty of headroom to handle Helix Stadium communications. Today I have rebooted computer, rebooted the Modem and Router 2x, turned off and back on the Stadium XL unit 6-7 times, restarted the Stadium Edit 6-7 times. It would make my day if I could simply keep my Stadium XL linked to Edit throughout most of the day, like most of my other wireless devices stay connected. Please don't take this as griping or whining. I'm 64 years old and have worked with computers on the job, etc just like many of you for years. I just wish this could be resolved. The Stadium XL is a great product, that's why I've chosen Line 6 every single time since the POD 2.0 Bean, POD X3 Live, XT, HD500 series, original Helix in 2015 and now the Stadium XL! (Oh, I forgot I owned a Spider Amp years ago and the Vetta II Amp about 20 yrs ago! Now that amp was a beast!) Thanks for listening and I hope others see this issue as well, and that I'm not the only one! Kind regards, Geetar42

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.

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

Unlike some other devices, the Helix Floor/LT/Rack allow any preset to be placed in any slot. There are 8 "Setlists" which are simply "BANKS" of 128 presets. Backup the Factory setlists if you think you might need those presets, then copy a BLANK SETLIST over the FACTORY setlists and you've got 1024 (8*128) potential preset locations to use any way you like. If you need to quickly get from a preset in SETLIST 1 to a preset in some other setlist, use MIDI.

Helix LT supports the concept of Setlists. You can create up to 8 Setlists, each containing up to 128 presets in Banks 1-32 and Preset locations/slots A through D. You can fill those preset locations in any order you want, and fill them by creating new presets or by copying existing presets including Factory presets. Check the Setlists and Snapshots sections of the manual. Come back with specific questions as you do the following: The idea is that you can prepare your device for a gig in advance by creating a Setlist for the gig. Name the Setlist whatever you want (e.g. Pub Saturday). Begin populating your setlist with presets, starting with creating/copying the preset you want to use for your opening song in Preset 1A. If you want to change your tone for various parts of the song, say for the Intro part vs. the Verse part vs. the Lead part, you use Snapshots to create those different tonal parts within the same preset. As you switch snapshots for the various parts of the song there is no audio dropout. When satisfied that your first song is as you want it, move on to your second song using Preset 1B. During the gig there will be a brief audio dropout as you switch presets. That’s why you make the switch between songs, so nobody notices. Again use Snapshots as desired. Then move on the Preset 1C for your third song, and so on for all songs in your set. And don’t forget to include your encore song(s) at the end, after the standing ovation! Prepare your device in advance for the entire gig, arranging your presets in the order in which you plan to play the songs to make the tap dancing of preset switching as simple and as least distracting as possible during the gig. While your device will only hold 8 Setlists at a time you can store as many different Setlists (and Presets) as you want on your computer using HX Edit and swap them in/out as desired.

Not long in the tooth. Just short in the gums.

On another forum a few days ago, we heard that 1.4 was close to release, and 1.5 is in dev (or something to that effect). I'm going to guess 1.5 is still happening this year.

FYI…. Since this is a paid utility please make sure any further posts promoting it are made in the Promote Your Patches area of this user forum, per the Terms of Use. Line 6 created an area specifically for users to promote their offerings rather than posting in the product specific forums. https://line6.com/support/forum/96-promote-your-patches/

What is a "Preset Stomp button"? The HX Stomp has: Buttons: VIEW, ACTION, PAGE/PAGE Footswitches: Footswitch 1, 2, 3 Knobs: Knob 1, 2, 3, upper Knob, lower Knob, VOLUME

Driver installed?

LT has only 8 assignable switches. But you can disable the up/down buttons with a hack I provided in that video above. However, still you are stuck with exactly 8 buttons that you can assign things to in Command Center, no way to make the up/down buttons do anything else on the LT.

You need to do this in the User preset area, not in a setlist. When done within a setlist it simply creates a copy of the original, with the same name, on the assumption that you plan to use the same preset at different points during the set. If you want to use a new preset in that particular Setlist slot you need to create the new preset in the User preset area, use the Save As operation to rename it, and then assign it to the Setlist slot.

I am sorry that you can't get it to work seamlessly. It's weird that it doesn't return you to the first amp channel (Snapshot 1) when the Preset loads Maybe reach out to Line 6. I'm sure it's something simple that we just missed. It always is. Let me know if you get it solved. I'd love to switch to Snapshots

So far as I am aware, Snapshots can change the parameter settings of a block, but not the device represented by the block. On Fractal modellers, you can have up to four different devices (amps, drives etc) within the channels of a block, and the channels can be changed with snapshots or scenes. With Helix or Stadium, it is one device per block within a preset. A different IR is a different device, and only one can be assigned to a block.

Has anyone followed the following tutorial link for the 10 tutorial videos? While it may not be exactly the learning path some may want it is free for now.

Thanks silverhead, been a while. BTW, I used to be psarkissian. Keep up the good work.

You have to set up separate Tip and Ring Commands in Command Center on the same preset/snapshot. Go into Command Center. On two separate Lightning Bolts choose Ext Amp Set up one as: Tip - Open. Set up the other as: Ring - Closed Hit Save. See if that's the combination for CH2 using the footswitches

Update: Helrig 1.1.6, plus a desktop beta update Helrig 1.1.6 is out, and the desktop apps (Mac, Windows, Linux — direct USB) are now in beta as well. Beta so far: 1,667 live edits sent to real pedals, 93 presets read back, and 32 connections in the first two and a half days, with one pedal lock-up (recovered with a power cycle) and 11 issue reports that already turned into 46 fixes across 9 builds. Big thanks to everyone testing it — full release is a few weeks out. On the web app, 1.1.6 adds full Command Center support — you can see and edit every MIDI, footswitch, EXP pedal, and Variax assignment on a preset, laid out to match your device's own Command Center. Also new: copy/paste for blocks, deleting and copying snapshots, editing every snapshot's value for a parameter from one row instead of switching back and forth, and Variax settings can now go on any controller. * Helrig is unofficial and not affiliated with Line 6 or Yamaha ("Line 6," "Helix," and "HX" are trademarks of their respective owners).

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.

For item 3, you’re definitely not the only one. Other Stadium XL owners have reported the same problem at outdoor shows and under bright stage lighting. This article summarizes those reports and a few practical things to check: https://helixguitar.com/articles/helix-stadium-xl-scribble-strips-bright-light I haven’t seen a confirmed inverted-color option or fix yet.

Hi all, I am really tired of this unit, honestly. I mean since nearly one year when I bought it the WIFI issue is still not solved. And also the snapshot values seem to randomly change (and has also been reported since months). I need to prepare for a gig and I have to work on about 40 to 50 patches with various parts. it is a nightmare. And I do not want to read about what Line 6 achieved with the few new amp models in the recent updates and the clones and showcase. These bugfixes are the bread and butter of a unit like this. You simply still cannot use it because it is not reliable and all the work takes three to four times longer. Don´t know if anyone of Line 6 is reading this post but I think I speak for a lot if not all users who simply want a working unit first before you work on more features.. Sorry for my frustration but I am thinking about selling it.. The overall concept and architecture is so great but it is too much to deal with.. Cheers..

OK - now I have a bit more informatrion, I've been able to find the information I was after. Don't ask about compression - ask about Focus view! https://manuals.line6.com/en/helix-stadium/live/the-focus-view#focus-dynamics

Thanks - yes that makes sense. I now aee 2 displays - one on each side of the pedal image. There are no lables, but I'm assuming trhe left side is displaying the compression and the right is output level? I'll try to find more info - I did try every way I could to ask that in the docs search field. I can't find anything.

Nice, I can see how that would work. Thank you for the response. I have been reading your posts and appreciate the videos! Thanks for all the info! That goes for all who post on here. It's a nice community (when we read the manual! HAHAHA)

The Auto Connect toggle at the bottom of the start-up window is set to On and lit green, but I am forced to connect manually. Except... Totally unlike the experience which led to my Friday post above, I had zero problems with the connection yesterday and it was on all day! WHAAT?! It even connected automatically (which it ironically did not do this morning). It made me wonder if Line 6 had surreptitiously sent an update. The only thing that I know changed since Friday is a Windows update. If that was responsible, then I'll take it. If today is similarly successful, then I will try the Carvin wireless pair again and let you know.

Nothing to lose, and you will get an answer on that point.

Yes. See the MIDI section of the manual describing Transport Control using Global CCs.

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.

There is no need for this this, because we have snapshots and stomps to change our sounds, and there's no need to go to individual presets while you play. But that's besides point... The only thing you can do is create a bunch of "chained" presets. If you use 8 presets, then for each of the 8 presets, you can customize the buttons to take you to the other presets. This can be done in Command Center. Command Center allows you to customize your "Stomp" mode view. In the same view you can mix and match whether you want to turn on/off individual stomps, change snapshots, or go to other presets. What we are trying to do is have one preset have buttons that will go to other presets from within its "Stomp" view. 1. Go to one preset, open up Command Center, and make sure that 8 buttons take you to appropriate 8 presets (including the current one). 2. When doing this, make sure when one button is pressed, the others don't default to "next snapshot" or something like this. There is a global setting you can disable to not have it default to that. But it's basically intentional: you press one button and now your layout can be completely different. In essence for every preset, in "Stomp" view, you have 8 different layouts. If you want all 8 to look the same, then click each button and re-assign what the rest of your buttons will do. Since you are not using snapshots, this shouldn't be a problem, but still worth checking so you don't have a "dead end" screen where you can't go to any presets at all. You need to make sure you can go to every presets from every other preset, so that's 8*8 combinations---have fun testing that :) But if you are using snapshots, then see what your stomp screen will look like after you go to a different snapshot than the default one your preset is saved with. 3. Since you have assigned a bunch of buttons in your "Stomp" view, you can now change their ring colors. 4. Once you've successfully set up the layout for one preset, so that it takes you to the other 7 presets and recalls the current preset -- repeat the same exact steps for the rest of your presets. On Helix Floor you have "10 button stomp" mode in Global Settings, so you can chain 10 presets instead of 8. Beware, that if you reorder your presets, this setup may not work as intended. Now you've created "wormholes" that link 8 presets from each other. Is it possible? yes. Would I recommend doing this? Again, no, because nobody uses presets to change sounds, when we have snapshots and stomps. And by nobody, I mean touring musicians who don't want gaps in their sound. And yes I'm aware of the "gapless preset switching", but you give up 50% of your DSP for that.. Not worth it. I have been using Presets for every song. Or sometimes one big "kitchen sink" preset that does all my sounds. I change the sounds with snapshots, and use the expression pedal to control different things. Never had the need to do anything else, and I use a ton of effects and tricks in my playing.

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

I was having the exact same problem described in this thread with my Line 6 Spider V30 MkII. After a Windows 11 update, Spider V Remote stopped detecting the amplifier and showed: "No Device Connection" The USB connection itself was working correctly: the Spider V was still recognized as an audio interface and worked normally with the ASIO drivers. I also tried: Different USB cables Different USB ports Reinstalling the Line 6 drivers Reinstalling Spider V Remote Older versions of Spider V Remote Running as administrator Compatibility mode Factory resetting the amplifier Nothing worked. My system is: Windows 11 25H2 OS Build 26200.9168 Feature Experience Pack 1000.26100.344.0 Line 6 Spider V30 MkII The solution The problem appears to be related to the new Windows MIDI Services stack introduced in recent versions of Windows 11. Microsoft provides a compatibility option called Legacy MIDI API Mode, which allows older MIDI applications/devices to use the previous Windows MIDI stack. I enabled it by adding the following registry value: Open Registry Editor (regedit.exe) Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 Create a new DWORD (32-bit) Value named: UseLegacyMidi Set its value to: 1 Restart Windows. After rebooting, I opened Spider V Remote, connected my Spider V30 MkII, and it immediately detected the amplifier and worked normally again. So if your Spider V Remote suddenly stopped detecting your amplifier after a Windows 11 update, especially on Windows 11 25H2, I strongly recommend trying this before replacing cables, reinstalling drivers, or resetting the amplifier. Important This does not appear to be a problem with the USB audio functionality itself. In my case, ASIO/audio continued working normally while Spider V Remote could not communicate with the amplifier. I have not seen an official Line 6 statement confirming this specific compatibility issue, but the timing and symptoms strongly point to the changes in Windows MIDI Services. If this fixes the problem for you as well, please report your Windows version/build and Spider model in this thread. Hopefully we can establish whether this affects Spider V users broadly and give Line 6/Microsoft enough information to address it. Edit: To undo the workaround, you can change UseLegacyMidi back to 0 or remove the registry value and restart Windows.

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

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

Yeah, I use my Axe FX III MkII Turbo for bigger stage gigs and bring my rack and FC-12 + 2 expression pedals pedalboard.

I agree. It would be nice. I do have a friend that is a one man band and he uses a rack with "within reach" access.

Glad to see this thread. Been having the same issues with my Stadium. MacBook Pro - Tahoe 26.1. Strong internet connection. Both Stadium and MacBook are connected to wifi without issue, just no communication between the 2. Initially it connected, but would drop connection after a few minutes. Now it won't even connect to stadium, despite it showing as available on the app. Would love to forgo the wifi and connect directly with a USB line directly into the unit, however that feature does not appear to be available other than to update firmware.

Mine periodically disconnects. My WiFi signal is strong, so it must be a bug.

Change DISPLAY SETTINGS>SCALE AND LAYOUT to a higher setting. This affects all of your apps, but it's all I can think of besides changing the screen resolution, which never looks right.

This post explains one cause of firmware updates/recoveries failing for the Line 6 POD Go. Hope this can help someone. TLDR: prior to updating firmware, shutdown any and all applications that could conceivably use audio. I rented a POD GO a couple of days ago, and the firmware was still at 1.40.1, so soon as I connected to POD GO Edit, it prompted me to update it to 2.0. Unfortunately the firmware update failed. POD Go Edit said it "updated successfully", but the screen on the POD GO device itself just continued to say "Updating..". I'm a software developer, and I know interrupting a firmware update is a big no no, so I went away and came back 30 minutes later. It was still stuck on "Updating..". At this point I sighed, turned the unit off and on, and it wouldn't boot past the "LINE 6 POD GO" screen (still shows firmware at 1.40.1). I tried a factory reset, but it doesn't get past the "Will reset Globals, Presets, IRs..." screen The steps I took were as follows: installed Lined 6 Updater It doesn't see the device. Also tried another USB Cable and alternate USB port. Tried booting POD GO holding "Page >" button. Line 6 Update now sees the device, but the firmware update fails. Will try a different computer later. Tried a different computer. No luck. (this is actually very interesting, which will become apparent later) The solution: Actually read the instructions presented in the Line 6 Updater (I know, I know, RTFM!). The first instruction provided by the Line 6 Updater is: "Shut down any programs that use audio or connect to your POD Go device, like DAWs, iTunes, Spotify, video games, etc." So I opened task manager, and saw that Spotify.exe was actually running in the background, so I killed that. I also killed MS Teams and WhatsApp Desktop. Tried the Updater again, and it worked! The reason I mentioned earlier that it was interesting the update failed on the other laptop, is that it didn't have any of those applications installed. It did however have Discord installed. I suspect that was the culprit.

Opinions are like a brain.... some have it. LOL

Thanks for the feedback datacommando Unfortunately, reinstalling the firmware did not resolve the issue with the controller. The Helix rack unit definitely senses the rack controller because it prompts for the for the control to be updated as soon as it is plugged in. But when you select OK, it pauses at that point and never goes beyond "Starting Helix Control Update..." The controller lights up but there are no scripts and the switches do not have any effect. Re: NEVER, EVER, UPDATE TO A NEW FIRMWARE BEFORE AN IMPORTANT GIG, RECORDING SESSION, AUDITION OR ANY SITUATION IN WHICH YOU GETTING PAID MAY BE INVOLVED, ETC. In this case I got to the gig, went to plug in the controller and was hit with the "Helix Controller Must Be Updated To Work Properly" prompt. Prior to that gig I had not made any firmware updates. So there must be something wrong with the controller itself. Very concerning as I would not want to experience that before a gig again. Re: EDIT: In the event that none of this works - contact Customer Support. I have contacted Customer Support and it sounds like they want me to take it to an Authorized Service Center. I could be without the controller for another 2-4 weeks (if they can fix it). Super bummed. Back to the old analog pedal board for the next round of shows. Hoping this is a one off issue and not something I have to worry about before future gigs.

Apologies for the massive delay, guys. Real life (and trying to herd the rest of my band into recording the album) has got in the way ;) Anyway, here are the instructions for installing and using Helix Native on Linux (the process works with Ubuntu 17.10, but also 18.04 and hopefully later versions), specifically with the Windows version of Reaper: Once that's done, reboot (if you missed that step) to get the lowlatency kernel running and run Cadence; you'll need to configure your interface (usually just click Configure, select the interface from the dropdown, then set the number of inputs and outputs and configure the buffer for your desired sample rate and buffer size - it's all in there). Fire up Reaper and open the Tools -> Preferences dialog, select Device in the left hand side, and select WineASIO as the driver, then select the inputs/outputs you want as you would if this was running in Windows. Create a track, open the FX dialog, choose Helix Native and you're off! This is also the start of the process for getting it to work with natively Linux-based DAWs (using the lin-vst wrapper), but I'm afraid that's going to have to wait for another day. EDIT: For what it's worth, when I originally did this I had the same problem as @eprincen with keystrokes not being accepted by the Native window. However, with the latest version of everything (Native included), it works flawlessly.

I am trying to buy the Model packs through Paypal and I am getting this message. I am using paypal for years and I have never seen this message before. WTF ? My billing address is in Germany Am Ölbxxxx (I am not goint to reveal it here) 90403 NÜRNBERG Primary, Billing address