Leaderboard

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

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.

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

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.

I suggest, (if you have some DSP available) to put in your chain the X IR you want as separate blocks. I don't know if you can change IR with snapshot but even if you can , there will be a gap in the change due to the loading. That's not the idea with the snapshot functionality. As contrary if you put 2 blocs and active/desactive the desired block with the snapshot functionality, you won't have this issue cause the 2 IR will be loaded at the preset selection.

Open a support ticket.

Use HX Edit to back up your Presets. then perform a Factory Reset. Line 6 Device Factory Reset Procedures | Line 6 Knowledge Base If that doesn't work, contact support.

it took me nearly 10 years to adopt snapshots, mainly out of laziness/stuck in my ways, but when i finally did there was no going back. makes life SO much easier!

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

I don't get this statement. If you can't remove your amp's preamp section from the signal chain, you're doing 4cm wrong. Describe your wiring and attach an example preset that demonstrates this "fact".

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.

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

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.

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

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?

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.

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.

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.

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

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.

I would update the firmware to the latest version now, using OS 26. It is highly unlikely that there will be any future updates so Intel app compatibility won’t likely matter for firmware. I don’t know about Workbench HD compatibility updates. With your used Shuriken you may also need to pick up or keep on hand an older computer, Mac or Windows, just to run Workbench HD in the longer term if it’s important to you.

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.

nlike Standard MIDI Continuous Control (CC) or Program Change (PC) commands—which update parameters immediately—the Note On event generator in the Helix Command Center software framework handles velocity and note-off states via an internal timer queue. ``````````````````````````````````````````````````````````````````` Bitlife hack apkBitlife hack apk

Have you uploaded this to Customtone as well? Might increase the visibility.

1.Check the physical cable connections: Ensure all 4 cables are plugged into the correct jacks: Guitar -> HX Effects IN HX Effects Send 1 -> Laney Guitar Input (front panel) Laney FX Send -> HX Effects Return 1 HX Effects Out -> Laney FX Return 2.Turn ON the FX Loop block: In your HX Effects preset, locate the FX Loop 1 block and make sure it is switched ON (active). Verification: Toggle the FX Loop block on/off. When it is OFF, you should hear no sound at all (or a very quiet clean sound). When it is ON, your Laney's preamp control knob should instantly start adding overdrive.

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.

If you actually READ the article I posted it so someone out there would see it and wouldnt have to bring their Helix BACK or spend HOURS in circles not fixing anything. YES! "t is a well documented fact that the Line 6 Updater cannot connect to a Helix in a failed state, if HX Edit is also open in the background." Clearly! Thank you for also pointing out POINTLESS DETAILS to waste more of someone else's time. If you had read THE POINT OF THE ARTICLE! It says that when your HELIX IS IN A FAILED STATE YOUR COMPUTER WILL NOT ALLOW THE HELIX TO SHOW UP UNTIL YOU TURN OFF MEMORY INTEGRITY, AND CORE ISOLATION. Computers have software built in now to make it harder to do things like BRUTE FORCE PASSWORDs with devices and when you install new firmware the device and computer HANDSHAKE IS CURROPTED NOW. So IT WILL NOT SHOW UP NO MATTER WHAT YOU DO. Line 6 ALSO HAS THESE PROTECTIONS TO STOP PEOPLE FROM MESSING WITH THERE PRODUCTS... If Memory Integrity was ON → the DFU driver was blocked → Helix never enumerated → “computer doesn’t see it The MAIN points are this. Most of that article are just extra things they MAY fix an easy problem that may be occuring that DISABLLING MEM INEG will not. But I DONT SEE ANYBODY ANYWHERE POSTING THAT! So I did.

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

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

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

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

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

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.

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.

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

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.

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.

Could anyone post a picture of what kind of modification they have done to their unit? Is this only a problem with the G10 or also with the G30 and G50?

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