Leaderboard

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

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

I don’t think using the Helix Stadium vs. any other piece of audio equipments matters. You’ll get more info by asking this question in a forum with a wider (not just Line 6) audience. Not that you may not get helpful info here, just that you’re fishing in a relatively small pool for an ocean-wide question. Budget and required features matters a lot more than Helix Stadium.

People that are happy generally don't always post very much.

New platforms always have growing pains, and it's the early adopters who have to suffer through it. Bugs that didn't get discovered during beta testing are basically a guarantee... doesn't mean it's "junk", though. Personally, I never invest in the "latest and greatest" the moment it's released, for exactly this reason, lol... let somebody else get cranky because their $2K+ new toy has some kinks to iron out. Wait it out, then buy. But that's just me...ymmv. I know most folks voted "give it to us now", but sometimes you gotta be careful what you ask for. Imho, releasing a less than finished product is just asking for problems... maybe it's me.

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

I'd love to know what is NEEDED at this point. L6 (and all the other manufacturers) have created an unsatiable thirst for new with the ongoing updates with zip valuing of what is already available.

I was going to request MIDI note output from the Stadium for a different reason but don't need to any longer. I have a 4Cast MVP video playback box that currently uses MIDI Note input to trigger video playback and cannot use any other MIDI message type to do that. I contacted 4Cast support this week who told me video triggering using MIDI CC messages is a feature in the new MVP firmware now being tested prior to release which is great because the Stadium CAN send MIDI CC messages. This will allow me to eliminate the MIDI message type conversion between Stadium and MVP that I am currently using. Currently, my connectivity chain is Stadium MIDI 5-Pin DIN Out -> MIDI Solutions Event Processor Plus 5-PIN DIN In -> MIDI 5-PIN DIN Out -> 4CAST MVP MIDI 5-Pin DIN In. Once the new MVP firmware is released, I can eliminate the MIDI Solutions Event Processor Plus box and go direct from Stadium MIDI 5-PIN DIN Out -> 4Cast MVP MIDI 5-PIN DIN In. Bluetooth latency permitting, I will then eliminate the physical MIDI 5-Pin cable entirely and go MIDI over Bluetooth with a CME WIDI Master plugged into the Stadium MIDI 5-Pin DIN Out and a CME WIDI Jack plugged into the 4Cast MVP MIDI 5-PIN DIN In.

Check to see that you have the correct Catalyst ASIO driver installed. IF YES THEN: Step 1 - Go into device manager and check the Power Management settings for all of the USB Controllers. Turn OFF "Allow the computer to turn off this device to save power". Step 2 - Go to this article and follow ALL of the instructions. Don't be thinking "blah blah yadda yadda". Just do it. Windows 11 PC Optimization for Recording | Sweetwater If you're still having problems, then: Go to the Korg website and download the most recent version of the Korg Drive Tools: Downloads | KORG USB-MIDI Driver | KORG (USA) Run the Uninstall tool. It will show all of the MIDI Port assignments. Delete all duplicates and be sure that the drivers you need are loaded under port 10. If your computer has installed the 25H2 update from Microsoft, then you MAY need to roll back to 24H2. Yes, Microsoft screwed up again, and rolling back is their recommendation until they fix the problem. If after rolling back, the drivers are still loaded above port 10, uninstall the Root Hubs (Device Manager), disconnect all your USB devices and RESTART the computer. If you lose your mouse/keyboard and have to manually power cycle, use RESTART after Windows boots. Run the Korg Uninstall tool and reconnect your USB devices starting with the most critical. You'll see which port they're assigned to as you reconnect them. This process should fix the problem. If not...

(I know Kemper does not have such a gap at all.), But... Helix always has had a gap when switching presets. So does the Boss processor and most other old-school digital processors. On the Helix, you have snapshots to circumvent that gap, that (annoyingly) is there. Each snapshot is your different sound within a preset, which is your virtual guitar rig. Preset spillover does not yet exist in the Stadium, as I understand. On the Helix, you sacrifice one DSP chip, to be used as a buffer for switching your presets. So you sacrifice half of your signal chain, and have pretty seamless switching between your presets. I never found myself in a situation to have needed this "feature". On the Helix Floor, I actively use snapshots and do not ever have a need or reason to switch presets during a song. Each preset is each own song. There's a gap when switching, but that that's when you stop and start the next song. That's how modellers should be used -- each preset corresponds to each song. Otherwise, you have several presets that can cover all your repertoire, have a preset for each type of song you'll ever need. In my set, when I was touring, I had 26 presets, which I went through on a nightly basis. I organized them in the order of the set, and just pressed "up" to go to the next song. We had 2 songs that were connected, and I just found a "gap", where I could switch to the next preset. But trust me, once you start creating individual presets (which is what I do), there's no going back IMO.....

That's why it's wise to keep your presets nearly identical, minus a few tweaks, extra blocks that you turn on/off. On the Helix, it doesn't matter if you have unused blocks btw, the sound does not suffer, and there's no extra lag with unused blocks. If you redo your signal chain from scratch, then there will be volume / tone discrepancies. Sometimes you won't realize that they are different. Create a "template" preset, which is your virtual "rig", and modify it for individual presets: copy/paste/tweak. That's the best way to use a modeller if you're a touring musician. Otherwise, just use one preset, if you can manage. Once I learned this workflow, I go through all my presets one after another to make sure they are all sounding correct and matched in volume. I've also once had this weird bug on the Helix, where one preset wound up getting louder, even though the blocks were all identical. I wound up redoing it from scratch, and it started sounding like my other presets. Just something to watch out for. In summary, there are so many factors that can create a difference in your sound, that it's best to just keep everything the same as much as possible. My tried-and-true approach that I've used for 6 years on the Helix.

1) add a gain block at 0 db so it does nothing 2) Drag it down to split path 3) Huge volume boost If you check the merge block it has a 3db boost on top. 4) Set the boost to 0db 5) Set both sides of the merge to -3db Sound about equal. Cool, but what about the main volume. Maybe I can just knock that down 6db Nope, it's quieter! I guess there's two questions, a) why would it default to a +3db boost on top of the natural boost from doubling? b) What boost would be the same as -3 on both channels? It's a real little gotcha, easy to overload blocks after a split! S

Thanks for clarifying….. and don’t beat yourself up too badly! -;)

All, I've corrected my wicked ways in the following thread I have deleted my first two posts and posted the simplified method I tripped over after much head scratching and three re-reads within the manual. Please refer to the thread I've linked in this response. Oops jpd

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

Wondo100, The Orange cab that theElevators uses would get you that "in the room feel" most guitarist look for, even if they come close without it. I am using something in the Electro-Voice ZLX-12P family right now for simple XLR mono out playback. jpd

Try using a different amp. Some amps have all these extra controls like "hum", ripple, as mentioned already. These can really get amplified if you have a weird signal chain. In my case I started running a compressor between the amp and the cab, which really improved the feel. But it introduced constant low-frequency hum, which I noticed one day. Well, in my snapshot for the dirty sound, I just dialed down that "hum" parameter to 0, and the issue was fixed. Some amps do weird stuff. Crackle and pop could be from static electricity. I've noticed the original Helix even having its capacitance triggered from static electricity, when it was on a rug. All sorts of menus would pop up constantly.

That's expected and normal, as it mirrors the physical behavior. Combine 2 signals and you get louder signal. I discovered this on the Helix when I added a delay in parallel by accident. Then when I removed it, the preset's level changed. I wound up keeping a delay in parallel as it's easier to manage in the end, and all of my presets have that delay, even if it's not used, for consistency in terms of the level.

In my experience nothing beats the sound and feel of a real guitar cab. So I have been happily using Mooer Baby Bomb with a 12" closed back cab by Orange. People scoff at it until they hear how it sounds. Toured with this great power amp all over Europe, Canada, Israel and the US. We ordered Fender Deluxe for our backline, and I used it as a glorified cabinet with the power amp for 2 weeks in Europe. Worked great.

because: 1. silent stage 2. recording straight into computer 3. snapshots. Go from dry clean sound to lead sound with delay, etc. 4. delay spillover 5. transposition 6. set it and forget it. get the same exact sound each time for my 100's of presets. 7. stereo sound, stereo delay after amp, which in real life would be a giant pain to recreate. But I don't need to reinvent my sound in every preset, because I already know what works for me.

When weirdness happens on digital gear, perform a factory reset. Don't forget to back up your presets first!

I've only noticed one impact from Yamaha on Line 6 product development. They discontinued Line 6 products that competed with existing Yamaha products, specifically mixers (Stagescape M20D), PA speakers (Stagesource L2/L3/LS), and guitars (Variax). There's been no Line 6 development of any new products in those domains since Yamaha's purchase of Line 6. Variax JTV, Standard and Shuriken were already in development, profitable, manufactured by Yamaha anyway (except for JTV), and allowed to proceed. Development of Variax ended in 2018 when next-gen Variax was on the drawing board.

TLDR, I just wanted to contribute one little known fact to this: Yamaha bought Line 6 in late 2013.

datacommando, I normally wouldn't chime in without a comment to the OP, but ... both of those are legendary in my realm. The Yamaha Magic Stomp seems to be either unknown by most or just plain underrated. I seem to remember a couple movies that I thought I heard something similar to the Magic Stomp being used. If only ... Thanks for the walk down memory lane

Just my two cents (coming from a guy who jumped on the Neural DSP/QC bandwagon early in 2020...), I think Line 6 is crushing it. This is a brand new modeler and they have in a short time already made drastic improvements. I understand it's a LOT of money to invest in something that isn't fully developed yet but that's what you gotta do these days. I feel like in 3 months Line 6 has done more than Neural DSP had done in a couple of years. Moving much faster with more transparent timeline and messaging. I love that. I feel happy coming along for the ride with the stadium and find it exciting. Showcase is awesome and something that's never been done. Proxy I am very excited for. I'm willing to go on the journey with Line 6 and have a lot of respect for Eric Klein and company. Me and others with a QC have been waiting 5 years for some things that were promised to happen "SOON" after launch (ie. plugin compatibility), lol. If you need the OG helix with gapless preset switching, I would recommend gigging that and holding off on the Stadium. The OG helix is a fully mature product and there's nothing wrong with relying on that. I have a feeling gapless preset switching is coming...

brunonz, Not to beat a dead horse with all the information already shared in this thread as well as what is out there in the Line 6 world. The simple answer is yes .. the unknown is for how much longer (a year, two years, ???)? "Based on information available as of early 2026, Line 6 continues to support the original Helix Floor and Rack units, even following the release of the newer Helix Stadium series. The company has indicated that the "original" (OG) Helix line will remain in the lineup and continue to receive updates, although the focus for new, high-DSP amp modeling (Agoura engine) has shifted to the new Stadium platform." - deep dive quote When older Line 6 gear was still being sold as new while the Helix came out, I did have a couple updates. I still see new Helix Family (OG HX, etc.) being sold and the word is that any of the OG series will still have firmware updates as long as they are being produced. The Stadium is the new flagship so a higher percentage of development and fixes will be focused on that family. Any of the FX blocks that are non-Agoura and as stated earlier here, any new effects and optimizations that can be ported over from the Stadium Family development as well as glaring bug fixes will be available via firmware updates. It logically follows that the HX Edit program will be upgraded out of necessity to support the firmware upgrades as well. The Helix Floor and Rack as well as the HX series, have been deeply optimized over the past several years (11 for the Helix family). They are still being sold new for a lower price point now. They have been battle tested in the field, so to speak, and still have positive user feedback. They still have support from users and an online following via these and other blogs and vlogs. There are many YouTube videos out there to search for how-to as well as tips and tricks. The only caveat will be the "how long" part. I have not dug into this but you can check with Line 6 for current and add-on warranty programs just to check what is offered for new purchases. That should give you more of an idea what Line 6 will be doing for the OG series. If you get any updated information you can report back your findings to this thread as well. jpd

ericjb, The link below is a good start to getting a good level. The youtube creator, Jason Sadites, has other videos on this as well. hope this helps, jpd

ksaal, Please use the link I have put below for the Stadium forum. Do a search and you will find the answer to your question. https://line6.com/support/forum/108-helix-stadium/ jpd

What there's room for is largely irrelevant. What any of us think could, would, or should be done with the platform moving forward is likewise, irrelevant. The reality is simple...the Helix platform is more than a decade old. For a "high- tech" product, that's ancient. With the pace at which technology currently evolves, 10 years might as well be 100. People want new toys, and companies exist to make money. For proof I refer you to the poll L6 conducted, where the majority clearly indicated that they'd rather have an unfinished product in their hands today, than wait for something that's more polished, with fewer problems. Personally I think that's asinine, but I digress... No company will keep devoting resources to pumping out free udates for units that were sold 10+ years ago, forever. There's no money in it...yesterday's sales don't help today's bottom line. Business is business.

Yes, I had overlooked the FRFR part in my earlier response. The AI directions seem correct to me as far as they go. But I think it has overlooked the desire to use either the real amp or an amp sim at any time. You still need the amp sim block after the FX Loop and you need to arrange for it to be bypassed when the FX Loop is on. You will need to use a Split block after the amp sim with a Cab/IR after the Split to provide cab simulation to the FRFR. I would use the 2nd Output block rather than a Send block for the FRFR signal. The signal entering the Split block should have either the amp’s preamp or the amp sim, not both. Choose/configure the Split block to send the signal through to both paths. One path goes to the amp’s cab while the other goes through a cab sim to the FRFR. Set up your presets to use either your amp’s preamp or an amp sim, not both. For your amp’s preamp activate the FX Loop, and deactivate it for the amp sim. If you want to get really fancy and use either the amp’s preamp or an amp sim in the same preset you might look into using Snapshots to activate or bypass the FX Loop and the amp sim with one footswitch.

brydo, I haven't had this issue "yet". And I am not saying this doesn't have to be addressed at some point in command center. When you use your finger to touch the problem footswitch, assuming you've left the footswitch themselves assigned to press and touch, does a menu popup on the Stadium XL itself and allow you to unassign it? jpd

Lmao... resurrecting a 10+ year old thread to pimp a gambling app. Bravo! ;)

Hi, When your Helix starts to do weird, and unexpected things, then the first thing to try is a Factory Reset. Reset Options Helix Floor/LT Button Combination Description 2 LED light Fun 3 & 4 Test Mode 5 & 6 Global reset 7 & 8 Reset setlists to factory, Keep IRs 8 & 9 Reset setlists to factory, Clear IRs 9 & 10 Reset setlists to factory, Global reset, Clear IRs 10 & 11 Upgrades existing presets to latest format 11 & 12 Clear current preset 5 & 12 Clear setlists, clear IRs, Return system settings to default 6 & 12 Safe boot mode To use Reset Options: Power off the Helix Hold the desired button combination Power on the Helix Release the button combination Please note: Buttons are numbered from top left to bottom right. Also, USB connections can be a world of voodoo and can be very temperamental - never use a USB hub (Note: some USB ports on the front of PCs can act as a hub). Try connecting to a USB port on the rear of the computer, which is more likely to be connected directly to the motherboard. Hope this helps/makes sense.

I didn't try yet but certainly sounds like it will work, I'll prob. try it tomorrow. Thank you for your help, much appreciated. D

Ticket has been filed. Hope they reply soon. Thanks again. Gary

Yes. USB for Audio and WiFi for Stadium App editing. I have been using the Stadium App since the release of v1.2.1 to see what issues still persist and to see if I can re-create them. So far, v1.2.1 looks a lot better than v 1.2.0. But there are still bugs that I have run across. Mainly with Preset/Snapshot state.

I have previously traced this issue to the underlying .hsp JSON file. I am not entirely sure, as I no longer develop these days, but I think that once the file is corrupted, it is not likely to self-correct and the file is permanently corrupted. This SHOULD be a very high priority issue for Line 6. But we must be patient as these types of tracking issues can be elusive, have multiple causes, and be hard to track down and correct. I have run into this issue still in v1.2.1, so it has not been entirely corrected as yet.

UPDATE: I opened up the LT and used a multimeter to test the power supply unit's input and output voltages. These are the measured results: INPUT: PIN 1 to PIN 2: 122 VAC OUTPUT: PIN 1 to PIN 3 12.42VDC PIN 1 to PIN 4 12.42VDC PIN 2 to PIN 3 12.42VDC PIN 2 to PIN 4 12.42VDC Measurements of both the input and outputs were done when the unit did NOT boot up properly, AND when the device did boot up properly and was fully functional with no issues. Lastly, while inside, I made sure all terminal and molex connections were clean and making good contacts: - from the incoming power cable, - throught the rocker switch, - input molex connector on PSU, - output molex connector on PSU, - molex connector on circuit board (from PSU) I have read that there "could" be a startup sequencing glitch that may be causing the problem, but cannot confirm nor know where or how to diagnose this possibility> Thanks again for everyone's assistance.

Silverhead and Datacommando: Thanks for the replies. Silverhead: I did open a ticket and hoping the techs will get back with me soon (and with a means to avoid sending it to a service center). Awaiting their response. Datacommand: I considered a "funky" preset may be causing, or part of, the problem. My thought was to test if the unit would bootup properly with only the factory setting. So immediately after the 9/10 reset procedure completed, and when the unit successfully booted up, I believe that it did go through the "reloading presets" process (with only reloading the factory installed presets and not my library of presets). I say "I believe" because I went through quite a few resets, reloads, restores, during my attempts to resolve this issues, it was difficult for me to remember the steps I did in proper order. However, I do know that I sat through several "presets loading" routines during my attempts, with the belief the LT did this procedure (as it does it without my initiation all other times) - but.... I could not testify that I actually remember that it DID perform this action on that specific occasion. Sorry, its been a long evening of internet researching and trying to find anyone that has encountered this exact problem (and while there have been others with various booting issues, I am surprised that I have been unable to find anyone that has encountered this "every other time" scenario). If I am able to eventually resolve it, I am staking my claim for the right of naming this malfunction. With the unit only having the factory installed presets installed, I turned it off and on a few times, and sadly the issue continued (first time no screen on boot, 2nd time bootup and operationally fine, 3rd time no boot, 4th bootup fine. ad infinitum). After restoring the system backup (with my presets and settings), whenever the unit cycled through the boot process successfully, the "reloading presets" process DID run and all my presets and settings appeared to be installed properly. Since it the problem was repeated on the factory reset AND a restored backup, this may not be an absolute conclusion to remove the presets as culprits, it is moving it down on the "highest suspected" list (at least for now). It is difficult for me to understand WHY it is a predictable problem which occurs on every other switching ON and OFF of the unit. Most electronic issues present themselves in an ALL or NOTHING manner, or after some warmup time, or even after a series of functions or operations accumulate glitches that ultimately lead to some type of failure. If I find the cause of the problem, I will post, and again, I thank you, and other potential respondees that can offer any advice or suggestions. Best wishes and ROCK ON!

I agree... ...mostly. You have never used Reaper DAW. The number of bugs in that software and the inconsistency in it's documentation you can probably count on one hand since it was launch over a decade ago. Best developer I have ever seen. It is THE ONLY software that I will update without even thinking about compatibility issues or bugs. And that is saying something about Audio processing on multiple platforms.

Eric Klein says here https://www.youtube.com/watch?v=eXcLPsrgWso they are aiming for March. The units at NAMM have the Proxy installed.

I routinely squeezed every drop of DSP from the OG Helix (down to hundredths of a percent). And I have come close to maxing out one of the DSP's so far in the Stadium. But I have never had any issues except for the Stadium not respecting the MAX DSP in one of the blocks, that I feel may still be there, but I have not had time to test. It appears that Line 6 has been a little conservative in the their DSP block estimations on the Helix Stadium. It appears to allocate DSP memory per block as the OG Helix did as well. So far my analysis has shown values quite different from the OG Helix which I did not expect. Also, I can clearly see that the FX Loops and Splits have also been allocated more than I thought they were ever on the OG Helix. The Cab block has been maxed out to something similar to the OG Helix but it is a dual Cab block by default anyway so that just simplifies things. I have had no problems since the 1.2.1 update but I have been building my DSP spreadsheet (which I am sure will change if it has not already with the 1.2.1 update) and so I have not properly Stress tested it. I am interested to know of any issues with DSP allocation and bugs.

All, my "SIDENOTE" issue is a known bug and I was informed by Line 6 support they are aware it. It will be addressed in a future update. jpd

That means you are not logged in to your Line 6 account on the Stadium

Okay. I figured it out. WIERD, but I figured it out. I now see that the Stadium XL is connected via USB (USB icon) and the Stadium is connected via Wifi (Network icon). Line 6 has never been perfect at naming consistency!

My brother opened ticket #496504 to report this issue. He was told by Line6 that he's not the only one seeing this problem, but there are not very many. I went to see him yesterday to help him out, because I'm not having that problem. His Stadium is connected to the WiFi and logged into his Line6 account. His Laptop is connected to the same WiFi and logged into his Line6 account. However, the Laptop CANNOT see the Stadium, or loses connection to it after a few minutes. So, the Laptop can connect to Line6 through the WiFi, and the Stadium can connect to Line6 through the WiFi, but they cannot Connect to each other. I submitted all the information to CoPilot AI, including info on the router and ISP. Here is CoPilot's analysis of the situation and suggestions for solutions. Issue: Stadium editor cannot connect or loses connectivity after a few minutes even though the Stadium remains fully online. The failure is isolated to LAN discovery, not Wi‑Fi or internet connectivity. Environment: Stadium on Wi‑Fi Windows 11 editor ISP: Fidium Router: Adtran 854‑series gateway (Fidium standard) LAN subnet: 192.168.40.x Stadium maintains valid IP and Line 6 login at all times Observed Behavior: Editor initially cannot find the Stadium or loses connection after a few minutes. Stadium’s Wi‑Fi remains stable (no DHCP loss, no reassociation) Stadium retains internet access and Line6 account authentication Only local discovery fails; reboot sometimes temporarily restores it Technical Analysis: The Stadium editor appears to rely exclusively on multicast‑based service discovery (mDNS/SSDP‑style). Adtran 854 gateways used by Fidium aggressively prune or filter multicast and broadcast traffic after a short period of device uptime. This results in: Unicast traffic: unaffected Internet connectivity: unaffected Multicast discovery: silently dropped This matches known behavior of Adtran 854 IGMP snooping, multicast filtering, and band‑steering logic. Why Other Devices Don’t Exhibit the Issue: Smart TVs and casting apps use cloud‑mediated discovery or Wi‑Fi Direct, not LAN multicast. They bypass the failure mode entirely. Root Cause Summary: Stadium remains reachable at L3, but the editor cannot rediscover it because the router suppresses L2/L3 multicast discovery packets after a few minutes. Proposed Engineering‑Level Solutions: Add a direct‑IP connection path in the editor (bypasses multicast entirely). Add cloud‑assisted discovery (similar to Google Cast). Add a unicast beacon or fallback discovery protocol to avoid reliance on multicast. Any of these would eliminate dependency on consumer‑grade router multicast behavior and resolve issues with ISP‑locked gateways like the Adtran 854.

I tried to import backing track created on cubase in wave format 24 bit 44100 khz, but the software doesn't allow me to drop the file. Did I miss something?

Updating the firmware with the Line 6 Central application was an incredibly easy and smooth operation. The JTV59 was connected to a new RJ45/USB I-O (the small black one) which was connected to an M4 MBP via the USB-C connector. macOS15.5 The Line 6 Central application immediately recognized the connected unit. After signing in, it notified me that a fw update was available. No hiccups!

Placed orders for the JTV59 with the USB box and a XPS-AB Variax Cabled Power Direct Box Footswitch w/ Power Supply. Fingers crossed that everything will work, including connecting to Line 6 Central and Workbench HD.

Line 6 Updater app will not connect to hardware in a failed state if HX Edit is open and running in the background, also, see bullet point 4 below. See bullet point 4 from the notes below: Updating Helix/HX IMPORTANT! Carefully read and follow the update instructions below. If you don't—and then run to the forums asking why it's not working—the interwebs will make fun of you. IMPORTANT! In the unlikely event that your update fails, please follow the steps below: Unplug the USB cable from both the back of your Helix and the computer. Turn your Helix/HX device off and on. Reconnect the USB cable to your Helix/HX device and the computer. Download, install, and launch the latest version of Line 6 Updater. In a failure state, the device will not connect to HX Edit. Line 6 Updater for macOS: https://line6.com/software/readeula.html?rid=9831 Line 6 Updater for Windows: https://line6.com/software/readeula.html?rid=9832 Select your device and try updating to the latest firmware again. If the device does not show up in Line 6 Updater after these steps, try a different USB cable and/or USB port. If it still doesn't show up, try a different computer Hope this helps/makes sense.