ArtNet and sACN encode/decode

Node Editor workflow: ArtNet and sACN encode/decode

For programmatic DMX control — integrating with lighting consoles, generating DMX values from logic, or bridging between protocols — use the encode and decode nodes in the Node Editor.

Sending ArtNet from the Node Editor

Build a graph like this:

1. Create your DMX channel values as a Pack of integers (0–255) or a Signal array.

2. Connect the values to the DMX signal or DMX data input of a Network:ArtNetEncode node. Set the Net (0–127), Subnet (0–15), and Universe (0–15) on the node to match your target device.

3. Connect the Art-Net buffer output to a Network:UDPSender node. Set the destination IP and port 6454.

Receiving ArtNet in the Node Editor

1. Add a Network:UDPReceiver node listening on port 6454.

2. Connect its output to a Network:ArtNetDecode node. Set the Net, Subnet, and Universe to match the incoming stream. The node only passes through packets that match all three values.

3. The DMX data outputs (Pack and Signal) carry the decoded channel values (0–255) for use in your graph.

sACN encode/decode

The Network:sACNEncode and Network:sACNDecode nodes work the same way as their ArtNet counterparts, with one key difference: sACN uses a single Universe number (1–63999) instead of the ArtNet Net/Subnet/Universe hierarchy. sACN packets are typically sent to the multicast address 239.255.x.x (derived from the universe number) on port 5568.

Use sACN when your infrastructure requires multicast delivery or when integrating with systems that prefer E1.31 over ArtNet (common in architectural lighting and ETC Eos environments).

How Backstage drives lighting — how the two protocols differ, and which of Backstage's two routes fits.

Node Editor nodes

The ArtNetEncode node has three on-node settings: Net (0–127), Subnet (0–15), and Universe (0–15). The ArtNetDecode node has the same three settings and only passes through packets matching all three. The sACN nodes have a single Universe setting (1–63999).