Leaderboard

Symptom: On Windows 11 Pro version 22H5, the Stadium App v1.2.0.15 application window crashes every time upon attempting a USB-C cabled connection to a Helix Stadium Xl at Firmware Version 1.1.0 Build:1274 for the purpose of doing a Stadum XL firmware update. This is caused by the ‘Helix Stadium Bulk Transfer’ driver packaged with the Windows version of Stadium 1.2 App not loading. On Windows, navigate to Device Manager and see the ‘Helix Stadium Bulk Transfer’ driver listed as ‘Other device.’ This is not normal. Look at the properties of this device and you will see the driver is not present and has not loaded. This is why Stadium App 1.2 on Windows crashes every time on attempting to connect to a Stadium XL over USB-C to do a fimware update. When you plug the Stadium XL into Windows via USB-C, this Bulk Transfer device appears as ‘Other Device’ but its driver does not load. When the USB-C cable is unplugged this ‘Other Device’ disappears from the Device Manager list. This issue was raised 4 December on a Line 6 forum but no resolution was documented on that post and its replies or subsequently that I can find. It has not been addressed by Line 6 yet in Stadium App 1.2 for Windows. Solution: The Line 6 developers need to fix the USB Bulk Transfer driver they are distributing with the Windows version of Stadium App 1.2. Workaround: The Stadium 1.2 app and drivers provided for Mac OS work. If you are a Windows user, you will need to ‘phone a friend’ who has a MacBook, load Stadium App 1.2 on it, make your USB-C connection between MacBook and StadiumXL, launch the Stadium App, and connect to Stadium XL so the current firmware version can be detected. If the Stadium XL is not already at 1.2 firmware version, you will be prompted to download and transfer firmware 1.2 to the Stadium XL. Background: After unboxing my Stadium XL on Monday morning, I spent hours as a Windows user trying to get Stadium App 1.2 to connect with my Stadium XL without crashing. On Tuesday, I brought my Stadium XL to work and borrowed a colleague’s MacBook Air to do the 1.2 firmware update. All went smoothly. As a hobbyist, I bought the Stadium XL specifically for the Showcase feature which is what distinguishes the Stadium XL from all other modelers at present. I was going to go for the Fender ToneMaster Pro until I randomly came across a YouTube video discussing Showcase. I was keen to immediately update to firmware 1.2 to start experimenting with Showcase. I have a 4Cast MVP stand-alone MIDI-controlled video playback ‘jukebox’ coming on Saturday which I plan to USB-C connect with the Stadium XL and recive MIDI note commands from Showcase flags to start the music video that goes with the song I am currently murdering with my guitar ‘playing.’ I will be using an AI stem extractor to get stems from the music video’s audio track to include in Showcase so the audio and video will remain sync. Obviously, Windows users need the Line 6 developers to fix the Windows distribution of the Stadium App going forward so it includes a USB Bulk Transfer driver that Windows can load. I can live with firmware that is ‘buggy’ on the features front because Line 6 has a proven track record of solid support for the original Helix over the last 10 years but when the USB bulk transfer driver needed for Windows users to apply firmware updates over time to fix these bugs is itself broken out-of-the-gate, that is a significant problem.

Update: it's a known issue. Phone support walked me through updating using USB-C to USB-C connected cable to my Mac, as described in another post (just in case any one else runs into this). Once updated and rebooted it showed QR code and 6 digits but didn't need it, just signed in with my username and password. Downloaded the stadium app and all working.

This is probably a known issue. Several bugs with Snapshots have been identified and will be fixed in a future update. I suggest you get along as best you can until then and revisit this after the update.

Here’s the only difference I did which has worked for me. Hope it works for you too. Delete songs (maintenance menu) backup (maintenance menu) factory reset (maintenance menu) restore backup (maintenance menu) reimport (Stadium App)

I didn't think to ask ... Mac users will have to chime in for that OS, however, I know that Windoze (not a misspelling this time) likes to "control" power settings for many devices, USB, network etc. For my wired and wireless device properties I always make sure I DO NOT allow the computer to turn off the device to save power. Here is an example for my wi-fi device but the same is true for the wired network device. Just in case this helps for those not aware of this setting. For those aware of this setting please forgive me. jpd

I had the same problem. I was using the front USB ports on my tower PC but discovered that their power was less than the rear USB port. Apparently this is very common, is not a fault, but has to do with how some PC's wire up the front USB's. The rear ports were already 'occupied' but as I needed some more easy access front USB ports anyway, I bought a 4 way USB hub for a few pounds, and connected it via a USB cable to the rear USB port so that I now have easy access to 6 ports. Pod Go Edit now works perfectly through the rear port via the hub. If you use a laptop, a mains powered hub should solve the problem for you.

Hi, As I wrote above, had the problem all the time when first got my Pod Go. Edit kept giving me disconnection messages all the time after a few minutes. Now I have the PG plugged into an external powered USB hub. Problem solved, no more disconnections. Cheers. Jay