bbehrens

The LumiKit looks pretty awesome too! Maybe I should've ordered that one!

hmmm, Good catch. I hope that you filed a ticket with Line 6 support. Their search functionality has always been lacking on their web site but I have found the search functionality on the Stadium very good so far. Except for this little hiccup.

Interesting. I have ordered Chad Boston's as the design looks good to me. But I would also like to put something directly on the screen. Can you post pictures of the applied screen protector on your Helix and report how the touch screen is behaving with it on? I would hope that it is just like most screen protectors on phones these days and works wonderfully well.

Also, for now, unfortunately, there are multiple problems with importing OG Helix presets. You may run into issues. Building the presets cleanly on the Stadium XL has been very successful and the Line 6 team did a pretty great job at making this about as easy (without a mouse) as I think could be done. Just a cautionary tale... Line 6 support has acknowledged issues with the import process. But it also might be dependent on the complexity of the preset being imported.

All of the Legacy FX blocks that were Legacy on the OG Helix are ONLY Stereo. There is no MONO version of any of them. So far, Line 6 has brought over ALL of the OG Helix FX blocks, including the Legacy. Due to the new Agoura Amp modelling, Amps and Cabinets are another story. But it appears that Line 6 has given Helix Stadium users access to everything except the pre OG Helix 3.0 Legacy cabinets. That and the combining of the Low and High Shelf and the Parametric EQ, which already have the Low and High Cut.

I am on v1.2 and have had this happen. It is a minor inconvenience and an annoyance. But I think that it may have to with with Wifi Connectivity. What has been your experience?

I have logged this issue and am currently working with Line 6 support. So far, they have confirmed that there are some known issues when exporting presets to Stadium. I have found that creating a preset exclusively on the Stadium and not using the Stadium App has not produced the issues that I have seen on the Stadium App, including this one. I have successfully created two inline cabinets (both using File files), and have been able to use Snapshots to change the IR files with no problem on the Stadium (I don't believe that this can be done reliably in the Stadium App until they resolve the Cabinet/Snapshot issues we are seeing.

I have no experience in setting/using the MIDI clock on the Stadium yet. I am just not set up for that quite yet. Sorry.

I have run into many different issues from connectivity, Sound, Parameter assignment, and Impulse Response switching in Presets. I have hardly run the gamut of capabilities of this fantastic device yet. BUT, I have found (so far) that programming a preset exclusively on the Stadium XL floor unit alone has produced significantly more consistent and expected results. I don't know about anyone else here, but I have had (almost - holding cards here) - NO PROBLEMS creating presets on the Stadium as compared to the Stadium App that I am running on Windows 11 (Latest update as of this writing). If you run into any issues, carefully build the preset from scratch using only the interface on the Stadium itself and see if you have nearly as many issues. I would be interested to now of issues with the Stadium App OR on the Stadium floor unit alone. I think that doing a little of BOTH is just asking for trouble until Line 6 gets the newborn issues under control. Try using only the Stadium interface. You'll still have to import stuff using command center on the App - but that should not present any problems.

Has anyone else had a problem on the Stadium with any of the Block parameter displays when editing on the touch screen? If I switch the Dual Delay from "Off" to "On" the little underscore line moves to the right but the left underscore stays green (just slightly dimmer and not frey like other parameter underscore lines) I was just wondering if this is a reported bug. I am NOT talking about the Stadium App as I am NOT using it since it has had so many issues.

Line 6 appears to have a problem with Cabinets on imported presets from OG Helix. The fix that seems to work is to select a different preset (Known to be good) and restart the unit (1+ minutes later - you are back in business.) (Sort of). :-(

Thanks Mike. This functionality was present on the OG Helix. Unfortunately, the blocks were all created equal but act differently. Not sure what magic combination of button pushes did that but the footswitch bypass was not one of them (pretty sure unless it is easy to change without intending to). I have a hunch that the Stadium App is a little buggy under the covers. But if the code is much different than the code in the presets on the Unit then we will be chasing twice as many bugs through the system. Even worse if they ever get a Stadium Native interface going for DAW's. But that has not been Line 6's approach. They unified their development process back as of 3.0 (I think) of the OG Helix. And the OG Helix has been, and is still, solid. I don't know when I will be able to use this new (more expensive) Stadium thingy. I don't run it like it was a plain vanilla pedal board.

Agreed with you all. I am still trying to figure out how the preset management is better now in the Stadium over the Helix. I assume that it would have something to do with Showcase and saving songs. But for now, it is just confusing to me. But what I DO understand is that I have half of the preset storage capacity on the Stadium as opposed to the Helix. I know that I might be able to use multiple SD cards. And 512 presets is still more than enough for any particular show. Still, I found myself swapping out Set lists on the Helix pretty regularly for Preset Development, Play-Along Set Lists, Sunday Set Setlists, Christmas, Top 100 songs, Bass Guitar Set lists, recording, etc. But this only allowed me to at least always have a backup of a set list that I needed to offload in order to create a new one or bring another one in. Remember, we could have 8 Setlists of 128 songs! So far, I have had to reset my Stadium back to Factory several times due to buggy issues and that has only made preset management MORE problematic trying NOT to lose presets that I had created so far (which is not very many yet, either. Remember to ALWAYS SAVE (like the early days of Windows!)

I often just take any old preset that I like or is similar to what I am looking for. However, I also have a spreadsheet and some scripts that can scour all of my Line 6 Helix presets and pull out any block in any preset and I put these into Excel spreadsheets so I can quickly look at what presets use which Amp models or IR's or Distortion pedals, etc. But if I am after clarity or a specific tone then I will follow Jason Sadites advice and just start with an Amp and a Cab. I will often put a one switch looper in front of everything so that I can play a chord progression, lead part or ambient part so that I can just swap through Amps or Cabs or effects or whatever. While Line 6 has provided MANY preset examples that are widely varied, many of the presets that you can buy online often have the same Amp/Cabs and effects chains for certain styles of music. Jason Sadites is vocal about his use of Compressors, EQ, and ribbon mics. Steve Sterlacci, primarily just uses his Helix as a simple pedal board. Worship Tutorials often uses the same Amp/Cab and effects chains in many different songs. What I think that they have in common is that you can get the best sound from focusing on the basics. Oh, and I would highly recommend any of their presets. I just wish that they were a little cheaper is all. If you are layering parts, then start with a basic tone and don't go too far beyond that until you start layering. Do not add too much early on. That will give you an idea of how the different guitar parts interact with each other. You might also use the looper to get multiple parts once you start building your preset. Add EQ, Compression, and other transparent effects earlier and then add Delays and Reverbs later. This will help clarify what you are listening to. To keep Hi-Gain tones tight, keep it clean. Angus Clark from Trans-Siberian Orchestra is VERY open about his guitar, effects, and playing style. He will even walk you through how he plays some of those famous TSO songs. His tone is cleaner than most people come up with. Often, Distortion, Reverb, and Delay can be used to cover up sloppy playing (which is not a bad thing). But you have to play it cleanly enough to not rely on those things that can muddy up your sound. Hope this was helpful. Just 2 cents.

Seems to be the perfect size for the Stadium! I Ordered a 1/4" plywood case that is almost exactly like that for my OG Helix. Built like a l]tank and protected it very well (except for when it is open on stage (I have a damaged scribble strip that is still readable and one of my knobs now has a ding where you can tell if it has been turned or not now. And I have my Green LED going out on one of the foot switches (No longer displays Blue or any color needing the blue LED light. Funny enough, I ALWAYS took it out of the case when playing live as I just did not need to extra height my foot had to travel. (I'm lazy I guess). IT also weighed more than the Helix! But I DO NOT like the design of the new Stadium backpack. NO THANKS!

True "Preset Spillover" is a feature that currently exists on the OG Helix. But, as stated by @stuming, you sacrificed one of your DSP processors (50% of your total available DSP) in order to get that. It's great for using multiple presets that don't require more than one DSP processor. I have not heard anything from Line 6 on IF they are going to support True "Preset Spillover". But, I would assume that it would follow the OG Helix in that you would need to sacrifice one of your DSP processors in order to do so. Line 6 could provide this functionality later as they did with the OG Helix but they are very silent on future functionality - No one wants to anticipate a feature that never comes - or comes much, MUch, MUCH Lat-ter.

Nope. Generally NOT using Hype. Though I do not own any of the Amps that I typically use in the Stadium, I prefer the unvarnished tone from the Amps I have used so far. Though, I may admit that I will go in and use it as a Tone knob. (In other words, I use everything at my disposal to get the tone that I think sits best in the mix - from my guitar, to the Hype Control. I do have it turned up to maybe 2.2 on one of my presets. Building presets takes some time since I use Snapshots and often IR's (though I generally prefer the Line 6 Cabinets - Tone changes when I use an IR and I may like it!) - So... I often spend time re-building Presets so far... due to bugs and L6 work in progress on the Stadium. :-(

That is indeed working for me! Thanks dandesy! Now for the BAD news. I created a copy of a preset from my OG Helix. The ONLY difference was that I select the "B" IR (from the dual IR block in Helix 3.80 as two separate dual IR blocks in Stadium since Stadium can't set IR blocks to Snapshots - so I turn one off and the other one on in order to change the "B" IR block. No import. Nothing weird other than turning one IR block off and the other on in the Snapshots. THAT Preset now causes the Stadium to lose sound until I restart the unit. Do you think that I need to re-create the Preset, yet, AGAIN?!? That stinks from a User Quality of Life/Workflow/Frustration point of view. I find that there is a lot of re-work since Stadium is not stable at this time.

Thanks for the info dandesy. Not sure I exported from the Set list. The second time I was sure to export from the USER list. Also, my Helix Stadium sound seems to just cut out from time to time. It either has no sound coming from any of the inputs when I first turn it on or it just randomly cuts out after a while. I either case, turning the unit off and back on does not always fix the issue either. And it has been happening on presets that I have created. I will have to go back to the Factory presets to see if the issue continues, AND I will try your suggestion of selecting a DIFFERENT preset once I restart the unit. I can't tell if I have a bad Helix Stadium - or the Helix Stadium is just not ready for prime time yet.

Made sure to do a fresh Export from HX Edit ver "3.82". Imported into Stadium via Stadium App. Exported without loading it in Stadium. File contents are as shown above. Apparently, Import/Export Functionality is not 100% good. I will be filing ANOTHER bug report. Was the initial OG Helix release like this? I purchased mine in 2017 so I was NOT an early adopter but it has been pretty darn solid in all this time. I only files one bug report on it in all this time.

Sound finally came back after leaving the Unit on for a while and them turning it off and then back on AGAIN. I exported the Imported file to take a look at it and this is the entire contents of the .hsp file: rpshnosj{ "meta": { "name": "YoureBeautiful2!" }, "preset": { "cursor": { "flow": 0, "path": 0, "position": 6 } } } No WONDER it is having problems. Either the Import failed, the Export failed, or BOTH.

I imported several Helix 3.8.0 presets into Helix Stadium. Three worked fine, but the 4th one caused a loud tone to come through the outputs (I was using headphones) and would not stop even when I changed presets or set the output in the mixer to 0! This reminds of the issue that occurred early on with the OG Helix. BE CAREFUL when wearing headphones. I turned off the Stadium and then back on and there was no sound at all from any of the Stadium outputs (Again, I was using headphones but did also check the L/Mono output as well. I rebooted again and the sound was working again. But when I went to that same preset to see if it would make the loud tone again, it did occur again the same way and I had to turn off the Stadium and start it again. Now I can not get any sound out of the Stadium no matter how many times I turn it off and back on (I have tried multiple times so far). It may be dead - which is worrisome!!! This thing costs WAY TOO MUCH to be having these problems. I hope that I do not have to send it back to Line 6. I will try restarting some more, and failing that will reset to Factory... AGAIN. I still have my OG Helix which is solid - The Stadium will NOT replace it any time soon. This is getting frustrating.

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

Yes, I rebuilt the Preset from scratch and it worked as expected. Saving and re-loading the original problematic Snapshot did not correct the issue as it continued to persist. Interestingly, while re-building the preset, when I moved a few of the blocks to a parallel path (From Path B to Path B1 and B2, I ran out of DSP and could add no further blocks. So I discarded the edits and added the other blocks first and then moved the blocks that I wanted to the parallel paths and it worked fine. And I could no longer produce the DSP issue. It should be noted that I was operating very close to maxing out the Max DSP (whatever/wherever that is). I am very interested in the DSP values as I have my own spreadsheet for the OG Helix where I have DSP values for every block in the OG Helix down to hundredths of a percentage and is very accurate. I don't think that any DSP values like this will happen any time soon for the Stadium as Line 6 takes some time so stabilize the DSP allocations on the OG Helix. Some of the 3.8.0 new blocks have the same MONO and STEREO DSP values and the MONO version were always optimized prior to 3.8.0. I think that they went off to do other things (Obviously). There is also the possibility that some DSP blocks may be more variable than the OG Helix was due to the new Agoura Amp models (though I think that it would be limited to the Amp/Cabinet combination and not the OG helix effects models and Legacy Amps.

If you know of any easy ways to view all of the Block assignments at a glance, then put them here. You could easily view all of the block "BYPASS/CONTROLLER ASSIGN"ments in the HX Edit App as there was a panel devoted to it. I could easily see all 23 (just kidding, 2 or 3) blocks that might be assigned to a footswitch. I hope that they include that in the Stadium eventually.