Skip to main content
Lighting production guidePlanning guide

The part everyone skips

DMX lighting explained, without the jargon

One DMX512 data link carries a start code followed by as many as 512 data slots. A fixture mode defines what its slots mean and how many it consumes; its start address defines the first slot it reads. Shared addresses can be intentional when compatible fixtures should mirror one another, while accidental range overlap gives unrelated parameters the same control data. The cure is documented range arithmetic and a traced signal path.

DMX for beginnerswhat is DMXDMX addressingDMX channels explainedDMX universe

Planning and browser practice are references, not show approval. Verify fixture manuals, circuit ratings, hanging limits, venue rules, and local code with a qualified person.

01 · Read the brief

Start with the brief and the system.

What triggered this guide

You changed one fader and a completely different light changed color.

The decision to make

Understand what a DMX address is, why fixtures fight each other, and how to patch a rig without overlaps.

02 · Use the method

Brief it, change one variable, prove the result.

Design method

Write one observable job and the audience, camera, subject, or document that will prove it. Confirm the authorized system limits. Change one controllable variable, compare it with the prior state from the position that matters, then record both the result and the handoff.

Safety boundary

A browser page or calculator cannot authorize electrical, structural, rigging, access, fire, laser, atmospheric-effect, or work-at-height decisions. Stop and use fixture documentation, venue procedure, local requirements, and the qualified person responsible for the actual system.

03 · Work the order

Work from evidence to handoff.

  1. 1

    Read the fixture manual and record the exact mode, footprint, connector, addressing method, and any manufacturer-specific behavior before assigning a number.

    Proof before the next move: The mode displayed on the fixture matches the mode selected in the console profile and paperwork.

  2. 2

    For each fixture, calculate its occupied range as start address through start plus footprint minus one.

    Proof before the next move: The written first and last slots agree with the console patch and remain inside slots 1 through 512.

  3. 3

    Mark deliberate shared control separately from accidental overlap. Share only when compatible devices are meant to receive the same slot data.

    Proof before the next move: Every overlap has an explicit purpose; every independent parameter owns an unambiguous slot.

  4. 4

    Assign the ranges, then document universe, fixture identity, mode, start, end, physical location, and next available contiguous range.

    Proof before the next move: A second operator can trace the patch without opening the show file or guessing from labels.

  5. 5

    Trace controller, output or network node, distribution, cable path, termination where required, and device in order before blaming the fixture.

    Proof before the next move: A low-risk test changes only the intended parameter on the intended device, and the observed path matches the paperwork.

  6. 6

    Move to another universe or revise the mode when the next complete footprint cannot fit; do not split one fixture footprint across the end of a DMX data link.

    Proof before the next move: Every fixture range is contiguous within one universe and the output-to-universe mapping is labeled.

04 · Choose a rep

Practise the exact decision.

Free reps open immediately. Protected reps open the exact practice request and may require sign-in, remaining free practice, or the required belt.

Practise what you just read

Calculate the plan, then prove it locally.

Use documented values to create a planning reference. The actual system still requires fixture documentation, venue limits, qualified review, and local approval.

The free stage and calculator need no signup. Protected practice may ask you to sign in; saving remains optional.

05 · Resolve the edges

Questions

What happens if two fixtures share an address?

They receive the same slot values. That can be intentional for compatible fixtures meant to mirror one another. It becomes a fault when independent or differently mapped parameters share slots, so compare both fixture modes and the complete occupied ranges before changing hardware.

What is a fixture mode and why does it matter?

The mode defines the parameter map and footprint. A larger mode may add finer movement or more emitters, but the exact tradeoff is fixture-specific. The fixture display, console profile, and paperwork must name the same manufacturer mode or the slots will be interpreted differently.

Do I need a second universe?

Use another universe when the required complete footprints cannot fit in the available contiguous slots or when the system design needs separate distribution. Verify the controller, node, transport, output, and paperwork all map that universe to the same physical data link.

Stay in Lighting

Open the school