Art-Net vs sACN: which should you use?

The short answer

Both Art-Net and sACN carry DMX over Ethernet. Choose the protocol your nodes, consoles and venue already speak. If you are starting a dedicated lighting LAN from scratch, sACN multicast is often easier to keep contained. Art-Net remains extremely common on nodes, visualisers and older rental inventory.

Addressing, universe count and a wired show network still matter more than the logo on the packet. A clean Art-Net unicast install beats a sloppy sACN stream dumped onto guest Wi-Fi.

What actually differs

Art-Net is a UDP protocol widely implemented by nodes, media servers and visualisers. Broadcast discovery is convenient on a small LAN and dangerous on a shared office network. Many stacks default to broadcast until you lock destinations.

sACN (ANSI E1.31) is DMX over ACN. Multicast lets many receivers join a universe without blasting every device. Unicast is available when you need a point-to-point stream. Priority in the packet lets a house system and a guest desk negotiate who owns a universe.

Universe numbering conventions differ. Art-Net historically talks in net / subnet / universe. sACN uses a 1-based universe number. Always check what “universe 1” means on both ends. Off-by-one errors waste more nights than protocol theory.

Hardware and politics

Match the receiving hardware first. If the venue’s nodes are Art-Net only, send Art-Net. If a festival insists on sACN multicast for a shared backbone, send sACN. Dual-protocol nodes exist; use them as translators rather than as an excuse to run both dialects everywhere.

Visualisers often speak Art-Net first. That is useful in pre-vis and useless as proof that the physical node is in the same universe. Test the real output path.

Neither protocol makes Wi-Fi a good DMX transport. Keep lighting traffic on a wired VLAN or a physically separate switch. Phones and tablets can live on a different SSID for a control surface.

A decision checklist

Inventory the nodes. Count Art-Net-only, sACN-only, and dual. That inventory is the decision.

Ask whether the network is a five-port show switch or a managed venue backbone. Multicast needs IGMP discipline on the latter. Broadcast Art-Net is unacceptable on the latter.

Decide unicast versus multicast (or broadcast) after you know IPs. Then lock firewall rules: UDP 6454 for Art-Net, the sACN data port your stack documents (often 5568).

Write the universe map on paper: which desk universe lands on which node port, which fixtures sit on that XLR. The protocol choice is one line on that page.

You can change your mind later

The patch — start addresses and personalities — survives a protocol swap. You are changing the truck, not the cargo. If a touring LD arrives with a different dialect, convert at the edge rather than re-addressing every fixture at 16:00.

Myths that waste a load-in

“sACN is always better.” Not on a bag of Art-Net-only nodes. “Art-Net is obsolete.” Tell that to the visualiser and the 2016 node that still works. “More universes need a better protocol.” They need more node ports and a switch that is not also running the bar TVs.

“We can share the office VLAN if we use unicast.” Unicast is politer. It is not isolation. A mis-aimed stream or a discovery burst still lands on the wrong neighbours. Dedicated copper is still the adult choice.

If you are the person writing the rider, specify both dialects if you can, plus a universe map and a spare unmanaged switch. That is more useful than a paragraph about protocol philosophy.

A side-by-side lab

If you own a dual-protocol node, send the same desk universe as Art-Net to port 1 and as sACN to port 2 on different nights. The fixtures should look identical. The difference you feel is configuration pain, not brightness. That is the lesson: pick the dialect that the room already configured, not the one a forum prefers.

When both fail, the problem is almost never “we chose the wrong standard.” It is subnet, NIC, firewall, or universe numbering. Work those before you convert protocols in a panic at 20:00.

What to put on the rider

List the dialects the house can receive, the number of universes you will send, and whether you need a spare switch port. “Art-Net or sACN, two universes, dedicated switch, no guest Wi-Fi” is a complete lighting-network rider for a small act.

If you can only send one dialect, say so in bold. Arriving with Art-Net-only software into an sACN-only house is a converter problem, not a talent problem — but only if someone brought a converter.

Related

• What is Art-Net? →
• What is sACN? →
• Patching →