CueSync drives Titan through its own WebAPI in real time — fire playbacks and cues, ride faders, and run macros on the same cue as video and sound. No OSC middleware, because Titan does not speak OSC.
CueSync's Network screen on its Outputs tab: a header reading In 2/3 and Out 5/6 beside a preset picker, and the Output Status panel laying six outputs out in two columns — ETC Eos (LX2), grandMA3 (FOH), QLab 5 (SFX), Resolume Arena, TouchDesigner and Unreal Engine, each with its address — five connected for 21 minutes and TouchDesigner refused with 'Connection refused — retrying in 4s' and a Retry control, under the count '5 of 6 connected'.
Avolites Titan · spec sheet
Speaks
HTTP (Titan WebAPI)
Built for
Avolites Sapphire Touch · Quartz · Tiger Touch II · Diamond 9 · Titan Mobile · Titan Go · Titan PC SuiteDrives Avolites' Titan WebAPI, on a Titan console or on Titan PC Suite.
The output is in every edition. A capability marked with an edition needs that edition.
What CueSync sends to Avolites Titan
What CueSync sends to Avolites Titan
Native Titan WebAPI Control
CueSync talks to Titan's own WebAPI. 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
Set Titan playback levels, fixture intensity or the grand master from beat, phrase and energy triggers for music-reactive intensity.
Beat-Phase Locking
Cues fire on the exact downbeat — CueSync locks to beat phase, not just BPM.
Playbacks by Name
CueSync reads the console's playback list, so you can target a playback by its name instead of hunting for a numeric TitanId.
Companion monitor (every edition)
Watch the Titan connection status and timecode from any iPad on the venue Wi-Fi.
Set it up
Avolites Titan with CueSync, in 4 steps.
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 a cue's actions.
4Press 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.
What CueSync's Avolites Titan integration does and how it behaves — the things you can check before the show.
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.
17 output protocols, one application
CueSync ships 17 output protocols from a single desktop application: grandMA2 (Telnet), grandMA3 (TCP OSC and UDP OSC), Avolites Titan (WebAPI), ETC Eos, ChamSys MagicQ, Art-Net, sACN, Resolume, disguise (d3), VIOSO Player/Show, AV Stumpfl Pixera, TouchDesigner, Unreal Engine 5, QLab 5, 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 — Titan has no native OSC surface. CueSync uses Titan's own WebAPI instead, so no OSC setup is needed on the console.
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.