DMX512 interface guide (2026): Art-Net vs sACN vs USB, what to buy and which software to run

Discuss the Implementation and Development of DMX512 Lighting
Post Reply
User avatar
ZerOne
Site Admin
Posts: 216
Joined: Sun Dec 13, 2020 8:21 am

A buying and planning guide for hobbyists and installers wiring up DMX lighting (stage and party lights, architectural LED, pixel strips) to a home or small-venue setup. Based on the QLC+ and WLED documentation and general DMX practice, as at October 2026. I have not tested every product type described. The DMX-512 Protocol Overview thread covers the protocol, and the Lixada USB-DMX dongle thread covers one cheap USB interface. This one helps you choose between the options.

DMX512 in brief
  • A universe is 512 channels, each 0 to 255, sent over RS-485 at 250 kbit/s in one direction (from controller to fixtures).
  • Wired DMX is a daisy chain of fixtures, with a terminator (typically 120 ohm) at the last fixture. Use proper DMX or RS-485 data cable rather than ordinary microphone cable, particularly on long runs. 3-pin XLR is common on budget gear, 5-pin is the formal standard connector.
  • A DMX line is limited in how many devices it can drive (32 unit loads in the standard), so use a splitter or an opto-isolated booster for more or for long runs.
  • Many pixel and LED controllers instead take network protocols directly over Ethernet or Wi-Fi, which skips wired DMX altogether.
The three ways to get DMX out of a computer
  • USB to DMX interface: a dongle with an XLR output, from cheap clones up to professional interfaces. Simple, good for one universe, and QLC+ has plugins for many of them. Quality varies a lot. Cheap units may lack isolation and have unreliable timing, so keep expectations modest for anything you rely on at a gig.
  • Art-Net: DMX over UDP (port 6454). Often used with Ethernet-to-DMX nodes. Art-Net universes start at 0. By default QLC+ broadcasts Art-Net on the selected interface, which is fine on a hub or a small network but wasteful on a switch. QLC+ documents unicast as better practice on switches.
  • sACN (E1.31): DMX over UDP (port 5568) that is a formal standard, and by default uses multicast addresses of the form 239.255.0.x in QLC+, with priorities (the QLC+ docs mention a priority range of 0 to 200, default 100). Many network nodes and pixel controllers support it.
Which for what? For a handful of wired fixtures in one room, a USB interface is fine. For anything with several universes, long distances or pixel controllers, a network protocol and a switch beats cabling. sACN and Art-Net are both widely supported, so choose whichever your nodes handle well. Some nodes support both.

Network hygiene
  • Put lighting on its own switch or VLAN. Multicast and broadcast traffic from lighting can affect other devices, and these protocols have no authentication, so anyone on the network can send DMX.
  • If sACN multicast floods the network, a managed switch with IGMP snooping is the usual fix (check your switch's documentation).
  • Use wired Ethernet for anything timing-critical, and avoid Wi-Fi for a main show rig.
  • Never set the Art-Net output address in QLC+ to the sending computer's own IP. The docs warn that it can cause a loop. Use the loopback address (127.0.0.1) for software on the same machine.
Software
  • QLC+: free and cross-platform lighting control. The site lists version 5.3.0 as I write (4.14.4 is also listed). It supports Art-Net, E1.31 and a range of USB interfaces through plugins. Good for scenes, chasers and a virtual console.
  • Open Lighting Architecture (OLA): a framework for routing DMX between interfaces and protocols. Its repository shows a last tagged release of 0.10.9 from February 2023, so check how current it is for your needs. QLC+ has an OLA plugin.
  • WLED: firmware for ESP8266 and ESP32 LED controllers. It accepts sACN, Art-Net and DDP, and can also output wired DMX with a MAX485 transceiver and a special build. See the project post in this forum.
  • LedFx: music-reactive LED effects that work with WLED.
Buying checklist
  • How many universes now, and in a year? One USB dongle is one universe. Network nodes often have several ports.
  • Does it do the protocol you need in both directions (input and output)?
  • Is it supported by your software? Check the QLC+ plugin pages before buying.
  • Opto-isolation for the DMX side, a decent connector, and robust firmware updates.
  • Power: DMX carries data only. Fixtures and LED supplies need their own power, and mains work must be done by a licensed electrician in Australia.
Links
Question for the group: what are you driving with DMX at the moment (stage lights, pixel strips, architectural), and have you found USB dongles, Art-Net nodes or sACN the most reliable?
Top
Post Reply

Return to “DMX512 Protocol Discussion”