So, I had a strange occurrence last night.
I have a preset that was imported from OG Helix. In Stadium 1.1 I copied it 2-3 times and replaced OG amp models with Agoura amps. Then I updated to 1.2. Then I made a copy of one of the Stadium 1.1 versions of the preset and tried to swap out the Luxe Black and drop in the new Super Black. Immediately newly modified preset with the Super Black lost all sound. I was going through checking to make sure I hadn't inadvertently turned a level way down somewhere and in the course of that I noticed that the "hom screen" rendering of the signal flow block diagram was not showing the lines connecting blocks in the upper path (the path where the amp model change was made. I decided to reboot the Stadium and noticed that on it that the hardware screen looked like it was rebooting (for lack of a more precise term) over and over. I powered off the stadium, gave it a minute, and powered it back on. After some time it was back in the same cycle with the screen continuously rebooting but the Stadium itself apparently fully rebooted and ready to go. Even though the display on the unit was wonked out, I was still able to get around the Stadium with the editor app. Long story short, I had to delete that preset I'd been working on (which should have come back up as just a copy of the one I'd copied initially because I did not save any changes before I rebooted the Stadium) and then use the edit app to select a different preset. Once I did that whatever was going on with the onboard Stadium screen resolved itself and the unit worked flawlessly from that point on.
One of the reasons I mention it is that it's behavior was somewhat similar to what I observed when I tried to use
@mikah912 's first version of the Mk II+ preset in that something was going on moving/copying a preset around with one of the 1.2 Agoura models in it. In the case of mine, the preset went from OG Helix-> Stadium 1.1->Stadium 1.2.
Since I had to delete the offending preset to get the Stadium to return to normal behavior I don't have anything to share for forensic purposes, and I'm not real keen on trying to recreate the problem because I'm not 100% confident what I did to get rid of the problem is something I can successfully do a second time. For now I'm going to stop making copies of current presets and swapping out amp blocks to make new ones. Most of the time that's how I create new presets so it'll be good maybe to find a new way to work.
One of the main reasons I'm mentioning the occurrence is a PSA--if you get into a loop of screen reboots on the stadium, it appears a corrupted preset might contribute to it and if possible, using the editor app to delete the current preset then select a different preset might resolve it. One thing I didn't try was just selecting a different preset without deleting the presumably offending one. Dunno if that would work to resolve the issue on the hardware, but I had no interest in keeping the wonky preset around.
)
