How to Trigger DMX Lighting with MIDI Cues

Synchronizing lighting with audio or multimedia playback is essential for live concerts, theatrical productions, and automated installations. Lighting designers achieve this precision by using Musical Instrument Digital Interface (MIDI) signals generated from a digital audio workstation (DAW) or show control software to trigger specific DMX512 scenes, chases, and cue lists. By mapping standard MIDI commands or timecode to a lighting console, cues execute automatically at the exact millisecond required, eliminating human error during complex performances.

Understanding the Signal Chain

To link MIDI playback to physical DMX fixtures, a continuous signal pipeline must be established across hardware and software components:

1. Source/Host (DAW or Show Controller): Programs such as Ableton Live, Pro Tools, or QLab output MIDI data alongside audio tracks.
2. Interface/Transport: The MIDI data travels via traditional 5-pin DIN cables, USB-MIDI, or network protocols like RTP-MIDI (AppleMIDI) over Ethernet.
3. Lighting Controller/Console: Software (e.g., GrandMA, ChamSys, Obsidian ONYX, or DMX software like SoundSwitch) receives the MIDI signal.
4. DMX Output: The lighting controller converts internal cue activations into DMX512 packets sent via 5-pin XLR cables or Art-Net/sACN over Ethernet to the fixtures.

Common MIDI Trigger Methods

Lighting designers rely on three primary forms of MIDI data depending on the level of precision required:

1. MIDI Notes and Control Change (CC)

This is the most common and accessible method.

• Note On/Note Off: A specific musical note (such as C3, velocity 127) functions as a digital momentary switch to fire a lighting cue, bump a fixture's dimmer, or advance a cue list.
• Control Change (CC): Continuous controller values (ranging from 0 to 127) are mapped to variable parameters like master faders, strobe speeds, or haze levels.

2. MIDI Show Control (MSC)

Designed specifically for entertainment automation, MSC sends standardized command strings (such as GO, STOP, or RESUME) followed by specific cue list and cue numbers (e.g., Cue 12.5). This allows direct targeting of cues without manual note-by-note mapping.

3. MIDI Timecode (MTC)

Instead of individual trigger events, MTC broadcasts a continuous clock (hours, minutes, seconds, frames). Lighting consoles listen to this incoming timecode and execute pre-programmed cues locked to specific timestamps on a visual timeline.

Implementation Workflow

1. Establish the Connection: Connect the playback computer to the lighting console using a direct MIDI cable or a local network running an RTP-MIDI session. Verify that both systems share the same MIDI channel (channels 1–16).
2. Assign MIDI Commands in the DAW: In the audio software, create a dedicated MIDI track. Draw short MIDI notes or insert MSC commands at the exact points in the timeline where lighting shifts must occur.
3. Map the Console (MIDI Learn): Open the lighting console’s input settings. Put the console into "Learn" mode, select the target cue or fader, and play the corresponding MIDI event from the DAW. The console records the incoming Note, CC, or MSC string.
4. Test and Calibrate Latency: Run the track alongside the lighting system. If network overhead or processing creates a noticeable delay, adjust the track's playback offset (MIDI latency compensation) in the DAW to align the visual output with the audio transients.