If you've worked around stage lighting for even a day you've heard someone say "patch channel 17 to the moving head." That number is a DMX channel. DMX512 is the 40-year-old standard that still runs the vast majority of lighting shows worldwide. But in 2026 it's increasingly joined by two network-protocol cousins — Art-Net and sACN. This article explains all three, when to use which, and how to design a tour-grade network.

1. DMX512 — the backbone standard

DMX512 (full name: USITT DMX512-A, standard E1.11) was first published in 1986. It defines a single-direction serial protocol running at 250 kbps over RS-485, carrying 512 "channels" per bus (hence the "512" in the name).

  • Physical layer: differential pair over 120Ω cable, XLR-5 connectors (XLR-3 in budget India installs — not recommended for serious work).
  • Topology: daisy chain. Up to 32 devices per bus; terminator (120Ω resistor) at the far end.
  • Timing: each frame = BREAK (88μs low) + MAB (8μs high) + Start Code (0x00 for standard DMX) + 512 bytes of channel data. Frame rate ~44Hz.
  • Max cable length: 300m total bus length. Shielded cat6 or dedicated DMX cable (Belden 9729 et al.).

1.1 What's a "universe"?

One DMX bus carries 512 channels. We call that one universe. Need more? Add another output. Modern stage shows run 20–50 universes; a stadium concert can touch 100+. That's where network protocols come in.

2. Art-Net — DMX over Ethernet

Art-Net was developed by Artistic Licence (UK) in 1998 as a way to pack many DMX universes onto a single Ethernet cable. Current version: Art-Net 4 (2016).

  • Transport: UDP broadcast on port 6454 (unicast also supported in Art-Net 4).
  • Capacity: up to 32,768 universes, structured as Net:SubNet:Universe (15 bits total).
  • Discovery: ArtPollReply packets — devices announce themselves automatically.
  • Framing: all 512 channels of each universe fit in one UDP packet.

Art-Net is the de-facto standard in architectural, retail-pixel and permanent-installation markets. All major LED controllers (Advatek, Falcon, Pathway, Enttec) ship with Art-Net native.

3. sACN E1.31 — the newer, cleaner alternative

sACN (streaming ACN, ratified as ESTA E1.31 in 2009) was created by ESTA to standardize what Art-Net had done ad-hoc. Key differences:

  • Multicast first. Each universe maps to a predictable multicast IP (239.255.0.1 for universe 1, etc.), reducing network load.
  • Numeric universe ID 1–63,999 (vs Art-Net's bitfield structure).
  • Priority & merging — supports built-in Highest Takes Precedence (HTP) merging across multiple senders.
  • Backward compat — most devices today support both.

sACN is dominant in theatrical and concert lighting (grandMA3, Hog 4, ETC Eos, Chamsys). If you're interfacing a lighting console with your pixel wall, sACN is almost always the right choice.

4. Side-by-side comparison

FeatureDMX512Art-NetsACN E1.31
TransportRS-485 serialUDP broadcast / unicastUDP multicast
Max universes1 per cable32,768 networked63,999 networked
Max devices32 per busunlimitedunlimited
DiscoverynoneArtPollnone (fixed multicast)
Mergingexternalexternalbuilt-in HTP/LTP
Latency~22ms<5ms<5ms
Best forFixtures <512 chLED pixel installsTheatrical consoles

5. Designing a tour-grade network

A typical modern touring rig looks like this:

  1. Lighting console (grandMA3) outputs ~50 universes over sACN on primary Gigabit NIC.
  2. Signal hits a Luminex GigaCore 16RF managed switch (purpose-built for Ethernet lighting).
  3. Secondary NIC on the console does the same on a redundant switch — automatic failover if primary fails.
  4. From the switch, VLAN-tagged sACN flows to:
    • DMX output nodes (ENTTEC ODE Mk3) that convert sACN → DMX512 for traditional fixtures.
    • LED controllers (Advatek PixLite Mk3, Falcon F48) that convert sACN → WS2811/APA102 for pixel wash.
    • Media server (Resolume Arena) that visualizes everything in real time.
  5. All switches on UPS, all cables locked with Neutrik etherCON.
Common mistake: running sACN multicast on an unmanaged consumer switch. Low-end switches flood multicast across all ports, saturating the network. Always use a managed switch with IGMP snooping enabled.

6. Which protocol should you pick?

  • Standalone moving head, haze machine, or small fixture rig <512 channels? Plain DMX512. One cable, one XLR, done.
  • Permanent pixel-LED installation (hotel façade, mall, retail)? Art-Net. Universal device support, broadcast model is fine on a dedicated LAN.
  • Live concert / touring with a lighting console? sACN. Native console support, multicast scales cleanly, built-in merging.
  • Hybrid show (console + pixel wall)? sACN end-to-end — pixel controllers today all accept it, and you avoid the complication of two protocols.

7. Where to practice this

Our DMX / Art-Net / sACN Pro course drops you into a virtual lab environment with QLC+ and Chamsys MagicQ running against a simulated 50-universe network. By lesson 10 you'll have patched, calibrated, failed-over and recovered an entire touring rig — without ever leaving your laptop.

#protocols #led #pixel-led #koshi-academy