CueSync vs Clockworks
Both sit between the DJ booth and the rig, and they are not the same kind of tool. Clockworks tells your rig where you are in the track. CueSync decides what should happen there. If your consoles are already programmed against timecode, Clockworks may be all you need — and it reaches DJ software CueSync does not.
Feature-by-Feature Comparison
CueSync
- 1.0Connect
- 2.0Cue
- 3.0Fire
- 4.0Coordinate
- 5.0Recover
Clockworks
- 1.0Connect
- 2.0Cue
- 3.0Fire
- 4.0Coordinate
- 5.0Recover
Why Teams Choose CueSync
Position vs Decision
Clockworks answers "where are we in the track?" with frame accuracy and hands that to your rig. CueSync answers "what should happen now?" — it evaluates phrase boundaries, energy thresholds, hot cues and key changes against a cue stack you authored, then fires. If your console is already programmed against timecode, you may only need the first answer.
Console-Native, Not Just OSC
CueSync speaks GrandMA2 Telnet, GrandMA3 TCP and UDP OSC, Avolites Titan, ETC Eos and ChamSys MagicQ in their own command vocabularies — it can run a macro or take an executor, not only stamp a timecode frame the console has to be pre-programmed against.
No DJ Software Required
CueSync analyses whatever is audible — a vinyl set, a band, a playback rig, a microphone — because the analysis is live rather than read from a DJ app's beat grid. Clockworks needs a supported source: Serato, Traktor, VirtualDJ, PRO DJ LINK or StagelinQ.
Where Clockworks Wins
Serato, Traktor and VirtualDJ integration, Denon StagelinQ, NDI output, up to twelve decks, an iPad viewer, and a team offering SLAs and on-site touring support. CueSync has none of those. If you run Serato or Denon gear, or you need NDI, Clockworks does something CueSync currently cannot.
Common Questions
Have more questions? Contact us
Ready to Automate Your Stage?
Download CueSync free and explore the full interface in read-only mode. Subscribe when you're ready to go live.