How to Trigger Lighting Cues Without a Click Track
A click track buys the lighting op a clock and costs the band their timing. What to do when the show is played rather than played back.
CueSync TeamStage Automation Engineers
The Question Behind the Question
"How do I trigger lighting cues without a click track" is usually asked after someone has already been told the answer is a click track, and has discovered what that costs.
A click locks the band to a grid. It changes phrasing. It removes the tempo drift that makes live performance feel alive. In a lot of rooms the musical director will simply say no, and they are right to — the click is being proposed so that another department can have a clock. That is a strange thing to ask musicians to absorb.
So the real question is: what can a lighting system follow, if not a click?
Three Things That Are Not a Click
An operator. Still the default, still excellent, and worth stating plainly because the alternatives get discussed as though the human option were embarrassing. A good operator following a score is more musically sensitive than any automation. What they cannot be is identical on the fiftieth cue of a two-hour show at the end of a six-week run.
Structural analysis of the live audio. Derive tempo, beat phase, and section boundaries from what the room is actually hearing, then fire on those events. No click, no timeline, nothing asked of the band.
Chasing a player that reports position. If any part of the show comes from a device that knows where it is — a CDJ over PRO DJ LINK, a playback rig emitting MTC — that position can drive cues directly. This is the strongest option when it applies, and it applies less often than people hope.
The Limit That Decides Your Architecture
Analysis is reactive. It knows a drop happened; it cannot know one is coming.
This is a property of causality, not of any particular implementation, and it is the single most useful thing to internalise before designing the show. It splits cues into two kinds:
| Cue type | Example | Works reactively? |
|---|---|---|
| Reaction | A hit on the downbeat, a state change at a section boundary | Yes |
| Anticipation | A slow build that must be fully up on the first frame of the chorus | No — needs the structure known in advance |
A reactive cue tolerates the small latency between event and action. An anticipatory one does not, because "on time" means before the audible event.
The workable pattern is to let automation own the reactions and give anticipatory moments either advance structure — known material analysed ahead of time — or an operator who knows the show. Trying to make analysis anticipate is the most common way these systems disappoint.
What This Looks Like in Practice
The honest architecture on a live-band or theatre show is a hybrid, with the seam drawn deliberately:
Scripted where the show is scripted. Anything that happens in the same order every night belongs in a cue stack. It does not need analysis; it needs a reliable GO.
Reactive where the show is not. Improvised passages, a band vamping until an actor is in place, an encore that may or may not happen — these have no timeline, and a cue stack cannot describe them.
A visible, deliberate handover. The failure mode is not either mode individually; it is ambiguity about which one is in charge. The operator should be able to see which mode is live and force the other at any time.
CueSync's Production edition exists for exactly this shape — cue stacks and audio-reactive automation in one workflow, rather than two applications negotiating over a rig. Triggers available include beat, phrase, energy, timecode, MIDI, OSC, manual and scheduled, which means the seam is a routing decision rather than an architectural rewrite.
Rehearsal Is Where This Is Decided
Three things are worth doing before the room fills, and all three are cheap:
Mark the rubato. Walk the score and flag every passage where the pulse genuinely stops being periodic. Those are operator territory. Beat tracking through a real rallentando will run ahead of the music, and finding that out in performance is avoidable.
Test the failure, not the success. Mute the input. Decide whether the rig holds its last state or releases, make sure the operator can see which happened, and have them practise the recovery once.
Fire the whole show once with nobody watching the screen. If automation only works when someone is monitoring it, it is not automation — it is a second operator with worse judgement.
The Honest Boundary
None of this makes a lighting rig musical. It makes a rig punctual, which is a different and smaller claim. The looks still have to be designed, the score still has to be understood, and the decisions that make a show feel considered are still made by people.
What it removes is the tax of manual repetition — and, specifically, the need to ask a band to play to a click so that the lights can keep up.
Further Reading
- Where Should Your Show's Timecode Come From? — the four architectures, including the no-timeline case
- Audio-Reactive Cues Over OSC — the QLab implementation
- What Is Music-Driven Lighting Automation? — the category from the top
- CueSync for Theatre Operators — cue stacks, Show Editor, Run Mode
Frequently Asked Questions
Because the cost lands on the musicians, not on the lighting department. A click locks the band to a grid, changes how they phrase, and forecloses the tempo drift that makes live performance feel live — and in most theatre and live-band contexts the musical director will refuse, correctly. A click is the right answer when the show is already playback-driven or when the band has agreed to it. It is the wrong answer when it is being imposed solely so that another department can have a clock.
Keep Reading
Where Should Your Show's Timecode Come From?
Reaper, QLab, the console's internal clock, a hardware generator, or the live performance itself. Four architectures, and how to pick between them.
ReadAudio-Reactive Cues Over OSC: What QLab Can and Cannot Do
Reacting to live audio usually gets built from QLab network cues, OSC queries and patience. What that does, where it stops, and what analysis adds.
ReadWhat Is Music-Driven Lighting Automation? A Definition
Music-driven lighting automation is lighting control that reacts to live audio through beat, transient, and FFT analysis. Here's how it works.
Read