Looking at Chataigne? Here is what CueSync does
CueSync speaks to each console, media server and show-control program in that system's own protocol, and gives you a cue engine, pads and a timeline to fire them from, without writing code. This page is about CueSync only.
What CueSync does
For the job: a show-control layer with the integrations built in.
One cue, the whole rig
One cue can hold a console command, a media-server command, a MIDI message and an audio clip, so a single press fires the whole moment. CueSync ships 15 output protocols — grandMA2 (Telnet), grandMA3 (TCP and UDP OSC), Avolites Titan, ETC Eos, ChamSys MagicQ, Resolume, disguise, VIOSO, Pixera, TouchDesigner, Unreal Engine 5, QLab (TCP and UDP), MIDI Show Control, Pangolin Beyond and Custom OSC — of which grandMA3, QLab, Resolume and Unreal Engine 5 (in-engine, on our own project) have been run against the real program or console, and the rest are built to each maker's published interface and have not yet been run against that equipment, so fire your cues on your own rig before a show.
Editions: Every edition
Any button can be GO
An incoming MIDI note can fire the next cue in your stack. In Theatre and Production an OSC message can too, and a MIDI GO note can call a Theatre show, so a button box, a controller or another program can be your GO. OSC input ships switched off: set a listening port first.
Editions: Every edition (OSC input: Theatre · Production)
Reaching what has no integration
Custom OSC sends the OSC messages you define to anything on the network that listens to OSC, and MIDI goes out through the system MIDI devices you pick, so a device CueSync has no named integration for can still be fired from a cue.
Editions: Every edition
The beat from the decks
CueSync joins your PRO DJ LINK network as another player and reads the position, BPM, phase and tempo master your CDJs already share, so the tempo comes from the decks, with no DJ software in the chain. If the beats go quiet while a deck is playing, it says so instead of firing nothing. Of the Pioneer units, only the CDJ-3000 has been through a hardware session.
Editions: DJ · Production
Cues that wait for the music
A cue can wait for a phrase change, an energy band, a fill or the DJ's hot cue press, and fire when the track gets there. Cues are checked in order, so the cue you expect next goes at the top of the stack. On your own files these cues use CueSync's analysis; on a Pioneer deck, phrase cues read the phrase map rekordbox wrote to the stick, which has not yet been checked on a CDJ-3000.
Editions: DJ · Production
Calling the show
Run Mode shows the cue you are calling, its countdown, the running order behind it and timecode health on one operator screen. Each cue fires on timecode, on GO, as a Follow or as an Autocontinue, and DRY steps the running order through with nothing sent to the desk, the media server or the rig, CueSync's own timecode outputs included.
Editions: Theatre · Production
An output that drops is named
When an output stops answering, CueSync keeps trying to reconnect, and once repeated attempts fail it raises an alert and marks the pads that use it. Before doors, Pre-Show Check names each output your cues target that will not answer, with the number of cues routed to it; on an output that sends without an answer, a pass means the command was sent.
Editions: Every edition
Before you decide
What you need
- A Mac with Apple Silicon and macOS 12 or later. CueSync does not run on an Intel Mac, and there is no Windows build.
- Every edition connects to every output. The editions differ in workflow: DJ for the decks and Auto Pilot, Theatre for the Show Editor and Run Mode, Production for both.
- Something programmed for CueSync to trigger: a console, a media server or show-control software. CueSync drives the desk, and the desk owns the rig.
- An account. Without a subscription you can run the demo show and tour the app in read-only mode. Building and saving your own shows, and connecting real outputs, need a subscription.
When CueSync is not the right fit
- You need a scripting environment that routes any protocol to any other. CueSync has no scripting: it speaks the outputs it ships, with Custom OSC for anything else that listens to OSC.
- You need it on Windows or on an Intel Mac. There is no Windows build, and CueSync does not run on an Intel Mac.
- You need software whose source you can read and change. CueSync is a commercial application, and its source is not published.
Common Questions
Have more questions? Contact us
Last reviewed . This page describes CueSync only and makes no claim about any other product. If anything here about CueSync is out of date, tell us at contact@cuesync.live and we will correct it.
Competitor product names and marks on this page are the property of their respective owners and are used only to identify their products. CueSync is not affiliated with or endorsed by them. This page is the opinion of its author as of October 2026, based on CueSync's own documentation.
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.