Fire a lighting console from the music
Send GO to grandMA3, MagicQ, ONYX, Titan, grandMA2 or any MSC console when the music does something. Templates fill in the addresses.
The pattern is always the same: Device → Trigger → console output. The trigger decides when, and the output sends the command.
Pick the moment#
Some useful triggers on a deck's data:
| Moment | Trigger |
|---|---|
| A new track loads | metadata.title On Change |
| A new phrase starts | phrase.current On Change |
| The drop hits | struct.current Equals Drop |
| Every downbeat | beat.beatInBar Equals 1 |
| The deck goes on air | playback.onAir State On |
Give the trigger a Release Delay of at least 60 ms so every output sees the press.
grandMA3 or Resolume (OSC)#
- Right-click the trigger → Add Output → OSC.
- Load Template… → grandMA3 → Exec Button. This fills in the address (
/Page1/Button201) and argument. For Resolume, pick Resolume Arena, which uses port 7000. - Set the host to the console's IP address. Templates start at
127.0.0.1. - Change the page and executor numbers in the address.
The Exec Button template follows the trigger's press and release, like a real key.
Consoles with their own node#
Add Output → Lighting also has dedicated nodes: MagicQ, ONYX, Titan, grandMA2 and ProPresenter. They show the console's own lists (cuelists, handles, timers) in a Pick … popup. They report back on a State pin, and the node face turns orange when a command fails.
Level actions on these nodes can Follow Value, for example a DJM channel fader riding a playback.
MIDI Show Control#
For dot2, grandMA2 (MSC) and Chroma-Q Vista, use the MSC output: Load Template → the console → GO. Set Cue to metadata.trackNumber to fire one cue per track.
Test without music#
Press ▶ on the trigger or the output node to fire it by hand. The node face shows the last command sent.