jpdennis

Kfletchan, [As I learn more my process could change drastically or adjust slightly (a very organic approach over time)] For most indoor venues I have used the OG Helix which I am now replacing with the Helix Stadium XL. When I have a larger outdoor venue I normally use two paths, one direct to mixing board via XLR and one using one of my mesa boogie amps via 4CM and a nice stage microphone of the soundman's choice. I personally feel his gives me a little something extra for the outside events. YMMV [So, here are my thoughts and next step actions ...] I have a EM midi controller for my Mesa Mark V:35 as well as an JP-2C which has its own midi in. So I am very interested in the "how-to" you asked about. I am currently studying the ins and outs of the Stadium XL via the online manual. I have noticed a "warning" if you will. The reason I am reading so much is that I believe the Helix Floor method for snapshot midi control assignments is a little different. With all the latest features and the Agoura OS Line 6 developed for the Stadium I believe some of the issues I have ran into might be based upon the above warning. I am seeing that I cannot assign primary or secondary triggers to a footswitch because I have been thinking like the OG Helix or even FX methodology for my needs. And that is because I already have been allowing the auto-assign feature to do most of my heavy lifting for footswitch assignments thus they already have multiple assignments. While I don't have the specifics yet, I am going to share what my beginning plan will be for any presets which I will create that will use snapshots. Others may already have figured this out but here is my first step. I will remove all assignments from the footswitches with the exception of EXPs of course. This will include snapshots as well as normal model blocks. My goal will be to start with a blank slate. For this part of the "test of concept" I may set my FS^ mode to Stomp A and Stomp B for now. This next step 1a and step 1b can then be done at the Stadium or the Control Center. I will then assign "say" FS1, as an example to snapshot 1 as the primary assignment (step 1a) and a midi command to one of my amp's midi in to control the channel/EQ/reverb state I desire as the secondary assignment (step 1b). If everything goes as planned I should have some time to test this out over the next several days due to my motorcycle parts landing this weekend requiring juggling upgrades on one of the bikes and 50% of the 70,000 overhaul on the other. Plus I have the always wonderful tax season meeting with my tax person next week. Anyway, I hope this idea I have gives you a start if not a leg up over me for finding the solution your looking for as well. Good luck, jpd

AlasdairGeorge, I would recommend you create a support ticket addressing these issues and report back what you are told. That would help other users in this forum as well. Line 6 support does not usually monitor this forum. jpd

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

bvstone, I am going to make a few assumptions as well as possible provide information you are already aware of. Please forgive me if my assumptions are incorrect. Forgive me if some of this information is redundant or you already know most of it. I find this an interesting concept as well as very doable as long as the DSP doesn't restrict you. The 4CM for Stadium XL to physical amp is fairly straight forward, as long as you heed silverhead's warning about cabling. When using the 4CM I put time based blocks (delay, reverb, chorus, flanger, etc.) after the amp. There are many vlogs concerning the Helix on this. The Matrix will come in handy for your thoughts concerning two separate signal paths. One of the output paths will use on the 1/4 L/Mono out jack only for the amp based 4CM and one will be the Stadium XLR L/Mono only for the FRFR. The 4CM path will not have any amp and/or speaker blocks on it. It could possibly be a single path to start to test DSP limits. Your more complex will be the guitar in to XLR out path containing the amp and cab models as your FRFR is similar to the studio playback monitor. You input on both paths can be set to the same guitar input of your choosing. I normally use my guitar's volume pots but if you want to use a Volume block I'd suggest putting it right after the input of both paths. Then you can play with their position within your design based upon the best application. I have found that placing the volume mono block on each path one after another (so to speak) works as expected so they are both controlled properly by the same EXP pedal. If using a Wah-Wah do the same and use the exact same Wah until you get use to assigning the same EXP to separate types. The various effects are your choice as I am just mimicking each path for effects and will use either a footswitch to activate the same type of effect block with a single footswitch and/or use snapshots. For the fx loop, that is your preference. Personally I am using a FX Loop Send 1 and FX Loop Return 2 so I can adjust the level (instrument versus line) separately based upon the FX loop on the amp I am using; I am still using the Helix Floor concept and will adjust as I get more familiar with the Stadium. You will need to apply this yourself for your system based upon the amps instruction manual. Also, forgive me if I have completely lost sight of what you are looking for ;-) Good luck, jpd

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

Je télécharge uniquement avec Chrome. Edge me pose problème. J'espère que cela vous sera utile. Veuillez m'excuser si ce n'est pas le cas pour vous. Veuillez excuser ma traduction française.

letterond, I only use Chrome for my downloading. Edge has been problematic. Hope this will be of help and forgive me if it doesn't help where you are. jpd

tufanderince, As I stated earlier, I do understand your frustration. I know that Line 6 is preparing to have PROXY in the coming update which I am hoping is released by mid March at the latest. Your other ideas are great. If you haven't already sent these ideas as feature request to line 6 support, I'd say please do. I have to say the idea of an onboard DAW seems interesting. Not sure how the multiple channels would work but the Matrix feature and Showcase may have some interaction. Only Line 6 can say what the current hardware is capable with respect to future firmware upgrades, as it was suggested during the prelaunch they are working on many things with the Stadium family, of which some have not been revealed yet. On a side note. and knowing this isn't what your vision is for a hardware upgrade with respect to the iPhone hardware use case idea you are speaking of, I have yet to connect via Bluetooth using my iPhone for any interactive capability for the Stadium. Having said that, the concept of the current iPhone connectivity opens up my thoughts to investigate at a later date what the Stadium can or cannot do at this time. In closing, I use this forum for conversation as well as sometimes reading with no feedback to open my mind to the possibilities of what others are doing, dreaming of, and issues solving with old fashion know-how & creative thought. 90% of my use for this Stadium is playing. The device just allows me to channel my Hendrix side. <AWAAN> Play & Party On! jpd

Fazly, To start this conversation, I haven't had to check the state of snapshot control for my EXPs, they just work but I do have auto assign engaged for several things in global settings. You will want to make sure the EXPs are allowed to be controlled by snapshots; I assume nothing so forgive me if this is already within your wheelhouse. What I normally do is have the vol assigned to one EXP (for my example I will say EXP2) and then the "state of a block parameter" assigned to another EXP pedal (for my example I will say EXP1). I will have EXP1 on (engaged) for the snapshot I want to control a parameter for (in this example the "amp drive"). All the other snapshots will have the EXP1 off (disengaged) and EXP2 on for vol. The other option is not to have a vol block and just assign one EXP pedal to the amp drive control EXP is on in the one snapshot and off in the rest. I do this for several of my presets based upon the snapshot setting I am controlling. But like putting on my shoes, there are several alternatives to my use case. YMMV jpd

goviline6, It is the "norm" from what I have experienced. Any change triggers the "you've made a change so do you need to save it" alert by either italics or e. I treat it like the Microsoft "are you sure" pop-up. It is a nice built-in for those you don't know if they want to exit or not from the Windoze app or OS. Personally, I made a mistake back in 1992 with DOS OS and I now know if I want to save or not or exit or not. Normally with the Helix family, I do a final save on a specific snapshot for each preset as my "initial" start when triggering a specific preset when at a performance venue so I won't be saving at the venue unless it is a leveling issue during sound check anyway. However, when creating and testing I always double check myself and what setting change or preset or snapshot within a preset I want to trigger a final save. At first it was a little annoying but after some time I learned to just accept it. It has saved me a couple of times so ... jpd

bverdon, This would happen even in my OG Helix Floor if I switch snapshots while playing, used the expression pedal by switching or adjusting the % of incline, as well as turning on and off blocks with the footswitches. The app as well as the Stadium will see that as a change of some sort. The app will just see it a few moments after the change. jpd

nobod999, Thanks. Nice to know there is a work-around at this time. jpd

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

tmlambert, It would be annoying if that was the case with respect to your chorus, EQ, and the two compressors. I use snapshots and for the FX blocks that I do not want touched by snapshots I make sure they are not controlled by the snapshot which is a per FX block setting. That way they stay at the same settings from snapshot to snapshot. As I get more comfortable with Showcase I am anticipating using fewer snapshots and preset linking. I have yet to hit the snapshot control limit silverhead has spoken of. I am only slightly concerned by that how it could affect DSP usage and preset stability since I have way more control than I had with the Helix Floor. jpd

I understand the OP's disappointment if a finished product was expected by the OP. However, Line 6 is deploying more as they can via current and soon to come updates. They are addressing the bugs slightly faster, which I can say due to the expeditious way I have been contacted by Line 6 support during the recent four tickets I created. I know that they are being careful to not address too many bugs without testing what is broken in the process of final release of updates. And I have read that Proxy is being demonstrated at NAMM, though I am not physically at NAMM. The Stadium XL is usable for what I need right now and has made headway with the updates. My memory may be bad, however, I believe they are committed to delivering updates in a tighter timeline than when the Helix Floor and Rack was first released. I may search when I have some time. jpd

Anyone know if this is just for demonstration at NAMM and will be in the next release?

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

GAJ52, Thank you so much for sharing your trial and error findings. I am finally getting some new stems created. I am hoping to have my first polished tracks ready. Please let us know if your backing tracks have sound over the next few days as you use/turn off/turn on and use again. If not, and if mine stop working over the next week or less, we will both need to create a new trouble ticket with Line 6 since I know more users have been waiting for this update to fix the "no sound" on backing tracks issue. jpd

Has anyone with the no sound issue checked the signal level bars by turning on the global eq, even without adjusting it, to see if there is a signal coming through at that point then check the Matrix levels. Upon applying the 1.2.1.xxx update I did have a couple of interesting issues. This may not directly apply here but I thought I would share that my Matrix levels were not quite right. A few of the matrix levels had been zeroed. When I first used the Stadium XL with the 1.2.1.xxx I had no sound and thought I broke something. I even made sure my guitar vol pots were set right and using my other amps and modelers to check. Not sure why I went straight to the Matrix levels at that point to check though when I was checking the global eq I did note that I saw the signal levels working fine even with no sound coming into my playback devices. jpd

theElevators, I agree that the Stadium will not be for every guitarist. I know from experience that modelers may not be the choice for every guitarist as well. While I wasn't part of the "I want it now and will deal with the bugs" crowd that requested early release, I did order it as soon as the early ordering was available. What I am interested in is the modeling improvements with the Agoura models. And, once Showcase is fully implemented and rock solid the best use case I see is the ability to have a "rig engineer in a box" so to speak. For me this opens up the "one man band" concept with reduced footswitch dancing as well as stage lighting controls. My Helix Floor was perfect for everything but the foot switch dance for complex songs and/or cover songs that require the "band leader wants the exact sound for the songs" demands. I am very interested in the Showcase feature as well as deep diving into the latest update that did fix several of the issues. [SIDEBAR] We had the helicopter sound rear its ugly head in the OG Helix as well back in 2017. And I did a search finding hits concerning DSP stress tests on the Stadium XL creating strange sounds. However, for my OG Helix, as well as the Stadium XL, I usually kept to presets that did not push the limit of the DSP capability; and I would create a "goto" footswitch within presets on the OG Helix if I needed to link presets for a very details song. That will be another test of the Showcase feature for me. Though, I may not be a typical user. <YMMV> jpd

gbr13697, Oh, got it. My fingers a little big as well. I now understand what you mean. Thanks for the clarification. jpd

gbr13697, Line 6 says, if all things are equal, to do exactly what you did. Of course I first log into the app and DO NOT connect to my Stadium via Wi-Fi or usb. I have disabled the auto-connection feature because of the issues I have read a few users are having. What I do every time I use the Stadium Desktop App in normal day to day use, before closing the desktop app, is I disconnect from the Stadium XL then log off the app then close the app. So again, when an update is ready, I log into the Stadium Desktop app without connecting to the Stadium XL and update via the prompt I see when the app launches. I update the app on the computer first. Once done I reboot my computer. While it is rebooting I then make sure my Stadium is turned off. I then turn it on, make sure I logged into the Stadium with a good Wi-Fi connection. There will be a red circle in the upper left. I use the hamburger menu to go to the download section and follow the prompt to update the Stadium firmware. [Now at this point I may be overthinking it but my process has never failed me so far] After the Stadium comes back on line I check to see if I need to reconnect to my Wi-Fi SSID and put in the password just incase I need to; I was taught to trust but verify. I then check to see if I am logged into the Stadium and if not I log into the Stadium XL. After that I launch the Stadium app on my computer, check to see if I am logged in still because the stadium desktop app update usually shuts down the app with me still logged in during the update process. I will log out then log back in. Next I connect and make sure the Stadium queues up for the final connection process and all is well for me. I then disconnect the Stadium from the app, log off the app and close the app. I will work only off the Stadium at this point to check to see if any of the blocks look strange in focus view; which is how I discovered the issue with the Parametric EQ block for the few presets I used it in. jpd [SIDE NOTE] Because I do not know how Line 6 fixed the code for the Global EQ and the fact that the Parametric EQ FX block is similar if not the same, I can only speculate the Global EQ fix also affected the Parametric EQ block and may have not been caught in final testing to let us know to have to reset the FX block if necessary. Again, I may just be full of it here. I have created a service ticket for this to see if it is something they should know about.

bbehrens, Are you saying you have the Stadium connected to your system via usb-c at the same time you are connecting via wi-fi? Thanks for any clarification. jpd