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 TeamShow Control 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. CueSync gives that operator tools: tap the tempo so beat-driven cues follow the band's pulse, follow an Ableton Link session if the band's tempo source speaks Link, and call the cues that must be called by hand from a hotkey, a pad or a MIDI note.
Structural analysis of a known track. Read tempo, beat phase and section boundaries from a Pioneer deck over PRO DJ LINK (with the phrase analysis from the rekordbox USB), or from a file played in Local Audio, then fire on those events. No click, no timeline, nothing asked of the DJ.
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
A beat followed live is reactive. It knows a drop happened; it cannot know one is coming. A track analysed ahead of time is the exception: its drops are on the grid before they play.
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 — a track analysed ahead of time, in rekordbox or in Local Audio, where AutoPilot can land a cue on the drop itself — or an operator who knows the show. Trying to make a live beat anticipate is the most common way these systems disappoint.
What This Looks Like in Practice
The architecture that works on a theatre show or a DJ night 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 DJ's set, a vamp that runs until an actor is in place — these have no timeline, and a cue stack cannot describe them. Beat-driven cues follow the deck, the file or the tapped tempo instead.
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 music-driven automation in one workflow, rather than two applications negotiating over a rig. Triggers available include beat, phrase, energy, timecode, MIDI, OSC, hotkey and manual, 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. Take the beat source away: pull the PRO DJ LINK cable or stop tapping. 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.
What Stays With People
Automation makes a rig punctual: every cue lands with the music. The looks are still designed, the score is still 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 put a click in anyone's ears so that the lights can keep up: the beat comes from a deck, a file or a tap.
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, or the live performance itself: four architectures, how to choose, and where a hardware generator fits.
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 follows the music's beat and structure, from analysed tracks or live deck data. How it works.
Read