sACN (E1.31) Configuration

CueSync's sACN DMX-over-IP output sends DMX to any sACN receiver on your network. To drive a console's own commands, use OSC.

sACN vs Art-Net

Both sACN (E1.31) and Art-Net carry DMX512 data over Ethernet. Here's when to choose each:

For festival-scale rigs and architectural installations, sACN is generally preferred. For single-console club setups, Art-Net is more common.

Setting Up sACN in CueSync

1. Choose Output → Add Output… (or open Network → Outputs and click +).
2. Pick sACN (E1.31).
3. Configure, then save — the output connects at once:

Priority System

sACN's priority system allows multiple sources to output to the same universe. CueSync's output wins when its priority value is highest. Useful for:

• Backup/failover — set console at priority 100, CueSync at 110 to override during AutoPilot
• Manual override — temporarily lower CueSync's priority to allow manual console control

Multicast vs Unicast

Multicast (recommended): sACN uses 239.255.x.x addresses derived from the universe number. All devices on the network that subscribe to that universe receive the data. No per-device configuration needed.

Unicast: Sends directly to a specific IP. Use when your network blocks multicast or when you need to target a specific receiver without broadcasting to all.

Testing

Add a Manual-trigger cue with an sACN action (a channel and a value of 255), test-fire it from the Cues screen, and confirm the level at the receiver. Test Connection in the output editor checks reachability, and the Network screen's Monitor tab logs connection events. CueSync announces the universes it is driving, so most consoles and nodes list it in their sACN source list.