Leaderboard

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.

This biggest point here is this: Line 6 asked the community if they would be willing to wait or get it earlier - most said they could ride it out and get the updates as the bugs were worked out . . . it sounded like most wanted the unit sooner rather than later (I know I did). Since I'm not using it to gig with at this time, I'll push thru the problems for now. Syphus

You have to configure the control jacks: https://manuals.line6.com/en/helix-stadium/live/global-settings#[mediaInline]-Global-Settings->-Switches/Pedals Determines whether each Control jack (A~D) is an expression pedal input, external footswitch input, external drum trigger input, or an external amp remote switch output.

A firmware update was released yesterday. I believe it fixed this bug.

I really enjoy using the Helix family. Over the 10 years I used the Helix Floor, Line 6 came through with feature updates they hadn't thought about that the user forum engaged in discussing then feature enhancements that would work with the hardware and software that where submitted to the developers for review. The enhancements that many users requested using the feedback to developer links had priority over the requests that one or two user only requests. So, the users of this forum would make sure everyone would submit the request to the correct link since Line 6 doesn't monitor this forum for the purpose of identifying fixes and enhancements, as a norm. Software/firmware bugs where addressed as well as more modeling amps, cabs, and effects added to the device. So, now that I am using and learning about the Helix Stadium XL, as I did with the Floor, I am very satisfied with it and know from past experience the Yamaha/Line6 support engineers will get it working as it has been presented or go many sleepless nights to get it working as expected. I am sure we will have even more modeled devices added. For me, I am looking forward to the coming years with the Stadium and hope I can learn to use it to its fullest. jpd

Being a brand new product there are a number of bugs that have been discussed in this forum. As already mentioned, being a support forum that is to be expected. People don't generally post here to report that they are completely satisfied. Also, a bug fix firmware and software release was dropped just earlier today. By my quick count it resolves more than 50 bugs. Some other remaining bugs are identified and workarounds provided. Helix Stadium is quickly becoming a very reliable product. Let us know what you think after you've tried it.

I love mine. Honestly, I thought it was a bit of an unnecessary purchase as I love my OG Helix floor just fine and I had no desire for a touch screen. After getting it, I do not regret it at all. It has some quirks, it has some things I like better about the old Helix, but overall I think it's an improvement and will only get better. Line 6 has said that most folks said they'd rather have it sooner than later even if that meant more features and bug fixes in later updates. I've come to LOVE the touch screen that I initially thought was unnecessary (for me). So yeah, I don't think it's going to be any huge world shattering game changer for you, and it takes some time to get used to the new ways of doing things (set lists, presets, and such are very different now and I do still prefer the old way better, but I'm getting used to the new work flow). I've gigged with it, and it is now my rig of choice going forward. I use it with every band I play with as well as a MIDI controller for my Nord Stage 3, so as with my old unit, it will get used a LOT, but I've gone all in on it now.

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!

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

You’re right - the poll was ‘later with Showcase or earlier without’, but still clearly unfinished with other promised features yet to come. btw…. my earlier comments are my own. I don’t represent Line 6 in any way. They might not want to characterize current owners as early adopters, nor would they say that it was released in early-dev form. Both the initial version and the subsequent Showcase version were released when the features they offer were considered sufficiently robust and stable while at the same time meeting marketplace commitments (release in the fall of 2025). I look forward to many more years of Stadium development and ongoing feature additions and enhancements.

In case anyone reads this later: I contacted Line 6 support. Updating to firmware 1.2.1 did not resolve the issue. Support suggested rebuilding the affected preset from scratch. After doing so, everything is working again.

I can also see why you would be disappointed. My expectations for the current product were not as high. The main reason I wanted it was because I always needed "just one more stomp" on the Helix Floor! This has given me that. Of course I may be wrong (I thought I was wrong once, but I was mistaken:)) however, I believe this model has the potential to open up so many more capabilities, I'm sure some we didn't know we needed! Your AI integration is an example of that. This platform seems to be able to handle things like that. So like Silver said, it comes down to expectations.

Fixed on firmware 1.2.1 / new drivers. As I imagined, was a firmware bug or a Windows driver issue. With the 1.2.1 update I did yesterday, works just like expected. Windows initially detected it as a 1 channel, 24-bit 48000Hz device and I manually changed it for 2 channels, 24-bit 48000Hz. Both ways worked and I confirm stereo recording working fine.

Anyone experiencing this should open a support ticket to officially bring it to the attention of Line 6. Also, no need to reinstall if versions 1.2.1.1314 (firmware) and 1.2.1.3 (app) are visibly installed.

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.

Log. In.

Loving my stadium. huge big fix just dropped like 32 days after releasing the showcase update. looks like most major bugs are fixed. Line6 is obviously working their tail off while pushing forward into uncharted territory. I think they’re crushing it. Hope yours comes soon so you can try it out.

Yeah, there are some things to work out, but it's been a major step up from the OG for me.

I was a helix Floor user and with new product I'm more than happy, the sounds alone, i'm getting really better sounds than with the previous helix, but for the live use i'm still avoiding heavy use of snapshots and other reported bugs... i trust the team and can say that the wait is painful but the reward is coming.... just this past weekend i used the stadium in a gig and everyone on the bar came to me and talked about the incredible guitar sound... that's all I have to say about this topic right now

Right! Where do I start… I love my DT25. I talk about how great it is on my live streams (thousands of viewers). To my friends. To fellow guitarists. I get compliments on its tone etc. However… As of two days ago, the power transformer is now dead! Fuses blowing. Contacted Yamaha Europe and Line 6. The service centre have just told me… THE PART IS NO LONGER AVAILABLE!! WTF??? THIS IS A CURRENT PRODUCTION PRODUCT that has had many known transformer issues… AND YOU CAN’T GET IT FIXED??? Literally said to me I have NO options! Seriously Line 6! What do I do now?

HX Edit 3.82 is the latest version for use with the Helix 3.80 FW. Download it from the L6 website if you can't update from HX Edit. I forget, it's been out a long time.

Hello, To start my setup involves looping via Daw (im using Loopy Pro but, this pertains to all Daws). Stadium is not bad when it comes to sending Midi Commands via Stomp Pedals but it has some gotchas. I wanted to bring them up here for the community and developers in hopes of them being addressed. My first, and the biggest in my eyes is the lack of the Helix Stadiums Stomps responding to LED Feedback. I am seeing you basically cannot get any sort of LED response on HS from DAW states without using a "dummy" block in the effects chain. For Example, If a Stomp is sending Midi CC 2 to a Daw and controlling the play state of a loop, Most Daws will send Midi CC 2 value 127 (loop on or playing ) and Midi CC 2 value 0 ( loop off or stopped to Helix) back to the controller. Helix's LEDs do not respond to this. Where as on most other footpedal controllers, the LED would respond and let the performer know the state of the loop. (this is true for anything being controlled in a DAW, effects, transport Play/Stop ect. Just using loop states as an example) I think we need an LED Feedback Setting per stomp in the command center. Just a simple LED Feedback On/Off toggle that lets the user decide whether to use the feedback from the daw to control the LED. I want to be clear here I don't expect the Helix Stadium to be a deep Programmable Midi Controller like a Mastermind or something but, LED Feedback is a basic feature that almost all footpedals on the the market have. All that said Helix Stadium does respond to incoming MIDI and so my current workaround Is to use a "dummy" Gain Block set at unity gain and, "Learn" the bypass toggle to the LED Feedback coming in. This works but is an incredible waist of resources (imagine if you had 4-6 loops to control we are using up 4-6 blocks to simply make sure the LED is showing the performer whats going on Loop-wise) !! Be careful here if you do this. Pay close attention to whether you are using the mono or stereo gain as this can mangle your signal if you pick the incorrect one !! My first thought when looking for a work around was to use a multi parameter delay and turn the mix down to zero percent and have all of the parameters tied to separate stomps. This would only use 1 block and all stomps would give me the feedback I need. This leads me to the first gotcha I found. The only parameter of any effect, (when controller externally) that will turn on or off the led on Helix is the Bypass parameter. Any other parameter like say "feedback" or low cut" will not change the state of the LEDS if controlled externally by a CC. Only if you press the footswitch on the helix itself will the LED go on or off. Booooo So this is where I stand. A bunch of Gain Blocks hogging up precious recourses just so I can get the little light to go on and off properly on my stomps.. again Booooooo One thing I want to make note of here is that the Stadium DOES respond correctly to CC values which is good! in other words If CC2 is tied to the bypass of a gain, value 127 WILL turn the LED on and even if you send the same value 127 again, it will stay on. Yayyyyyy. It will turn off only when it sees value 0. Yayyyyyyy. This keeps the Daw perfectly in sync with Helix so, points on that for implementing this right! I can't tell you how many multi FX out there just respond stupidly to any value toggling states and throwing everything out of wack. Sooo Yayyyyyyyyy on this. The other gotcha I found I will just mention briefly and I find to be a little less important but it is a thing and for others this could be very important. When you have a Hold function sending a Midi Message from a stomp and a press option on that same stomp, Triggering the hold will also send the press. Boooooo. So lets say CC1 is sent from Stomp 1 and it turns of and off your external Delay. And a Hold sends CC2 on that same stomp turns of your Boost. Well you better want your Delay and Boost turning on at the same time if you trigger the HOLD because thats whats happening. Most of the time on controllers with Hold functions the HOLD Bypasses the press so that you have control over both devices separately but with one stomp switch. Thanks for listening here ya'll. I know its long but, I will say I did fall in love with the Helix Stadium and only have a few very fixable quirks that I very much hope will be addressed. Despite the fact that there are probably way less people using the Stadium as a hybrid controller, than there are as just an effect processor I really think technology as it pertained to both in and out of the box is getting more complex... I mean now-a-days its rare to find a guitar pedal without midi control. So it would be great if you all could comment and chime in here so that we can get this in view of the developers... even if you don't need this functionality now you probably will down the road and your comment or upvote might have been the catalyst for getting this post in front of the developers.. Don't live in regret for the rest of your life because you didn't chime in here... that would be a Boooooo.

My bad. I was sure it was called Return Level in the Global Settings. But actually it's called Send/ReturnL and Send/ReturnR. Btw: I've repeatedly asked for a "separate Send and Return Level parameters" feature in a future update. Combined Send/Return level pairs (the status quo) can be a limitation in a lot of use cases (4CM with amps, Tonex in the loop etc). Sends and Returns should be treated independently.

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

@flobudi there's lots of options on the chain to optimise volume. The amp channel volume will change the volume and no other amp characteristics. There are also gain blocks (mono or stereo) that you can run as a final block to 'normalise' your levels and/or to add boost for solos. You can also alter the output level of the output block. As to the optimal level, just don't end up with everything so hot your causing digital clipping in the chain or at the desk. The Helix has meters on the output blocks you can monitor. As you'll be aware from the fractal the metered level is not the perceived volume in the mix so you will need to adjust accordingly (without clipping, hence using a conservative baseline).

OMG, great tip, JPD. Thank you. Super maddening bug. I have a really elaborate preset I've been working on all day, and after I deleted some blocks and re-mapped some Stomps none of my (dozen or so) remaining blocks (that I didn't touch) respect snapshot bypass anymore. Copy-Clear-Paste each block seems to get it back, but then I need to remap all 8 snapshot and dozen or more blocks. Very much looking forward to 1.2.1.

I do the same since I had problems with an ISP router being picky about what it would allow on the network.

Thanks for the thoughtful reply — I think you summarized the situation very accurately. I agree that what I’m describing does resemble a kind of “Helix / Line 6 University,” and I also understand that historically this has not been Line 6’s primary approach. The forum-as-community model, where musicians share tips and knowledge with each other, has clearly worked well for many years and remains extremely valuable. Where I think the tension appears is exactly what you mentioned: Helix Stadium (and even the original Helix) has evolved into something that goes far beyond a traditional pedalboard. Routing, MIDI, multipath, preset leveling, recording workflows, Showcase, integration with other systems — at a certain point this becomes closer to a sound design and production platform than a simple guitar or bass product. Yes, the information exists, but it is fragmented, uneven, and often discovered through trial and error. For many users — especially working musicians with limited time — this creates an unnecessarily steep learning curve. Using a metaphor: at times it feels like being handed a spaceship capable of traveling through time, space, and parallel realities, but then being left alone to learn how to operate it blindly, gathering scattered clues from forums, videos, and isolated comments. You can get there, but the path is far more difficult than it needs to be. Regarding how many users would benefit from this kind of approach, I personally don’t think it’s only about a small group of advanced users. I believe this is necessary for most users, and especially for newer generations who are discovering these tools now. Today, many users are forced to guess how fundamental things work, jumping between forums, YouTube videos, and partial documentation instead of having a clear and structured learning path from the beginning. As for whether this is viable as a business, I honestly don’t see it only through that lens. More than a commercial product, I see structured education and deep documentation as something that has become necessary and complementary to platforms like this — whether free, paid, or a hybrid model. It should evolve alongside products that have long surpassed the concept of a simple “pedalboard” and are now genuine sound design tools. To add some personal context: I am relatively new to this world. I purchased a Helix Stadium XL about a month and a half ago, and since then I’ve been encountering many of the issues discussed in this thread. While some aspects are intuitive, much of the system’s real potential goes beyond my initial understanding. As mentioned earlier, the learning process often becomes spending many hours researching forums, watching YouTube videos, and consulting various sources with information that is scattered, fragmented, and often unstructured. In my case, I’m even considering relying on third-party books such as Craig Anderton’s, despite knowing that it likely does not fully cover Helix Stadium’s specific features. This learning approach — based on trial and error and non-centralized resources — feels unusual for a product at this level, and it’s surprising how normalized this has become. At times it can even lead to discouragement or a temporary loss of motivation to use the device, not due to lack of interest, but due to the difficulty of finding a clear path forward. That said, I genuinely enjoy the platform and have no intention of giving up on it. After a month and a half of use, I feel that I’ve made limited progress relative to the system’s true potential. I understand that some users may have more experience or learn faster, but that shouldn’t be an implicit requirement to properly benefit from a tool of this complexity. The absence of truly in-depth manuals, structured courses, or clear learning paths should not be part of the “entry cost.” Even from a practical or business perspective, I believe that investing in deep documentation and structured education pays for itself: it strengthens user commitment, reduces frustration, prevents early abandonment and second-hand resale of the product, and ultimately makes the platform more accessible and attractive to new users. I genuinely believe this need already exists, and that the fact we are having this discussion is itself a strong indicator of that. Thanks again for taking the time to engage — this type of exchange is exactly why I started this thread. Kind regards,

All amps don't "clean up" the same. That phenomenon is a result of the interaction between the guitar's pickups and the amp's input circuitry. While the Helix amps are very well modeled, in the end they are not really tubes. All that said, my guitars, single coils to JBs to high output ceramics, all "clean up" just fine with the Helix amps I use. The INPUT circuitry of most REAL WORLD amps is 1MegOhm impedance. Certain FX placed between the guitar and an amp's input (see below) are lower than that and in order to get "authentic" sound from the modeled FX Helix uses analog circuitry to mimic that interaction with the pickups. First thing to do is to check GLOBAL SETTINGS>PREFERENCES>AUTO IN-Z. When set to ENABLED Helix uses that analog circuitry to mimic the interaction between your pickups and that type of effect, using the first ACTIVE effect in the signal chain as a reference. When set to FIRST it uses the FIRST effect, active OR bypassed. Since MOST of the FX in Helix are 1M input impedance, the ENABLED/AUTO settings will normally be fine. If you ALWAYS want your pickups to act like you're plugged straight into an amp (you don't use those FX), then on the INPUT BLOCK of each preset set the IN-Z to "1M Ohm". This overrides the GLOBAL IN-Z setting and is as close as Helix gets to that (plugged straight into an amp) behavior. There's a spreadsheet online somewhere that has all of the Helix FX impedance info, but I can't find it just now. Here's a partial list distilled from that SS. Thanks to @John Mark Painter on TGP. The post is from 2020, so you might want to do a search for the actual spreadsheet which was updated to v3.80: All Dynamics are 1M All Reverbs are 1M All Pitch are 1M All Filters are 1M Wah with Impedance Changes Weeper 90k Teardrop 90k UK 136k Delays with Impedance changes Analog Echo 230k Elephant Man 90k Analog w/Mod 90k MultiHead 22k Cosmos 10k Modulations with Impedance changes 70's Chorus 22k Analog Chorus 22k Courtesan 136 Vibe Rotary 90k Dual Phaser 230k U-Vibe 90k Distortion with Impedance Changes BIGHORN (Tested manually...check for yourself and confirm) 70k? Deranged Master 22-32k Colordrive 136k Triangle Fuzz 22k Fuzz Pi 22k Arbitrator 10k Facial Fuzz 22k Buzz Saw 230k Tychoctavia 230k Octave Fuzz 230k Jumbo Fuzz 90k Industrial Fuzz 10k Hedgehog 230k Scream 808 230k Scream 230k

I have noticed that there are times I have a FX that won't respond to on/off state changes between snapshots. I found that if I copy the problematic FX block then delete it and immediately paste it back in I can control it with the snapshots just fine. Not sure why. That being said I am waiting for the next FW update to see which of the reported issues I have experienced are fixed. jpd

Now that more and more are moving to Linux I think it would be good businessto have drivers for most soundcards and equipment for Linux. I think it would increase a lot of music performers who Would like to use Audacity and the Line 6 soundcard to create music. What do you think?

gavinashun, great question. I believe the instruction state that 32Gb HC (UC 1 or higher speed class) is the minimum to use. There are others members in this forum that have said they have read or heard the Stadium can use a 1TB microSD. I know 512Gb is reported to work in this forum. Here is stapani's comment ... You will have to use the maintenance mode to format the microSD before use according to the manual. jpd

Just compared the file contents of the original (problematic) file with the second one I recreated from scratch and noticed that the snapshot settings for all of the blocks is populated with null after the first three Snapshots (which work correctly), instead of true or false as opposed to the Preset that is working properly. I did create the preset with the Stadium App (as that is still my preferred method) so I can not report whether it was the App or Stadium XL that created the problem. But once the preset is created with these null values then I think that it can not be corrected unless you edit the file (perilous and error-prone at best) or just re-create the Preset from scratch as @bverdon suggested. Either way, it is definitely a bug. For further clarification: Original (problematic) Preset: the "snapshots" element is each block records "false, false, false, null, null, null, null, null" The re-created Preset: the "snapshots" element is each block records "false, false, false, true, false, false, false, false" I typically expect true/false to be binary unless there is another purpose being used for the value. This would lead me to believe that those blocks are not being set properly and may either be turned on or off depending on the last snapshot loaded (or another internal array).

The issue was confirmed and reproduced by line 6 support. fingers crossed!

Hey, I just dropped a pack of 5 free Line 6 Helix presets, and wanted to share it here. They’re a mixed bag: a couple of dirtier, aggressive tones, a few atmospheric patches built around delay and reverb, and some in-between textures that ended up sounding way better than they had any right to. And hey… free is a fair price. If you want to check them out, you can find audio previews in the link. Let me know what you think! https://www.noiseharmony.com/post/line-6-helix-free-presets

Hello, I searched the internet for help on using Helix Edit on Linux. I have no problem running the native Helix plugin under Arch Linux using Yabridge, which works flawlessly. However, I still need to perform firmware updates for my Helix Floor and enjoy the convenience of editing presets using Helix Edit. Since I couldn’t find anything online, I decided to come up with a solution myself. I can confirm that I was successful in running Helix Edit on Linux. Below are the steps to achieve it: 1. Install Wine and Required Dependencies Make sure you have Wine and its required dependencies installed. - sudo pacman -S wine wine-mono wine-gecko winetricks - yay -S wineasio - register the ASIO driver within Wine: wine regsvr32 wineasio.dll 2. Install Line 6 Helix Edit in Wine Download the Helix Edit installer Run the installer using Wine: wine path/to/helixedit_installer.exe Follow the installation prompts. 3. Workaround for USB Connection Using USB Passthrough with VirtualHere (USB Sharing): Since Wine doesn't natively support USB devices like the Line 6 Helix, a solution is to use a USB-over-network tool like VirtualHere, which allows USB devices to be shared with Wine over a virtual connection. Steps for VirtualHere: Installation: - yay -S virtualhere-server-bin - yay -S virtualhere-client Run the VirtualHere USB Server on your Linux machine: sudo ./vhuitarm -b Or use the appropriate version for your machine. Run the VirtualHere Client in Wine: wine path/to/virtualhere_client.exe The USB device (Helix) will now appear in VirtualHere, and you can "attach" it inside Wine (Alternative to VirtualHere) Configuring USB Device Access via usbip: For a more manual solution, you can use USB/IP to share your USB device and try to access it from Wine. Install usbip: sudo pacman -S usbip Load the necessary kernel modules: sudo modprobe vhci-hcd Find the USB device: usbip list -l Bind the USB device (replace <busid> with the correct ID from the previous command): sudo usbip bind -b <busid> The device should now be accessible within Wine.

The minimum volume knob on the pedal is likely causing this. Set it to it's minimal position.

My 500mA 9V negative center power supply does not operate this pedal. OK.. batteries. It shuts down after 5 min or so of playing, whether I have fresh batteries or not (Duracell Coppertop, three sets!).

No traduzcas la página: desactiva el traductor automático, aprende inglés y podrás descargar todo desde la página de L6.

They are EH and made in china AX7. The amp has been totally fine and sounding awesome and then suddenly went to turn it on and the fuse blew. Ordered a load and same again. Just blows each fuse. Valves are working fine as I’ve put them into another all tube amp. it’s the fact that i have been told by Like 6 it’s not repairable due to the power transformer no longer being a part that can be ordered, and after lots of discussion with the service centre here, I am 100% sure it is the transformer. What do I do now? It’s a dead amp and no way of fixing it! I really think this is crazy for a current production amplifier being sold. Am I wrong here?

Ok, got new PC, i7, 8gb, win8.1 x64 There was a problem, but not the same - my system was crashing with BSOD with a relation to the line 6 driver (l6podhd564.sys) when ASIO starts. Not always but often. Similar to this - http://line6.com/supportarchivenew/thread/80846 I removed "Microsoft Camera Codec Pack" from Windows Update center and blocked it. Problem gone!

Had this issue this morning. Yesterday the showcase track I loaded in worked great. Today, no audio even though the stems are there. I’ll try the backup and factory reset. fingers crossed!