tcamuso

Meanwhile, you can to add your own router and run it in Access Point (AP) mode. This bypasses the gateway’s Wi‑Fi filtering while keeping the same LAN/subnet. CoPilot AI instructions and suggestions follow. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Many ISP gateways (including Fidium’s Adtran 854) aggressively filter mDNS/multicast, which the Stadium editor depends on for device discovery. The Stadium stays online, but the editor loses sight of it. A simple, reliable fix is to add your own router and run it in Access Point (AP) mode. How to Set Up a Secondary Router as an Access PointEmpty heading Connect new router to ISP gateway Ethernet from gateway LAN port → new router LAN/WAN (AP mode will clarify which). Log into the new router’s UI Connect to its default Wi‑Fi. Enable “Access Point Mode” Usually under Advanced Settings. This disables routing/NAT and keeps everything on the same subnet. Create a new SSID Example: Stadium-AP Use WPA2/WPA3. Connect the Stadium + your computer to this new SSID Both must be on the AP’s Wi‑Fi for clean mDNS. This gives you a clean, multicast‑friendly Wi‑Fi segment without changing the rest of the home network. Recommended Budget Routers (All Wi‑Fi 6, All mDNS‑Friendly)Empty heading Model Coverage Price Notes NETGEAR R6700AX (AX1800) ~1,500 sq ft $55–$70 Best value; strong 2.4 GHz; stable multicast ASUS RT‑AX55 (AX1800) ~1,500–1,700 sq ft $90–$110 Most configurable; excellent mDNS behavior Linksys MR7350 (AX1800) ~1,700 sq ft $60–$75 Good range; reliable multicast TP‑Link Archer AX21 (AX1800) ~1,500 sq ft $60–$80 Easy AP mode; very stable

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.

I'm getting this error message: So, I turned off the Memory Integrity, and the driver loads fine, but now Windows Security is complaining that my system is vulnerable as a result. What's weird is that I have this installed on another W11 system, and I am not seeing that error message. Anybody have any idea what I can do to fix this?

This is FANTASTIC! I'm going to download Reaper on my F31 workstation and try it out!

rd2rk Oh wait! The second one worked! But I have 3.0 installed now, so I don't know if it would have worked with 2.92. Meanwhile, check out this preset. It requires you to put your footswitches in stomp/snapshot mode, that is, stomps in the top four and snaps in the bottom four. Mesa-echoes.hlx

Nope. Just upgraded to 3.0, too.

Being intimately familiar with software updates, I'm gonna wait a bit before I commit. ;) I will be looking forward to seeing what those new models are in that patch, though!

OK, gang, I finally got it to work using saschafrank's suggestion to route the A/B split to a switch and set the max/min. I did this in the Helix Editor, and it took a few cycles of the assigned footswitch before it actually did anything, but now it's working. I don't know why the switch did not immediately respond to the configuration in the Helix Editor, but it seems to be working as expected now.\

Hi, rd2k. I tried to import this, but the helix editor complained saying ... I'm using V 2.92.

OK. I can have up to 8 snapshots, and each snapshot can control a myriad of parameters, but there are still only 8 possible sounds. If you have 4 snapshots and 4 stomps, then each of the snapshots can have up to 4 additional FX added to them. That's 4 factorial (4 x 3 x 2 x 1) combinations of FX for each snapshot, PLUS each snapshot with no stomps activated. That means with just 8 footswitches, I can have up to 76 different sounds. Example. You have a snapshot for lead. You've tweaked dozens of parameters in your EQ, Compression, Overdrive and Amp blocks for this snapshot. Now you have four stomp switches. One for Chorus, one for Delay, one for Slapback Echo, one for Reverb. Now you can have your lead tone dry, or with any combination of chorus, delay, slapback and reverb. AND you can do that for the other three snapshots, as well. This is powerful stuff!

Doesn't work for me. I don't know what I'm doing wrong, but I cannot select an exclusive A path or exclusive B path with one switch. If the footswitch makes one exclusive, flipping the switch ALWAYS gives me a merge of both.

No joy. I can get A-only, but when I flip the switch, I still get an A/B merge.

Is there any way to have an exclusive A or B? I can assign a foot switch to the A/B split and get 100% B, but when I toggle the foot switch to bypass the split, I get B merged with A, when what I want is 100% A. So, I want an A/B split that gives me 100% A and 0% B, or 0% A and 100% B. In truthtable terms: Footswitch State : OFF ON Output from split A/B : A only B only No merge 100%

Thanks for the reply, phil_m, but I'm already using snapshots. I've got 4 snapshots and 4 stomps. I need to have the stomps to add effects to the snapshots, which give me lead, crunch, in-between, and clean by changing settings on the compressor, overdrive, EQ, and amp blocks. So, that leaves the four stomps to add FX. Four stomps and four snapshots allows for many more combinations than just 8 snapshots. With the 4-snapshot/4-stomp configuration, I have 76 (4 * 4! + 4) possible combinations.

Thanks, zz. I'll probably have to figure some other way to effect this. Is there any way to have an exclusive A or B? I can assign a foot switch to the A/B split and get 100% B, but when I toggle the foot switch to bypass the split, I get B merged with A, when what I want is 100% A. So, I want an A/B split that gives me 100% A and 0% B, or 0% A and 100% B.