Search the Community

FWIW, this is an AI summary of what I just went through to finish setting up my Stadium XL: Oh yeah...and I just bought a Stadium XL. Solved: Helix Stadium XL wouldn't connect to Windows 11 app (Code 28 / Wi-Fi Connection Required / Norton 360 Deluxe) I wanted to post my experience in case it helps someone else. System: Windows 11 CyberPower PC (Ethernet connection) Helix Stadium XL (Wi-Fi connection to the same home network) Norton 360 Deluxe Symptoms Connected the Stadium XL to the PC with a USB-C cable. Windows did not play the device connection sound initially. Device Manager showed: Audio devices were present. Helix Stadium Bulk Transfer appeared under Other devices with a yellow exclamation point. Device status showed Code 28 (drivers not installed). The Helix Stadium desktop application displayed "Wi-Fi Connection Required" even though both the PC and Stadium reported they were on the same network. What fixed the USB driver problem The Stadium itself had a notification (hamburger menu) to install a downloaded firmware update. After installing the update: Windows immediately played the device-connected sound. The yellow exclamation point disappeared. "Helix Stadium Bulk Transfer" disappeared from Other devices. A new Line 6 category appeared in Device Manager with Helix Stadium XL, and Windows recognized the device correctly. So if you see a Code 28 error, make sure the Stadium firmware is fully updated before assuming there's a USB hardware problem. What fixed the Wi-Fi connection problem The Helix Stadium application still reported "Wi-Fi Connection Required." After troubleshooting, I discovered the issue was Norton 360 Deluxe Smart Firewall. As a test, I temporarily disabled Smart Firewall for 5 minutes. The Helix Stadium application connected to the Stadium immediately. That confirmed the firewall was interfering with local network discovery. Interestingly: Program Control entries were already set to Allow. There were no custom Traffic Rules blocking Line 6. My Ethernet network profile in Windows was already set to Private. After additional troubleshooting, everything began working normally and the application now connects successfully. Suggestions if you're having the same problem Update the Stadium firmware first. If Device Manager shows Code 28 for Helix Stadium Bulk Transfer, don't panic—the firmware update may resolve it. Verify your Windows network profile is Private. If you're running Norton 360 Deluxe, temporarily disable Smart Firewall as a test. If the editor immediately connects, you've confirmed the firewall is involved. Hopefully this saves someone else a few hours of troubleshooting.

I have two MIDI foot controller devices which have FIXED MIDI CC numbers for each stomp. Namely ActitioN and the IK BlueBoard. https://line6.ideascale.com/a/dtd/HELIX-NATIVE-Snapshot-Control-support-MIDI-pedals-with-FIXED-CC/938764-23508?submitted=1#idea-tab-comments Trouble is the SNAPSHOTS feature in HM 2.6 uses a FIXED CC value - CC#69 follows by a Value 0-7 for each snapshot. So say i want to use 4 stomps for SNAPSHOT 1-4 - my foot controller sends four DIFFERENT FIXED CC values ! I use Ableton - so initially had a look for MAX4LIVE devices that can remap one CC to another - but found none that could remap the different CC values ( 76-79 in my case ) to 69 - while at the same time setting VALUE to 0 when I send 76, 1 for 77, 2 for 78 and 3 for 79. So my attempt to use MAX4LIVE MIDI conversion add ons failed. What we really need is a way in HN to either have a LEARN function so to change snapshots we can use the CC values of our choice ( and ignore value ) OR.... have a built-in CC remapping facility page where HN automatically transforms incoming ( different ) CC values to 69 and the appropriate value. https://line6.ideascale.com/a/dtd/HELIX-NATIVE-Snapshot-Control-support-MIDI-pedals-with-FIXED-CC/938764-23508?submitted=1#idea-tab-comments

Hey, I made this post because this is something I have been having troubles with over 3-4 years. I have had many problems with the toneport UX2 version (I work with a windows 7 64 bit system). But two problems have never gone away: a crackling popping sound after X number of seconds and after a couple of hours it would crash and freeze my volume, making me restart the computer. In my case I noticed that the crackling sound may appeared when I was doing something on windows. After searching a lot of forums I found a program that could analyze the DPC latency of a system: go here http://www.thesycon.de/deu/latency_check.shtml It will give you information if your system can handle real-time audio/video service. By disabling devices in device manager one after another, I had found my problem for the crackling sound. After disabling my ethernet driver it dropped right into green and I have never heard a crackling sound again. After a day the volume bar hasn't crashed either. After research I think this comes because windows cannot handle a continues data stream over USB. This comes from a security update with a bug. You can try to restart the audio service through CMD with the following commands: net stop audiosrv net stop AudioEndpointBuilder net start audiosrv net start AudioEndpointBuilder The idea is that you don't have to restart your computer but just your audio drivers. I'm just really happy that I can listen to music without ANY crackling/popping noise and just enjoy this good audio card. I hope I helped some people with this, because it sure did help me. Bye!