CueSync drives Titan through its own WebAPI in real time — fire playbacks and cues, ride faders, and run macros, all locked to the beat. No OSC middleware, because Titan does not speak OSC.
CueSync talks to Titan's own WebAPI on port 4430 — the interface Avolites actually ships. No OSC bridge, no middleware box between the music and the desk.
Playback & Cue Triggering
Fire and release playbacks, step cues forward or back, and jump to a specific cue number on beat drops, energy changes, or BPM thresholds.
Fader & Intensity Levels
Map audio energy to Titan playback levels, individual fixture intensity, or the grand master for live, music-reactive intensity.
Beat-Phase Locking
Cues fire on the exact downbeat — CueSync locks to beat phase, not just BPM.
Playbacks by Name
CueSync caches the console's handle list, so you can target a playback by its name instead of hunting for a numeric TitanId.
Mission Control (Theatre/Production)
Monitor the Titan connection, active cues, and outputs from one HUD.
Quick Setup
1Confirm the Titan WebAPI is reachable on the console — it listens on port 4430 by default.
2Add an Avolites Titan output in CueSync pointing at the console's IP address.
3Map CueSync triggers to Titan playbacks, cues, and fader levels in the routing editor.
4Check the wiring before you subscribe: configuration is unrestricted without a licence, and Test Connection runs the same liveness probe the live connection uses, so it confirms the device is reachable and answering with real latency. Firing cues is what a licence enables — an unlicensed install never sends one, so the cue path itself is verified after you subscribe, not before.
Avolites Sapphire TouchQuartzTiger Touch IIDiamond 9Titan MobileTitan GoTitan PC Suite
Engineering facts
Specifics that hold up in production
The load-bearing claims behind CueSync's Avolites Titan integration. Numbers, named subsystems, test references — the things you can verify before the show.
Cue evaluation on a sub-5 ms budget
CueSync evaluates beat events from Pioneer PRO DJ LINK on a sub-5 millisecond budget on the cue-evaluation path, and reports the budget-violation rate on screen. The CueSync portion of the chain is engineered to a strict sub-5-millisecond budget and continuously regression-tested; the network send budget is under 2 milliseconds.
15 output protocols, one application
CueSync ships 15 output protocols from a single desktop application: GrandMA2 (Telnet and OSC), GrandMA3 (TCP OSC and UDP OSC), Avolites Titan (WebAPI), ETC Eos, ChamSys MagicQ, Resolume, disguise (d3), VIOSO Player/Show, AV Stumpfl Pixera, TouchDesigner, Unreal Engine 5, QLab (TCP and UDP), MIDI Show Control, Pangolin Beyond, and Custom OSC. Every CueSync edition includes every protocol.
Avolites Titan Questions
Any Titan console or the Titan PC Suite / Titan Go that exposes the Titan WebAPI — from Tiger Touch and Quartz up to Diamond.
No — it's an automation layer. CueSync can run smaller rigs end-to-end or fire automated playbacks while an operator busks and overrides.
No, and nothing does — Titan has no native OSC surface. CueSync uses Titan's own WebAPI (HTTP on port 4430) instead, which is why no OSC setup is needed on the console. Anything claiming OSC control of Titan is going through a translation layer you would have to install and maintain yourself.
Playback fire and release, playback levels, cue step forward/back and jump-to-cue, fixture intensity, macro execution, grand master level, and blackout — mapped from CueSync's beat, phrase, energy, and BPM triggers.
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.