NyxResonance streams audio across your local WiFi using standard IP multicast — no specialist radio hardware, no internet connection at the venue. Here is the router we recommend, what an existing venue network needs, and a full technical reference for IT teams.
The console publishes each channel to a multicast group on the local network. Any number of phones can join the same group — so your network load stays flat whether ten people or three hundred are listening.
The operator console sends each channel to its own multicast group — three channels total around 480 kbps, sent once.
Each phone subscribes to the group for the channel it wants. The network forwards one copy to every listener.
Adding listeners adds no bandwidth. The only requirement: console and phones on one flat segment that forwards multicast.
One inexpensive consumer router that we have set up, configured, and verified end to end. No admin login, no internet — power it on, plug in the console, and attendees connect to its WiFi.
As an Amazon Associate we may earn from qualifying purchases. This does not affect the price you pay.
The Archer AX3000 is the only router we have tested. It's the one device we've verified against the full audio path. Other routers and access points that meet the requirements below should work, but we haven't tested them and can't guarantee they will. If you use different hardware, you do so at your own risk — test it before a live event.
NyxResonance uses ordinary IPv4 multicast over WiFi — the same mechanism as IPTV and AoIP. To run it on a managed network, the console and every attendee device must share one Layer-2 segment that forwards multicast to wireless clients. These six points are the ones that actually break deployments, in rough order of how often they're the cause.
Guest and enterprise WLANs often enable client (AP) isolation, which stops wireless clients receiving each other's traffic — silently blocking all audio.
Console and attendees must share one subnet and VLAN. Just as important: keep that segment free of internet traffic. Multicast audio is never retransmitted, so a single phone backing up photos or streaming video can grab the airwaves in bursts and delay an audio packet past the buffer — heard as a dropout. This happens at one channel as easily as twelve.
If switches run IGMP snooping, the VLAN also needs an active querier — or snooping prunes the groups and audio cuts out after the query interval.
Where APs support it, enable multicast-to-unicast (Ubiquiti "Multicast Enhancement", Aruba/Cisco DMO) — it converts to per-client unicast at full rate.
If ACLs are in play, permit the multicast range 239.1.1.0/24 on UDP 5004 (audio). DHCP must cover the segment.
NyxResonance runs 3 channels today. Listeners are free — multicast sends one copy to any crowd size — so the ceiling is channels, set by your network's basic (multicast) rate, not its headline speed. A default 2.4 GHz SSID (1 Mbps basic) leaves little headroom; a 5 GHz SSID with legacy rates disabled (~6 Mbps basic) has room to spare as we add more channels.
Everything an IT team needs for firewall rules, QoS, or multicast policy. All traffic is IPv4 UDP within the local segment — none of it leaves the venue network.
| Channel | Multicast group | Transport | Codec |
|---|---|---|---|
| Blue · Channel 1 | 239.1.1.1:5004 | Multicast RTP / UDP | Opus 48 kHz stereo |
| Green · Channel 2 | 239.1.1.2:5004 | Multicast RTP / UDP | Opus 48 kHz stereo |
| Red · Channel 3 | 239.1.1.3:5004 | Multicast RTP / UDP | Opus 48 kHz stereo |
| Service / profile | Value | Notes |
|---|---|---|
| Console discovery (optional) | 224.0.0.251:5353 | mDNS — manual setup works without it |
| Bitrate per channel | ~160 kbps | Stereo Opus, in-band FEC enabled |
| All three channels | ~480 kbps | Sent once via multicast, regardless of crowd |
| QoS marking | DSCP EF (46) | Maps to WMM Voice — honor it at the edge |
| Jitter buffer | ~160 ms | Prebuffer absorbs WiFi variance |
| Multicast scope | Local segment | Never routed to the internet |
Prefer not to use the recommended router? Any access point can work if it meets every requirement below. We haven't tested other devices — treat this as the spec to check yours against, and always trial it before a live event.
239.1.1.0/24) between wired and wireless clients on the same subnet.Meeting this checklist makes a device a good candidate, but only the TP-Link Archer AX3000 has been verified by us. Validate any alternative with a full audio test — console live, multiple phones listening — before you rely on it at an event.
A five-minute check that catches almost every network problem before attendees arrive.
If your venue network is complex, reach out before the event and we'll help confirm the configuration. The simplest guaranteed path is always the recommended router on its own dedicated segment. Email us at support@nyxresonance.com.