Search the Community

My brother opened ticket #496504 to report this issue. He was told by Line6 that he's not the only one seeing this problem, but there are not very many. I went to see him yesterday to help him out, because I'm not having that problem. His Stadium is connected to the WiFi and logged into his Line6 account. His Laptop is connected to the same WiFi and logged into his Line6 account. However, the Laptop CANNOT see the Stadium, or loses connection to it after a few minutes. So, the Laptop can connect to Line6 through the WiFi, and the Stadium can connect to Line6 through the WiFi, but they cannot Connect to each other. I submitted all the information to CoPilot AI, including info on the router and ISP. Here is CoPilot's analysis of the situation and suggestions for solutions. Issue: Stadium editor cannot connect or loses connectivity after a few minutes even though the Stadium remains fully online. The failure is isolated to LAN discovery, not Wi‑Fi or internet connectivity. Environment: Stadium on Wi‑Fi Windows 11 editor ISP: Fidium Router: Adtran 854‑series gateway (Fidium standard) LAN subnet: 192.168.40.x Stadium maintains valid IP and Line 6 login at all times Observed Behavior: Editor initially cannot find the Stadium or loses connection after a few minutes. Stadium’s Wi‑Fi remains stable (no DHCP loss, no reassociation) Stadium retains internet access and Line6 account authentication Only local discovery fails; reboot sometimes temporarily restores it Technical Analysis: The Stadium editor appears to rely exclusively on multicast‑based service discovery (mDNS/SSDP‑style). Adtran 854 gateways used by Fidium aggressively prune or filter multicast and broadcast traffic after a short period of device uptime. This results in: Unicast traffic: unaffected Internet connectivity: unaffected Multicast discovery: silently dropped This matches known behavior of Adtran 854 IGMP snooping, multicast filtering, and band‑steering logic. Why Other Devices Don’t Exhibit the Issue: Smart TVs and casting apps use cloud‑mediated discovery or Wi‑Fi Direct, not LAN multicast. They bypass the failure mode entirely. Root Cause Summary: Stadium remains reachable at L3, but the editor cannot rediscover it because the router suppresses L2/L3 multicast discovery packets after a few minutes. Proposed Engineering‑Level Solutions: Add a direct‑IP connection path in the editor (bypasses multicast entirely). Add cloud‑assisted discovery (similar to Google Cast). Add a unicast beacon or fallback discovery protocol to avoid reliance on multicast. Any of these would eliminate dependency on consumer‑grade router multicast behavior and resolve issues with ISP‑locked gateways like the Adtran 854.

Hi, I have a problem with the connection between my Helix Rack and the controller. When I use the original Cat-5 cable, everything works fine. But I tried using another one — it's also a Cat-5e cable — and when I connect it, the controller doesn't work. It only lights up, but doesn’t respond, and the rack displays a message saying “Controller must be updated.” It never updates… I’ve tried everything, I swear. Lot od cables and lenghts… What’s interesting is that I also tested it with an old Cat-5 cable I made myself — and if I connect it one way, it works, but if I flip the connectors, I get the same problem and it doesn’t work. I'm looking for help from anyone who has dealt with the same issue. Thanks!

Help. I've have my xtPro for about a year now and I've never been able to get anything out of it bar a low volume output, forcing me to turn up the volume on the amp, which just introduces noise. Can anyone help? The connection to to amp currently used is DI Effects Return (pod) to Return (amp) and Unbalanced Analogue Output (pod) to Send (amp). Any ideas?