Leaderboard

As it happens I was just about to start a thread about an issue I've noticed with Song selection via MIDI, when I saw this post; My wife and I gigged with the Stadium on Saturday. We used to use Stage Traxx 3 on an iPad for lyrics and backing tracks (when I used a Quad Cortex) and of course this meant having a separate mixer, to run the QC and iPad through. Now we have Showcase we don't need the backing tracks on the iPad, so we have a much more streamlined workflow, with guitar and mic and backing tracks all coming through the Stadium. My wife keeps the iPad however, as she finds it helpful for lyrics, so to sync everything, we use a WIDI Flex Bluetooth MIDI dongle on the Stadium, and all the Song selections, and also the Song Play commands are done through the iPad by my wife (she's the singer, so has free hands). In other words, when she chooses a Song on the iPad, it sends the MIDI command to the Stadium to select the same Song (which is actually the same .WAV files for Backing/Click Track) Then when she presses Play on the iPad, it sends the MIDI command to play that Song on the Stadium, and the lyrics highlight on the iPad in sync with the Stadium, because they are both using the same .WAV files (and the sound output on the iPad is muted for all tracks). The problem however, is that the MIDI command that selects the Stadium PLAYLIST, then the Stadium Song doesn't work; so say I have a Playlist created on the Stadium, for a gig on 21 September, and the Playlist is called '21 Sep'. Each Song within that playlist will have a MIDI command associated to it, that differentiates between a Song in this playlist, as opposed to the same Song within the master 'User Songs'. This is really important, as the Song select MIDI command is based on the Song number within the Playlist. So a particular Song may be number 7 in the '21 Sep' playlist, but might be number 23 in the User Songs master list, and number 7 in that master list might be a completely different Song. By making sure the lyrics within Stage Traxx 3 contain the correct MIDI command for PLAYLIST selection, then the command for Song selection, you overcome the problem of possibly being in the wrong Stadium Playlist, and then have the wrong Song recalled by the ST3 MIDI command, because ST3 should always choose the correct Playlist then the correct Song. EXCEPT... in my experience the Playlist MIDI command doesn't work, and instead of selecting the correct Playlist, then Song, it just plays whichever Song is recalled by the Song selection MIDI message (eg Song number 7) within whatever Playlist you're in, rather than selecting the Playlist you have requested via the MIDI message. Has anyone else had this experience?

I’m not aware of any such thing as Helix Native Studio. I presume you mean Helix Stadium Native. The procedure is a bit different than Helix Native due to the different way presets are handled in Stadium. It is well described in the Stadium Native manual and I suggest you start with that (see Support link at top of this page. Select Manuals). If you are having difficulty come back here with specific details on where the documented procedure is not working for you. Currently Helix Marketplace assets (your paid-for presets?) are not supported in Stadium Native.

Are you using the balanced XLR outs from the Helix to your interface? If not, I'd try using those first and check their ground settings, too.

wanted to share what has worked for me, in case it helps anyone experiencing constant disconnections between Helix Stadium and Stadium Edit on Windows. In my case, when I connected the Helix Stadium directly to my home Wi-Fi, Stadium Edit kept disconnecting constantly, sometimes approximately every 30 seconds. I also tried entering the IP address manually, but the problem continued. What has worked for me is creating a Wi-Fi hotspot directly from my Windows PC and connecting the Helix Stadium to that network instead of my home router. This is what I did: In Windows, I went to Settings → Network & Internet → Mobile Hotspot. I enabled the hotspot. Windows created a Wi-Fi network with its own name and password. On the Helix Stadium, I searched for that Wi-Fi network and connected to it. Stadium Edit then detected my Helix Stadium automatically and connected without me even having to enter the IP address manually. So basically, the Stadium is communicating directly with the PC through the Wi-Fi network created by Windows, instead of going through my home router. So far, the connection has been completely stable. I tested it for around 40 minutes without a single disconnection, whereas with my normal home Wi-Fi it could disconnect every 30 seconds. I can't say this will work for everyone, and I don't know exactly what is causing the original Wi-Fi issue, but I wanted to share it because it has worked for me so far. I'll update this post if I experience any further disconnections after longer testing.

Nobody is able to answer this yet. Neither the Helix Stadium app nor Helix Stadium Native are able to load Helix Marketplace assets yet. That will come in time but no date has been announced. Here’s the relevant statement in the current Helix Stadium manual: As of this writing, Helix Marketplace premium presets and IRs are not supported. They will be, but unfortunately, we have no timeline to share. And in the current Helix Stadium Native manual: Original Helix presets purchased from the Line 6 Marketplace are not supported in Helix Stadium Native at this time.

Yes Helix Stadium Native runs on both platforms and you can use both under a single license.

If I'm understanding you, you can't use Helix as an Audio Interface because the Helix ASIO driver is incompatible with your ARM based laptop? If that is the case, you have two options. Well, 3 if you want to try ASIO4ALL, but it sucks and you won't like the latency. assuming it works, not likely. 1 - Sell the ARM based laptop and get a proper x86 laptop. I know, money is tight and why would anybody want to buy it? IDK, I wouldn't, but you did.... 2 - Look for an Audio Interface with an ARM compatible ASIO Driver. According to the Focusrite website, the 4th Gen Scarlett interfaces are ARM64 compatible. Scarlett interfaces are excellent for home use and much more affordable than many "PRO" interfaces such as RME, and higher quality than cheaper options like Behringer. I've been using a 2nd Gen Scarlett 18i20 for ages. You can use Helix as a MIDI CONTROLLER with Native, but that won't help if you can't get audio into your laptop. You don't need MIDI DIN ports on the interface as Reaper can bring in MIDI over USB. I THINK the L6 MIDI driver should be compatible (it's "Class Compatible" and works fine with my iPad), but you might want to open a support ticket and ask.

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.

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

I have the Stadium XL with my ToneX in the loop. Sonically, I find the Proxy very comparable to the ToneX captures—at least to my ears. Since I play a wide variety of styles and was already using a sort of "pedalboard strategy" with my "standard" Helix, I’ll likely stick with this setup. That means I have six main presets, each with matching pedals (Clean/Pop, Blues, Rock, etc.) and a corresponding Agoura amp—which can even be tweaked per snapshot (something that’s really easy to do since the Stadium update). I have the ToneX pedal in the loop, which I can use to replace the amp if needed. This gives me incredible tonal variety right at my feet, as the ToneX offers so many more amps (and gain stages, plus Bright, Balance, and Fat controls) ready to go. It’s also cool to be able to switch between the Agoura and the ToneX across snapshots (e.g., Clean vs. High Gain). I really like that. So, for now, I’m sticking with ToneX (mainly because of the workflow). If things get really wild, I can patch in my iPad and use NAM within Genome2 as a third option...

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

Ultimately, if you think you can get a sound that inspires you to play more with a Tonex pedal, go for it. The only right answer is the one that you think sounds best. I used a Tonex One with my HX Stomp before upgrading to the Stadium XL. Once I did (and Proxy came along), I didn't feel the need any more mostly because the XL was big enough, sounded/felt fine enough, and I didn't want to carry anything else around lol.

I have around 250 presets. So.... All of them are basically variations on my main core sound. The main settings: distortion, amp/cab, light delay, solo EQ all stay the same. Every song preset that I create has some kind of a quirk, or a unique signature thing. So I start with browsing through the previous presets, pick the one that suits me and tweak. Like for example, I know that preset number 076 has a nice acoustic guitar sound, and preset number 2 in another playlist has that awesome envelope filter. So I go and combine them, copy blocks/paste blocks. It's so convenient! Because for example the envelope filter is so finicky! It works for one song but doesn't work for another, unless I change the setting slightly. I may want to dress up my lead sound with some vintage fuzz in this one 70's song. I may want to add some kind of a synthesizer solo for this other song. Every song has different rhythm, dynamics, and even the same lead sound does not always work -- it needs a different BPM for example, sometimes it needs to be louder/softer based on what the other musicians are doing. I want to handle all the sound changes myself, and not have the sound guy try to guess where my solo is.... My goal is to have the sound guy not make any adjustments to my sound at all, just plug and play. So in short, for the variety of stuff I'm currently playing the preset-per-song is the way to go. Plus it makes the layout so much simpler because you don't add unnecessary junk that doesn't apply to the song. All my lead sounds are almost always in the same position. If I only need 2 sounds, I don't clutter my preset with unnecessary snapshots that I can accidentally step on. If one song has acoustic sound and an electric solo sound--same thing: I make 6 out of 8 snapshots that acoustic sound. And 2 right-most buttons are my solo sound. It makes it so much easier coming out of the solo to just slam on any of those 6 buttons. And it makes it easy to go to the solo by pressing the right-most buttons, one or the other. Sometimes if I'm trying out new sounds, I can add additional options on the top row. When I practice and I notice that I mess up and press wrong buttons, I reposition these snapshots. It all varies per song and how fast the song goes, etc. Sometimes I use the expression pedal to change between rhythm and lead as well, if it keeps going back and forth. Every preset is custom and it's awesome.

Ive talked before about trying to port sounds between the 2 and of course they dont...not even close BUT Lately I have started just using some simple actual physical cabs and can now define why exactly I wrestle so much with the Helix which is of course superior in so many ways... The diff is this: When you plug the HD500 into a physical cab and turn the cab emulation off; When you play, the dynamics are much more direct and the level of soft to loud playing is large...just as if you were playing into an actual amp When you do the same with the Helix, with identical amp models etc and using only an amp...the sound is much more hifi but it just doesnt jump out anywhere near as much as the HD which is really gutsy...the relationship of tone>dynamics is small and compressed. So if you just want really good tone (and fx arent the backbone of your sound); send through a physical cab that you like the sound of...the helix is no match and you will save yourself a lot of bucks Before flaming me or speaking without knowing...try it first...Im happy to send the presets...even dial them in a bit closer. I spoke quite a lot before on the diff between the HD/Helix model of the Fender Twin Vib channel model...this also makes it perfectly clear...the Helix is a step back in actual authenticity of tone in this type of application Im using r88 ribbon to record and its chalk and cheese Im writing this to help others who may be looking for information Conversely I also play classical...in which the helix is much better if you keep a bunch of chips for the mic preamp as they fry by just looking at them. Ive been doing studio workd for 40 years and never had a fry of phantom power ever and that has been with interns hot plugging etc...do it once on the Helix and you will need a new chip. Long live the HD500 for clean/crunch tones with guts!!

When I have my Helix connected to the computer and am running HX Edit, HX Edit frequently crashes and when that happens I cannot change my presets, and sometimes sounds. Restarting HX Edit, then closing it fixes the "stuck" problem. So maybe the fact that you're connected with a USB cable causes this problem. So I'm wondering if you had HX Edit running, which caused this. Or if not, if it's simply the USB cable being plugged in.

Does this happen OUTSIDE of LOGIC - for instance, connected directly to your monitors or through headphones?

add a volume pedal and a wah pedal to an empty preset. Move the expression pedal and see if it responds. Meaning, do you hear the volume change or wah-wah effect. by default, one of them should work, when you drag in these 2 blocks.

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

This is the one I've been most excited to build. For years, I've watched people share presets constantly — links dropped in threads, files passed between bandmates, screenshots posted in forums and groups. It always felt like all of that deserved a real home instead of living scattered across posts and DMs. So now it has one. The Community Library is that home: a real, browsable place at helrig.com/community for every preset someone's chosen to share with the rest of us. If you make tones and want other people to actually find them — this is the place. How it works: press Share… next to Save on any preset, and pick one of two things. A Private link is just for whoever you send it to — no account needed for them to open it, edit it, or download it. Publish to the Community Library instead, and it goes up for everyone — browsable, searchable, sortable — under your own name or anonymously, whichever you'd rather. Publishing doesn't cost you a saved-preset slot either. However many you want to put out there, the door's open. Either way, the link isn't just a bare URL — paste it anywhere, and it shows the actual signal chain as a preview, so people see the tone before they even click. Here's one of mine to start things off — an SRV preset: https://helrig.com/p/DSf372-o4FFU-B3ZhCkRBg Go publish something. Let's build this thing out together. Helrig is a one-person project — not affiliated with or endorsed by Line 6 or Yamaha.

Attached are 2 example presets. Example 1 is the usual way that it's done. Guitar>Helix INPUT Helix SEND 1>5150 INPUT 5150 SEND>Helix RETURN 1 Helix 1/4" LEFT MONO OUT>5150 RETURN Helix XLR LEFT MONO OUT>EVH Hypersonic INPUT If you want to use a Helix amp in addition or in place of the 5150's Preamp you can either place the Helix amp adjacent to the FX Loop with both Bypass assigned to a FS with FX Loop SAVED ON/Helix amp OFF (FS toggles 5150/Helix) as in example 1 or place the Helix amp on the Path 2B Split in front of the Cab as in the second example. There's lots of ways to do this, but in your configuration I think that using 1/4" for your 5150 and XLR for the FRFR would work best. sozorox1.hlx sozorox2.hlx

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.

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.

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

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.

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

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.

A friend of mine is a keyboard player. He is a longtime user of the Kurzweil workstations. His was bought in 2008. He told me he went to try the new ones a few years ago, and they sounded sterile, compared to the "warm" sound of his old one. That brings me to my point of "warmth" actually being low definition and muddiness. There are countless live records from the late 60's / early 70's that sound great, huge, beefy! And in 2020s we have all this HD equipment, and it sounds so surgical, too many details, just lifeless. Could be one of those. As for the Helix... I don't know how people survived with the Pod HD 500 back in the day without snapshots. I would have to rethink my entire approach to switching sounds in some of my songs with doing pedalboard assignment... If not for the sounds, the routing and the switching on the Helix are so much more advanced.

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.

My Spider V Remote program on my windows 10 PC keeps crashing whenever I change the presets. This particularly happens the most when i mess with the cabinet settings for some reason, but it occasionally happens when I change the other settings as well. I've factory reset and updated my amp but this hasn't solved the problem. The message that comes up is "Spider V is not responding". I've also tried running the program in administrator mode and in windows 8 compatibility mode. Help would be appreciated.

I don't know if this forum provides any feedback re: number of times your attached file has been downloaded. Customtone at least gives you that. Users who have downloaded it can also give it a rating for additional feedback. You may hear total silence here.

Hello All, I notice that a lot of people seem to complain about a New Marshall in an update. I am not one of those people. I love Marshalls. Bring them all on... But... Having worked for Marshall in the past for several years and literally playing through thousands of amplifiers... Most of the Plexi Marshalls (and I have owned some and restored several) that are modeled in the Helix don't sound to me like Marshalls, or accurate Marshalls. I have purchased a Marshall 1959 patch from Glenn Delaune. To me, that sounds pretty much exactly like a Marshall Plexi. Listen to them. Glenn has a video on YouTube to hear. So my question is: Why do the Models not sound close to what Glenn made with his patch? I would think it should be in the ball park. Right? Unless I am doing something wrong. I am wondering if the amps that are being used to Model are in disrepair, need new caps, etc. I am not trying to bash the Helix at all. I love it. I REALLY Love it. Just trying to give some honest input to make it better.