Art-Net vs sACN — Lighting Network Protocols Comparison
Quick answer
Art-Net and sACN are protocols used to transport DMX512 data over IP networks. Art-Net was developed by Artistic Licence and supports both unicast and broadcast transmission. sACN (Streaming ACN, ANSI E1.31) is an ESTA standard using IP multicast as its primary transport, with support for unicast and built-in source priority mechanisms. Choosing between them depends on system scale, network topology, and redundancy requirements.
Overview
The increase in control parameters across modern lighting fixtures renders direct RS-485 DMX cabling physically inefficient. Transporting DMX512 over Ethernet allows consolidating hundreds of universes over unified network infrastructure. This article breaks down the transport layers of Art-Net and sACN, addressing mechanisms, multicast traffic handling, and network hardware requirements.
Who this article is for
- •Lighting Designers
- •System Integrators
- •Network Engineers
- •Technical Directors
- •Event Support Crews
What you will learn
- •Data transport mechanics of Art-Net and sACN protocols
- •Differences between Broadcast, Unicast, and Multicast delivery models in lighting networks
- •Operation logic of priority levels and HTP merging in sACN
- •Role of IGMP Snooping and IGMP Queriers in multicast traffic management
- •Physical and network limits of bandwidth and cable segment distances
Introduction
A single DMX512 universe contains 512 data slots. Pixel-mapped LED arrays and complex moving heads demand extensive channel counts, requiring modern control systems to manage dozens or hundreds of universes.
Transporting control data over Ethernet addresses physical cabling constraints. However, delivering DMX512 over IP introduces new engineering challenges: traffic routing, switch processing loads, frame synchronization, and multi-console arbitration.
Art-Net protocol mechanics
Developed in 1998 by Artistic Licence, Art-Net encapsulates DMX512 data into User Datagram Protocol (UDP) packets over port 6454.
Addressing and versions
- •Art-Net 1 and 2: Used broadcast transmission, sending every packet to all devices within the subnet segment. At higher universe counts, this creates substantial processing load on network interfaces and node CPUs.
- •Art-Net 3: Introduced 15-bit addressing, expanding protocol address space to 32,768 universes. Unicast transmission became the standard practice, directing packets straight to receiver IP addresses.
- •Art-Net 4: Expanded gateway DMX port management, improved discovery mechanisms, and refined RDM handling. Art-Net 4 enables combining discovery and RDM management via Art-Net with live control streaming via sACN.
Broadcast and Unicast in Art-Net
Selecting between broadcast and unicast in Art-Net depends on source count, receiver layout, universe volume, and frame refresh rates. Broadcast is suitable for small networks with few universes. In larger systems, unicast prevents flooding switch ports with unnecessary traffic.
For unicast transmission, the console must know receiver IP addresses and universe-to-port mapping assignments.
sACN (Streaming ACN) mechanics
sACN (ANSI E1.31) is an ESTA standard representing a lightweight subset of Architecture for Control Networks (ACN, ANSI E1.17). It transmits data over UDP port 5568.
Addressing model and Multicast
The primary universe addressing mechanism in sACN is IP multicast. Packets are transmitted to designated group IP addresses within the 239.255.0.0/16 range, where the final two octets correspond to the universe number.
- •Universe 1 maps to IP
239.255.0.1. - •Universe 200 maps to IP
239.255.0.200.
The transmitter does not need to know individual node IP addresses. The console broadcasts to the multicast group, and nodes subscribe to their assigned universes. The ANSI E1.31 standard also permits direct unicast transmission to specific IP addresses.
Multicast traffic management and IGMP
In unconfigured L2 network segments, switches process multicast traffic like broadcast. To constrain packet distribution, IGMP Snooping is used.
A switch running IGMP Snooping monitors node join requests (IGMP Reports) and forwards a universe's multicast stream exclusively to ports with active subscribers. To maintain membership tables, an IGMP Querier must exist in the network (L3 routers, specialized managed L2 switches, or network gateways). Without an active IGMP Querier, switch group subscriptions can time out, causing data loss.
Priority levels and source arbitration
In sACN, each packet includes a universe priority rating from 0 to 200 (defaulting to 100).
- •When receiving the same universe from multiple sources, the receiver selects the stream with the higher priority.
- •When source priorities are identical, receiver settings dictate behavior (most commonly applying HTP merge).
With HTP (Highest Takes Precedence), the receiver evaluates values for each individual DMX slot across active matching-priority sources and outputs the highest value.
The standard also includes optional per-address priority extensions (per-channel priority) supported by specific hardware implementations.
Performance and bandwidth comparison
Bandwidth and processing load
Data load per DMX universe depends on transmitted slot counts, frame rates (packets per second), and UDP/IP/Ethernet header overhead. Transmitting 512 slots at 44 Hz generates approximately 90–100 kbps per universe at Layer 2.
Theoretical bandwidth throughput limits:
- •A 100 Mbps network can technically transport several hundred universes.
- •A Gigabit network (1 Gbps) theoretically holds several thousand universes.
In practice, system capacity is constrained not only by line bandwidth, but by node CPU processing capability (packets per second, PPS) and switch forwarding performance.
Frame synchronization
Synchronizing output across multiple universes during complex cues uses protocol-level sync mechanisms:
- •Art-Net 4 uses the ArtSync packet.
- •sACN uses E1.31 Synchronization Packets.
Receivers buffer incoming frames in local memory until the synchronization trigger packet arrives.
Network architecture requirements
- •Art-Net Unicast: Functions on standard L2 networks. Requires accurate static IP addressing or managed DHCP configurations.
- •sACN Multicast: Requires managed switches with IGMP Snooping enabled and an active IGMP Querier in the L2 segment to prevent multicast flooding.
- •L3 Routing: Routing sACN multicast across separate IP subnets requires multicast routing configurations (such as PIM).
Common mistakes
- 1.Unmanaged switches for sACN multicast: Unmanaged hardware floods multicast traffic to all ports, overburdening node processors and Wi-Fi access points.
- 2.IP address collisions in Unicast Art-Net: Duplicate IP assignments cause ARP anomalies and packet loss.
- 3.Missing IGMP Querier in multicast networks: Without regular Querier queries, switches prune multicast groups, interrupting data delivery.
- 4.Matching priorities across multiple consoles: Leaving primary and backup consoles on identical default priorities (100) forces receivers into HTP merging rather than seamless failover.
Decision matrix: Art-Net vs sACN
| Parameter | Art-Net 4 | sACN (ANSI E1.31) | Application Context |
|---|---|---|---|
| Primary Transport | Unicast / Broadcast | Multicast (Unicast supported) | Multicast simplifies source setup; Unicast bypasses IGMP requirement. |
| Source Configuration | Requires target node IP (in Unicast) | Assign universe number | sACN decouples transmitter setup from receiver IP addresses. |
| Arbitration & Redundancy | Basic merge mechanisms | Built-in priorities (0–200) | sACN provides standardized source arbitration. |
| Switch Requirements | Basic L2 switches (for Unicast) | Managed switches with IGMP Snooping/Querier | Art-Net Unicast is simpler on unmanaged hardware. |
| Legacy Compatibility | Extensive legacy support | Supported by modern equipment | Art-Net remains widespread across legacy media servers and fixtures. |
Best practices
- •For large touring rigs and fixed installations, standardize streaming DMX control data on sACN.
- •Segregate lighting traffic on dedicated VLANs or separate physical cabling. Avoid mixing audio protocols (Dante, Ravenna) with DMX over IP without QoS design and bandwidth planning.
- •When deploying sACN multicast, utilize enterprise managed switches and verify IGMP Snooping and Querier operation.
ART-R recommendations
ART-R recommends infrastructure designs supporting both protocols simultaneously.
- •DMX Nodes: Compatible DMXking hardware (such as the eDMX MAX series) natively processes both Art-Net and sACN with port routing and merge logic.
- •Control Consoles: ChamSys MagicQ consoles offer native output and reception of both Art-Net and sACN per universe.
FAQ
Can Art-Net and sACN run on the same network?
Yes. Protocols utilize distinct UDP ports (Art-Net: 6454, sACN: 5568). However, duplicating output of identical universes over both protocols simultaneously should be avoided to prevent unnecessary processing load.
What is the maximum cable length for Art-Net or sACN?
The 100-meter limit applies to physical copper Ethernet segments (Cat5e/Cat6) under IEEE 802.3 standards. The Art-Net and sACN protocols have no inherent distance limit and operate over switches, fiber optic links, or L3 networks.
Is a router required for sACN?
Within a single L2 segment/VLAN, a router is not required, but a managed switch with IGMP Snooping is. Routers are only necessary when forwarding traffic between different IP subnets.
What happens if a node loses network link?
Behavior depends on node hardware implementation. Most professional nodes offer configurable options: Hold Last State, Blackout, or triggering a standalone fallback scene.
Can sACN or Art-Net run over Wi-Fi?
Standard Wi-Fi introduces variable latency, jitter, and packet loss unsuited for real-time control. Wireless DMX systems (such as CRMX) operate over dedicated physical layers built for real-time reliability.
Why does a sACN stream drop after several minutes?
This commonly indicates a missing active IGMP Querier in the L2 segment. Without query responses, switches drop port multicast memberships.
How does Art-Net 4 differ from sACN?
Art-Net 4 incorporates discovery features, RDM management, and gateway port routing. sACN is a standardized protocol for streaming DMX data with priority management.
People also ask
- •How much bandwidth does a DMX universe use? Transmitting 512 slots at 44 Hz generates approximately 90–100 kbps.
- •Which IP address range should be used for Art-Net? Early Art-Net specifications recommended
2.x.x.xor10.x.x.xranges, but modern hardware operates across standard IPv4 subnets. - •How do I verify sACN traffic on a network? Use diagnostic software (such as sACNView) on a computer connected to the same network segment.
- •What is a DMX node? A network device converting Art-Net/sACN IP packets into physical RS-485 DMX512 signals on XLR ports.
Related articles
- •DMX Addressing & Universe Optimization
- •DMX Network Diagnostics & Troubleshooting
- •DMX512 Protocol — How It Actually Works
- •Festival-Scale DMX over Ethernet: Redundant Topologies
Related categories
Downloads
- •Network Switch Configuration Guide for sACN (PDF)
- •Bandwidth Calculator for Lighting Networks (Excel)
Glossary
- •Unicast: Transmission of network packets from one sender directly to one receiver IP address.
- •Broadcast: Transmission of packets to all devices within a network segment.
- •Multicast: Transmission of packets to a group IP address, received only by subscribed nodes.
- •IGMP Snooping: A switch feature monitoring multicast subscriptions to restrict traffic distribution.
- •UDP (User Datagram Protocol): A connectionless transport protocol providing low-latency packet delivery.
- •VLAN (Virtual Local Area Network): A logically isolated network segment on a physical switch.
- •HTP (Highest Takes Precedence): A merge method where the highest DMX slot value across matching-priority active sources is output.
Conclusion
Art-Net and sACN solve the transmission of DMX512 over IP networks, differing in addressing models, traffic management, and arbitration mechanisms. Art-Net Unicast is effective for small-to-medium setups without dedicated multicast infrastructure. sACN Multicast provides a scalable architecture with flexible redundancy when IGMP is properly configured on switches.
Schema recommendation
- •Article
- •FAQPage
- •TechArticle