bverdon

Well... all good points above and appreciate the discussion. For the record, I did purchase the powervalve 200 but ultimately returned it to Sweetwater. It was worth a shot. To me, the tube is pretty much a gimmick. It provides a small low end type of bump (with a slight volume bump) but still feels like a class D power amp to me. Not to say it doesn't have it's pro's and gives you some stage volume with your modeler rig. To me the tones and feel of what I was getting out of my Friedman 2x12 cabinet (with V30's) just didn't seem genuine. I am glad I tried it... cuz now I know it isn't for me. I will probably try the Wampler Pedalhead when it comes out... and return it if I have the same experience. No harm, no foul.

Anyone care to share their amps they cloned? Or is there a method of sharing files?

I read somewhere that Eric noted that there is a bug (and they are working on a fix for the next release 1.3) that the SIC from a linked cabinet ... which my understanding is that the matching cabinet when you introduce a new amp/cab block at the same time, are mated and when you unlink and select another cabinet, the SIC should follow the other cabinet in the signal chain. I don't know how anyone can tell the difference unless they compare the exact same cabinet and disable the primary cab with the mated SIC.

If I had to do my pre-order with Sweetwater over again for the Stadium... I would have done with multiple resellers and canceled the other one once the other one shipped.... what a mess that was with Sweetwater!

Interesting... I do not have this issue using Reaper. A Reaper trial is free for something like 60 days if you want to determine if it's a Stadium hardware or software (DAW" issue

Thoughts? Mine shows up early next week.... Would have opted to go for the Wampler Pedalhead... but that won't be out for a while. I have a Friedman 2X12 ported cab with V30's. Should be interesting....

In my case... nothing... nothing pressed or changed. It's strange... It hasn't happened again though. Maybe because the stadium was on for over 6 or 8 hours? Will keep an eye on it. Again... not biggie... thought it was strange. I mean... I would select a new preset play for about 10 minutes... not change ANYTHING... and the stadium app would look like I changed something. This happened on several different presets. After a reboot... no longer an issue.

What is your facebook link?

I am not sure if this was occurring prior to the 1.2.1 update, but now things are a bit more stable and I find myself paying more attention to other things. Now when I have the Stadium app open and NOT changing anything, it looks like after a few minutes of playing, the Stadium app thinks I have modified something. The preset name changes to what appears to be in script mode which signifies something has been modified. I have created a new preset from scratch and it still happens. Not sure if I am the only one and I haven't tried backing things up and performing a factory reset yet. It's really cosmetic ... at least seems that way unless there is some sort of memory leak occurring that is actually changing something. Anyone else notices this?

Completely nailed it! If you didn't research your Stadium purchase prior to the purchase, it's all on you for sure! I knew what I was getting when I purchased. Anyone interested in a fully featured Stadium should not buy unless they are ok with the early development lifecycle.

I’m following this thread because the biggest issue right now appears to be snapshot inconsistency. It’s both the most important feature and, unfortunately, the most concerning bug at the moment. Until this gets fixed, the most reliable workaround—although a bit time‑consuming—is to rebuild your patch from scratch. I’ve also had decent success by creating a brand‑new preset (saving frequently) and then copying blocks over from the problematic patch one block at a time. Again, save often. Once all the blocks are in place, you can rebuild and configure your snapshots. One thing I now do EVERY single time I create or update a snapshot is test each snapshot individually BEFORE saving the patch. This has helped me avoid corrupted or inconsistent states.

I’m curious to hear about everyone’s experiences so far using FRFR systems with the new Stadium. What setups are working best for you, and which amp models you pairing with it?

Appreciate the post... and that you opened a ticket with support. I have had a few issues with snapshots but when I started from scratch and rebuilt the preset, the issue was resolved. If I re-imported the old troublesome preset...the issue is there. Not sure if that helps for a workaround.

Ah!! Good deal... makes sense. I was thinkin of opening up a ticket... lol! Thank you

Weird.... I don't see that line

I just received my Stadium XL yesterday and I was able to stay connected for 4 hours.... no disconnects from the edit software (Windows). I have an eero mesh Wi-Fi (currently connected to the main AP) and my AP is in another room, about 15 feet away. I am connected at 5Ghz speeds on both the PC and the stadium. So... for me very stable. I would suggest that if you are having issues, try to get both devices on the same speed but if your AP is very far away, try to get both devices on the 2.4Ghz channel. This may not be a bug for Line6 to address.

Hopefully all those who are interested in this support, will chime in. I for one really hope they eventually develop the support for it. I am sure there are much higher priorities but it never hurts to start the conversation.

Ha! just found this one....

Does anyone know of a decent video that illustrates using the effects loop of an amp to send just time based type of effects to a real tube amp? Everything I search targets 4 or 7 cable methods. When I tried to do this to my 5153, nothing but noise. Thanks

Ah... well.. by assigning the topology to a footswitch.. now I can save the desired topology per snapshot within a given patch! Nice! Did not think I could do this... love it! Thank you very much Phil!

What?! This would be awesome... how do I do that?? ok... went back and I see where I can do this... now to see if I can save a clean snapshot with one topology...and the dirty tones with a different topology within the same snapshot...that would be ideal vs. switching via stomp mode. Thank you!!

I like topology III for clean tones and topology II for crunch and heavier tones on my Helix / DT50 setup. I know I could build a new patch but... is there any way to switch the topology within the same snapshot? Thanks

I have a Helix floor unit and a DT50 head and matching 4X12 cab. I feel like I have finally got some good tones through this set up but I have tried mic'ing this puppy up and well... it always sounds buzzy.. not what I am hearing in the room. I have tried multiple mic's ... angles, distances... It's probably the small room I am in just doesn't have decent acoustics... but to my ears (and of course, I am slightly angles from the cab... ) just doesn't sound good mic'd. I would probably have the same issue with other amps in this room.. not sure. Well... messing around today, I sent the same signal I am sending to the DT 50, I split off an xlr with a cab... and feel like this is so much closer to what I am hearing in the room from the amp in the room. I think the volume is slightly high.. but the tone is there. In the short clip of me noodleing I switch between several pickups and I hear/feel the dynamics of what that sounds like in the room with the amp . What I really like about this is, I can play my DT50 while recording a backing track and capture more of a performance kind of feel. Have you guys messed with anything like this? Run into the same issues when mic'ing cabs. Or... am I just really doing everything wrong? Thoughts?

Figured it out... one corrupt preset in my preset list... just went through each one... one of them gave me an error regarding some kind of memory location... deleted it... now everything is working as designed.