DMX Jargon DecoderEasyStagecraft Course · Tier 1B · Module 1 (Speak Lighting) · v1.0 · "the digital signal protocol that connects the console to the lights, decoded"
The DMX moment. "We've got a DMX issue, give us 30 minutes." When an LD says this, you need to know: this is real, it's fixable, and the LD is asking you to leave them alone for half an hour. After this sheet, you'll know whether to panic, escalate, or go grab a tea. The answer: tea. Always tea. DMX issues are routine; the 30-minute estimate is honest.
The 12 DMX terms a teacher needs
Term
What it actually is
Why a teacher cares
DMX-512
The industry-standard digital signal protocol for controlling theatre lighting. 512 control channels per data stream.
If DMX is broken, no fixture responds. The whole rig is dark until it's fixed.
Universe
One DMX-512 stream of 512 channels. Big rigs use multiple universes.
Each universe is one cable run from the console. Adding a universe is a A$40 hardware item — not a budget-buster.
Address
The number 1-512 a fixture is set to listen on within its universe.
If a fixture is at the wrong address it won't respond. 5-minute fix.
Footprint
The number of consecutive DMX addresses a fixture uses. A simple dimmer = 1 footprint. A moving head = 12-32 footprint.
A 32-footprint fixture takes up 32 of your 512 channels. 16 movers × 32 = 512 — you're already at one universe.
Splitter / Opto-splitter
Hardware that splits one DMX signal into multiple identical outputs. Used to run multiple cable paths from one universe.
~A$20/day hire. Standard, not a luxury item.
Terminator
A small plug at the end of the DMX cable run that absorbs the signal so it doesn't bounce back.
A$2 of hardware. Without it, the rig can act flaky. If a fixture is unresponsive at the end of the cable run, ask "is there a terminator?"
RDM (Remote Device Management)
An extension of DMX that lets the console talk back to fixtures (read status, change addresses, query temperature).
Saves bump-in time — addresses can be set from the console, not by climbing to each fixture. Premium feature.
Refresh rate
How many times per second the DMX signal updates (typically 44Hz).
Almost never an issue. If it comes up, the LD is talking to themselves — leave them to it.
sACN / Art-Net
Network-based protocols that carry many DMX universes over ethernet. Used in big rigs.
Big-show kit. If a school musical quote includes sACN, ask: "do we really need it for a 1-universe rig?"
Channel offset
The relative position within a fixture's footprint (e.g. "the pan channel is offset 1 from the fixture's address").
Programmer-speak. You don't need to engage.
Patch
The map that connects console channels to physical DMX addresses.
Re-patching takes 20-60 min. Don't interrupt during patching.
5-pin XLR / 3-pin XLR
The cable connector types. 5-pin is the DMX standard; 3-pin is audio.
Cheap suppliers sometimes use 3-pin "DMX" cables. Works most of the time but isn't standard-compliant. Worth knowing.
Common DMX problems + what they sound like
"We've lost the universe."
Means: the data stream isn't reaching the rig at all. Likely a cable disconnection, terminator missing, or splitter failure. Fix time: 5-30 minutes. Routine.
"Universe 2 is acting flaky."
Means: signal is intermittent. Likely a marginal cable, a fixture with a poor connector, or daisy-chain too long (DMX has a ~300m limit). Fix time: 10-60 minutes. The LD will work through it methodically.
"Address conflict on fixture 14."
Means: two fixtures are set to the same address. Both will mirror each other. Fix time: 5 minutes (re-address one of them). Routine.
"We need to add a splitter."
Means: the cable path is splitting in two physical directions + needs hardware to split the signal cleanly. A$20/day. Approve.
"We need another universe."
Means: the rig has more than 512 footprint, so a second 512-channel data stream is needed. Hardware: an extra DMX output from the console (most consoles have multiple) + a new cable run. Negligible cost if planned; A$40-60 if bought in last-minute. Question: "why wasn't this in the original spec? Did the fixture count grow?"
"RDM scan picked up an unknown fixture."
Means: the system found a fixture that isn't in the patch. Could be a leftover device or a manually-addressed unit. Fix time: 1 minute. Programmer-speak.
The phrases that pay off
Three things you can say in a DMX conversation that signal you've done the homework:
"How many footprint does each moving head use? I want to make sure we've got enough universe space."
"Is the terminator in at the end of the cable run?" (Solves ~30% of intermittent DMX faults.)
"Is universe 2 daisy-chained or split? If daisy-chained, how long?" (DMX runs longer than 300m act flaky.)
You don't need to fix DMX. You need to understand what's broken when the LD describes it, and not panic. After this sheet, you do.
What NOT to do during a DMX problem
Don't touch the console. The LD is trying to isolate the fault; you'll add a variable.
Don't ask "how long?" every 5 minutes. The LD's estimate stands until they revise it.
Don't escalate to the supplier on the phone unless the LD asks you to. They'll diagnose first.
Don't tell the cast "it'll be fine, we'll start in 10". You don't know. The LD does.
What to do
Do call a 30-minute break for the cast (note: their union/school rules may have specific break-call wording).
Do ask the SM to update the call sheet if the delay extends.
Do use the time to grab a coffee + check the run sheet for downstream impact.
Do ask the LD when they're done: "what was it?" — for the next time it happens.