bbehrens

Eric Klein demonstrated cloning of Amps, Cabs, and Distortion Pedals at NAMM. It makes me wonder what kinds of pedals will be able to be cloned through the "Dolly" cloning process. (Can't remember the name though I know that it is a sheep. Baaa Baaa.)

A change will occur to a Preset if the volume pedal has changed position as well. My Volume pedal is pretty stable on the Stadium but the Volume Pedl on my OG Helix would not always be at exact 0%. And it is now impossible to tell on the Stadium since there is nothing to indicate that the Volume/Wah Pedal is at 100% or 0% or whatever (an annoyance I hope that they will correct in the future.

This explains why, even though I cut the split by -3.0 dB, I still get problems with Unity gain. Nice observation. Like on the OG Helix, I can use this to my advantage instead of using gain blocks for volume builds in my presets. I just have to be careful of where I put them and what blocks come before and after them as some blocks are additive (such as Reverb and Delay. Still, it CAN be useful.

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

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

Funny. Line 6 has been often noted for paying attention to their customer base. My guess is that they are under a lot of pressure for getting a solid competitive product out since other modelers that have come out with more features over the last 10 years have gained a lot of ground. Line 6 has banked a lot of good will from their customer base. We will see if it lasts as long as they think that it will if they don't fix the Stadium issues and continue treating their customers as their source of income.

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

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

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!

The Stadium App still disconnects from the Stadium Unit over my Wifi every once in a while. It finds the Stadium and connects just fine when I initially start the Stadium App. However, when the Stadium App loses connectivity with the Stadium Unit and I try to connect the Stadium in the Stadium App, I get the message that the App successfully updated to 1.2.1 and the Stadium App will simply not find and connect to the Stadium. However, if I close the Stadium App and restart it again - "Vwalah!" (That's my word) and it connects just fine again. Anyone else having this problem after the update?

You must update the Helix Stadium App FIRST. Just fire it ip and it will let you know that you need to update it. Then update the Stadium Firmware from inside the App. THIS time you HAVE TO update via USB. I read everything that it was telling me first and it worked just fine for me. Hopefully others will find this helpful.

I have noticed that when my shows the "X" home screen, when I am in the middle of something, that the sound is unaffected and it comes back pretty quickly. Still, it's an annoyance.

Is this a preset imported from an OG Helix, built using the Stadium App, or built from the ground up only on the Stadium Unit itself. Imported OG Helix presets are prone to a variety of issues, the Stadium App is not much better, and there are still occasional issues building only on the Stadium unit itself (I have seen with parameter assignments) - BUT, it is still the most reliable option.

I am curious if this preset was hatched via the Stadium App or was handcrafted on the Stadium itself. I have noticed assignment issues with the Stadium Unit itself as I have been also working with Support and can get an assignment to work consistently, but I have to save it every time I assign the same parameter in order to get it to work. And then when I switch Presets or turn the unit off, the assignments are not there again. I avoid the Stadium App right now because there are even more issues that it creates.

I, too have noticed the red flash in the output blocks at the end of each path. I have noticed that the effects can bunch up rather quickly where you start a clean path with -23 dBA and just a few blocks later with an amp are getting the red light up at the end of the path with the default settings. You have to pay much more attention to the gain staging than you did with the older unit. However, this is all new hardware and underlying architecture so my guess is that the block have not been fine tuned to the Stadium yet by Line 6 - though I can't imagine why not... Anyways, it would be good for someone who has the know how to do some null tests or other digital goodness to see what the actual input/output of each of the block actually is. Jason Sadites has preached a Gospel of do what you want and don't worry about gain staging for the non-transparent blocks (e.g. EQ, Compression, Distortion, Fuzz, POG, etc.) but watch how you use the Delays, Reverbs, etc. (You know, those effects that last over new notes that cumulatively up the gain). But the Stadium does indeed to appear to be a might more sensitive. Anybody got any hard data to share?

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.