jpdennis

haasamps, Question for you, is it not syncing to the tempo or is it off by a some measure with the meter, like dragging behind the beat? Thanks for any reply, jpd

joerch71, I use the gain at the lowest setting with the boost on for one type of "boost" and the opposite (gain adjusted up slightly with the boost off) for another setting. Once I deactivate the kinky boost I can still keep my volume normalized for the amp I use and its settings. Any additional volume adjustment is via my guitar pots. While I haven't viewed all the YouTube tutorial videos on Gain Staging , there are some out there when I just did a search prior to replying to your post. Hope this helps. jpd

Also, this seems to be a cosmetic issue since I can turn the EQ off and it does stay off from a sonic perspective but it visually shows being on when I return to the EQ settings and the visual shows it being on even though it is off sonically. Then I have to turn it off and back on to reactivate it sonically.

lwilliams, Thanks for the follow up. I received the same response from support. In fact I was told that the EQ settings aren't saving once powered down for the tech. I was scratching my head because I was able to create this initially using the latest 1.2 FW. But for some reason once I built over 12 presets it doesn't response to nay changes. I am looking forward to the next FW update for this and a few other fixes, hopefully. jpd

acarrasquillo77, From the current readings in this forum there is an issue with the app that is being looked into by Line 6 support. Most are just using the Stadium XL device, as I am. I create the snapshot, save it, then move to the next snapshot I want to create, save, etc. It has worked for me so far. For any fine tuning once the snapshots are saved and working as expected I will use the app only for minor adjustments. I save the snapshot in the app then, after saving each snapshot, I use the mouse to click on the output block, select snapshot 1, and save the preset one last time. This method, while slightly tedious, has worked 99% of the time for me. jpd

lwilliams, Have you created a ticket to "poke" support on this issue? The more of us havign this issue who create tickets the higher up the "fixit" ladder it will go. I have been restoring from backup. I may try resetting to default and then manually setting up the global EQ to see what happens. If I only use the default settings it seems to work as expected. I have discovered using the default settings works with the App. But once I restore the sync between the app and the Stadium is sporadic at best. I have been told they are working on the sync part for 1.3 and to wait for the next upgrade ( possibly right after NAMM if not just before or during). jpd

As a follow up, in my device the global EQ is set to on for the phones and off for the 1/4 and XLR. I cannot change the state of those three device settings. I have added this to the ticket.

I have an issue with the global eq not staying off. I created a support ticket. Here is what my tickets says; "This isn't a software issue on the PC, it is a physical device issue at the Stadium XL. I cannot get the Global EQ to stay off once I set it to off. I will set the EQ off for, say the phones, then go back to my preset. When I use the hamburger menu on the stadium device to look at the global eq it is still on even though I stayed on the global eq screen while rotating through presets to see if it would turn on during this process. While it appeared to stay off once I viewed the home screen of the preset and then used the hamburger menu to view the EQ it was still engaged. I even turned it off in the Stadium App but it would not stay off on the device. I've reset the Stadium to default three times and haven't had any luck. Thanks for any feedback. Dennis" Anyone else noticing this issue? I did a search in the forum first but did not see an exact thread for this. jpd

Yesterday my Stadium "dropped of the face of the home network" according to the app on my pc. I was able to use my Line 6 credentials to log into the Stadium Device as well as check for the ip address in the wi-fi area. I could even see the Stadium device in the mesh network app and router web-browser portals. My network scan device included the Stadium in its list of devices. I could log into the desktop stadium app. But the desktop stadium app could not see the Stadium even with a manual ip entry. I even tried resetting the Stadium to default (after a backup). That didn't work. Then I used the maintenance to forget the wi-fi & Bluetooth only. No luck. My solution was to use the mesh network app to reboot the mesh network. Could be some associated mac_add arp table issue. I am just speculating. I am glad the reboot of the mesh network worked. Maybe I will have to reboot every month or two; something I've read is a "maintenance" checklist for the mesh networks. Not sure but I am happy it does connect to the app now. I thought I'd share. On a side note the Stadium is recognized as a Valve SteamDeck device; a discontinued device. Gamers unite! LOL jpd

Are you saving the preset each time you create a snapshot as well? Are you using the app to create the snapshots or the stadium device? Thanks for any reply, jpd

I am using the same Gator case I purchased for my Helix Floor. The barrier strip is attached via a Velcro bond. Moving it to better contain the Stadium was straight forward. I am glad I kept the case when I sold the Helix Floor during the waiting period for my Stadium.

NoSlowhand, I am glad you have this resolved. Thanks for including the detailed corrective measures you took. Everything we share in this forum can benefit someone. jpd

NoSlowhand, I have noticed the Line 6 servers are a little slow today, though it could be my area in Northern California as well with respect to our ISP. And forgive me if you've tried the following with no luck as well. I had a problem when I was trying to log into the Stadium using my username and password. My problem was that I am using MFA and had to disable MFA then reset my password. That solved the manual log in problem. If you do not use MFA via an authenticator like Google or Microsoft, etc then next ... I assume you've already installed the latest Stadium App (called Helix Stadium version 1.2.0 release date 12/17/25 and it includes the ASIO driver). Here is a youtube video of another person having the same issue of not being able to update via QR or manual log in. The second part shows the steps he took to get the Stadium updated. He shows the usb-c to usb-c cable plugged and connects to the Stadium via the usb cable as his connection choice but still says to make sure the Stadium and the computer is on the same wi-fi network. ( I have added another user's solution below this video ) Another user did the following "My solution to the problem was to install Line 6 Central on my laptop, boot Stadium XL in maintenance mode and disable wifi and bluetooth, reset to factory settings. Restart and reinstall firmware 1.2 over USB. That seems to work." Good luck Dennis

blindner, Have you used the right arrow to expand the settings on the tuner once the string offset is enabled? Or are you speaking of something else that I am not understanding?

These are great ideas to open a feature request for.

bbehrens, I have been creating the presets on the Stadium XL device itself for the same reason. I use the Stadium App if I want to fine tune the color, move presets to reorder, copy, make templates, etc. In my creation environment I have the Stadium XL on a platform next to my computer. So far, with the Stadium App closed, I've not had an issue with preset creation connected to Wi-Fi and connected via USB to my DAW or for playback/play along with music files or videos. I disconnect the usb-c cable when I launch the Stadium App to fine tune and test the global EQ on/off as well as the learning process I am going through with Showcase. Fun fact, I thought I was a novice with Showcase but it turns out I am a pre-novice ... I was going to say sub-novice but it didn't have the same ring ;-) jpd

Yanu91, are you doing this using the four cable method? On the rear of the ht5r mkii, what is the effects level set to (-10dB pushed in or +4dB out position)? If it is pushed in try setting it to the +4dB level setting. jpd

All, the support team just posted back in my ticket concerning this issue as well as the snapshot lockup issue ticket that an update is coming out shortly and for me to be on the lookout to update immediately once released. FYI jpd

vinny_x3, Have you thought about using a verbal cue track for the first measure lead-in into a song? jpd

drexell, I am just now working with Showcase and have to export each track as a stem from Reaper. Once I have up to 8 stem files exported per song I can then import into the Stadium XL per song to use the Matrix for level setting what I want to hear (bass, drums, keyboards, click, cue, etc.). I am still a novice with Showcase so I have yet to get to any big problems. jpd

gavinashun, great question. I believe the instruction state that 32Gb HC (UC 1 or higher speed class) is the minimum to use. There are others members in this forum that have said they have read or heard the Stadium can use a 1TB microSD. I know 512Gb is reported to work in this forum. Here is stapani's comment ... You will have to use the maintenance mode to format the microSD before use according to the manual. jpd

vinny_x3, is this for showcase use or just in general? jpd

gavinlewis, you can try reducing the amp "ripple" setting as well to see if this helps.

Jimbles_81, Are you saying you'd use the XLR out L & R for 2 and 1/4 L & R for 2? If so then enjalt said it best (and I am expanding) - the headphones out would go to your IEM and you'd use the matrix per output (XLR, 1/4, headphones) to level what you want and what you do not want heard per output. Forgive me if I am completely misunderstanding your request. jpd

Forgive me if you've already attempted this. Have you looked into the control permissions in System Settings -> Privacy & Security using the "allow accessories to connect" feature? We used to use this at work for cameras, microphones, etc. so we could limit their use to a specific app. It was a little painful when non-Apple devices had to be allowed for one app and then denied for all others. I do not recall the terminal command, however, I realize you are asking for a "relatively simple workaround". Any high-level Mac experts out there? jpd