Free forever·no account, no tracking, no third-party requests ·open data, free API
showstack / compare / dmx512-vs-sacn

DMX512 vs sACN

What is the difference between DMX and sACN? Below is every field we hold on both, side by side. Each one is sourced on the individual entry, and anything nobody could source is left blank rather than guessed.

Side by side

DMX512sACN
Categorylighting-controllighting-control
FlowControl — small, urgent, must arriveControl — small, urgent, must arrive
PortsUDP 5568
Transportrs485udp
Multicastno239.255.0.0/16 (IPv4, universe in low two octets), FF18::83:00:00:00/104 (IPv6)
AddressingOne universe = 1 start code plus up to 512 slots of 8-bit data, refreshed up to about 44 times per second.512 slots per universe; universes 1-63999, plus 64214 for E1.31 discovery.
Spec availabilityopen-publishedopen-published
StewardESTA (Entertainment Services and Technology Association)ESTA (Entertainment Services and Technology Association)
First published19862009
Statuscurrentcurrent
Our confidenceverifiedverified

Both are control flows. Latency and loss on the messages that fire once. A repeating level survives a dropped packet; a GO does not. That applies equally to either, so it is not a discriminator here.

Speaks both (41)

These are the safe choices if you have not committed to either, or need to bridge the two.

DMX512 only (12)

sACN only (35)

What goes wrong with DMX512

DMX is RS-485 and wants 120 ohm impedance cable with a terminator at the far end. Microphone cable works until the run is long or the rig is noisy, and then it fails in a way that looks like a fixture fault.
There is no error detection. A corrupted slot is simply acted on. Flicker that follows no logic is usually a data integrity problem, not a fixture.
Star topology is not part of the standard. Daisy chain, or use a real opto-splitter. Passive Y-splits are the source of an enormous amount of unexplained behaviour.
Start code 0x00 is dimmer data. Other start codes exist (0xCC is RDM), and a device that ignores start codes will act on RDM traffic as if it were levels.

What goes wrong with sACN

Multicast without IGMP snooping configured on the switch turns into a broadcast storm. This is the single most common cause of "the network died when we patched the second console".
Priority is per-universe (0-200, default 100) and sources with equal priority get merged by the receiver, not by the sender. Two consoles at default priority will fight.
Universe numbering is 1-based here but many products expose a 0-based index internally. Always confirm against the receiving device, not the console.

Sources

Disagree with any of this?

Every claim above comes from one of the two entries and carries a source. If one is wrong, correcting it is a single file and it fixes this page automatically. Edit DMX512 or edit sACN.