Integration · Playback · QLab
QLab, on cue.
CueSync fires QLab over OSC — GO a cue by number, start or stop it, move the playhead, change its level, rate, opacity, pre-wait and duration — and in Theatre and Production sends the whole cue list into QLab, so sound and video land on the same cue as the lights.
QLab spec sheet
Screen capture · v1.0.35 · Outputs
| Speaks | OSC · MIDI Show Control |
|---|---|
| Built for | QLab 5 (TCP and UDP)Run against QLab 5.6.3 over TCP and UDP. |
| Editions | In DJTheatreProduction |
| Manual | /docs/connect/network-outputs |
The output is in every edition. A capability marked with an edition needs that edition.
What CueSync sends to QLab
| Native QLab OSC | QLab's OSC dictionary is built in. CueSync targets /cue/.../start, workspace transport, and panic without plugins. |
|---|---|
| Cue Start / Stop / Panic | Start numbered cues, stop or pause playback, or fire a panic on energy changes and phrase transitions. |
| Beat- & Phrase-Accurate | Cues land on the downbeat or at phrase boundaries — CueSync locks to musical structure, not a stopwatch. |
| MSC for Theatre | MIDI Show Control (GO, STOP, RESUME and a cue by number) for rigs that standardise on MSC instead of OSC. |
| Per-Show Profiles | Save QLab workspace routing per production and recall it instantly. |
| Live Connection Status | QLab connection state and health are always visible, and a failed send CueSync can detect raises an operator notification. |
Set it up
QLab with CueSync, in 5 steps.
- 1In QLab, enable OSC controls (Workspace Settings → OSC) and note the listening port; for MSC, enable the MIDI/MSC patch.
- 2Add a QLab output in CueSync pointing at the Mac running QLab and its OSC port.
- 3Map CueSync triggers to QLab cue numbers, transport, or MSC commands in a cue's actions.
- 4Watch messages stream through CueSync's OSC/MIDI monitor as you map them.
- 5Press Test Connection to confirm the device is on the network and answering — it works before you subscribe, so you can check the wiring first. With a subscription, fire a cue and watch it land.
Integration details
Specifics that hold up in production
What CueSync's QLab integration does and how it behaves — the things you can check before the show.
- QLab — TCP/UDP port 53000
- Cue control is
/cue/<number>/go,/cue/<number>/startand/cue/<number>/stop; transport is the bare/go,/stop,/pause,/resume. Default port 53000. - Beat-aligned timing
- CueSync times cues to the beat phase of the music and is designed for live production. What you see and hear end to end also depends on your network, console or media server, and fixtures, so confirm the whole chain on your own rig before a show.
- MIDI Show Control for theatre
- In every edition CueSync emits MIDI Show Control (GO, STOP, RESUME, a cue by number) alongside OSC, so it slots into the standard theatre cue-light and playback workflows that QLab already anchors.
QLab questions
- No. QLab exposes OSC and MIDI Show Control natively; CueSync speaks both directly.
- Yes — CueSync locks to beat phase and phrase boundaries, so a GO lands on the downbeat rather than whenever a key was pressed.
- Both. A DJ set fires QLab from the music on PRO DJ LINK; a theatre show fires it from the cue list, on timecode or GO, over OSC or MIDI Show Control.
Different question? Ask us directly.
See also
CueSync for Theatre OperatorsTimecode Calculator (free tool)MIDI Show Control IntegrationTimecode IntegrationLooking at QLab?Audio-Reactive Cues Over OSC: What QLab Can and Cannot DoWhere Should Your Show's Timecode Come From?MIDI Show Control: Still the Most Reliable Cue TriggerQLab or grandMA3: Which One Should Be Master?
Ready to Automate Your Stage?
Download CueSync free and run the built-in demo show — press Space and its cues fire against simulated outputs, no hardware required. Subscribe when you're ready to drive a real rig.
QLab® is a trademark of Figure 53, LLC. CueSync is an independent product and is not affiliated with or endorsed by Figure 53.