jpdennis

I currently have a question to Line 6 support concerning this procedure and will report back in this thread if I get a reply. It may be nothing but better to be safe than sorry. jpd

I thought I'd ask .. How many users are following this exact procedure? I followed this and discovered the screenshots folder actually had files in it. I followed the following procedure exactly as outlined without any issue. The looperData.dat instruction seems to be very important. Has anyone followed this exact procedure and still had issues?

Mystic368, It is the "other devices" "Andere Gerate" the OP's first post and the subsequent comparisons for device drivers between his system and mine that we both posted in this thread. Now I am just speculating, but ... Sometimes different character sets aren't or can't addressed by programmers. This is similar to the cyrillic vs non-cyrillic issue for some driver set programming. In the case of the German language "Andere Gerate" in English could be translated as other devices, or unknown devices, or other equipment, or unknown equipment, or other instruments, etc. It is just frustrating not to see the line 6 stadium device driver accurately and it can have an adverse affect upon the operating system as well. ReverendLove can better clarify on his frustration and what the device driver isn't allowing. jpd

Kfletchah, You are welcome. You helped me dig deeper sooner than I was going to so you helped me as well. ;-) Just a heads up if you ever need more than one MIDI trigger, I am using 4 of the instant commands for a preset using 4CM with my Mesa JP-2C. It took a few seconds to wrap my head around the math matrix for this. I have one for the channel selection, one for the reverb, one for EQ1, and one for EQ2 ... so far. I had to be sure that I sent a EQ1 off command when sending an EQ2 on command and visa versa. Then I am using a footswitch independently to turn on and then turn off the Shred feature via toggle and two MIDI commands for the single footswitch which turns the color ring on and off as well. Once the light turned on the possibilities are only limited by my own mind. Anyway, thanks for seeking an answer to your need. And a shout out to Line 6 for this new methodology. jpd

Rockobeall, I was working on something similar which does not use a footswitch. Below is the thread I shared what I am trying which require one or more values to be controlled by snapshots. __________________________________________________________________________________________ Now to address using the footswitch ... these of course will be a different CC# for you as well as possible values based on what your looper document suggests. I know you want to use a footswitch and I am working on using a footswitch for the Shred value of my Mesa JP-2C. I haven't had time to plug it in but in theory I add a primary setting to Shred off (CC#27 and value=10 for the off state) and a secondary MIDI command for Shred On (CC#27 and value 64) which can both be assigned to the same footswitch. I press the unit once for on and the ring is lit. I press it again for off and the ring is unlit. I had to try this a few times to get the on state and ring lit state to work as I wanted and I am a little tired at this moment after a long day on my motorcycle build. So I might have my "states" backwards. Or I may have completely missed your point. Let me know. jpd

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

boynigel, Are you wanting to separate multitrack from a single audio file? I do not believe the Helix Stadium is currently capable, just like nobod999 said. I do not know if that is even in the future. You'd have to submit this to Line 6 support as an enhancement request and hope others ask for this as well. You can check with Line 6 support for their direct answer. However, I use my DAW for extracting separate tracks as I create them. Also, there are site that allow you download backing tracks as separate instrument/vocal tracks to use in showcase. Of course don't do what I did the first time; I wasn't watching tempo prior to extraction and I believe I had three separate tempos - I guess that makes me human - hahaha 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