Integration
ETC Eos, Driven by the Music
CueSync sends OSC to your Eos console in real time — fire cues, Go/Back through cue lists, set channel and submaster levels, and launch macros, all locked to the beat.
OSC
What CueSync Enables
Native Eos OSC
Eos speaks OSC out of the box. CueSync targets the standard /eos/ command surface — no plugins or middleware on the console.
Cue & Go/Back Automation
Fire specific cues, or run Go and Back through a cue list on beat drops, energy changes, or BPM thresholds.
Channel & Submaster Levels
Map audio energy and frequency bands to Eos channels and submasters for live, music-reactive intensity.
Beat-Phase Locking
CueSync locks to beat phase, not just BPM — cues land on the exact downbeat every time.
Per-Venue Profiles
Save Eos routing per venue and recall it instantly between shows.
Mission Control (Theatre/Production)
Monitor the Eos connection, active cues, and every output from a single HUD.
Quick Setup
- 1Enable OSC RX/TX on the Eos console (Setup → System → Show Control → OSC) and note its IP and port.
- 2Add an Eos OSC output in CueSync's protocol settings pointing at that IP and port.
- 3Map audio triggers to Eos cues, Go/Back, channels, or submasters in CueSync's routing editor.
- 4Validate the wiring with CueSync in read-only mode — full configuration is available without a subscription.
Compatible Hardware
ETC Eos TiGioGio @5Ion XeElement 2ETCnomadNomad Puck
Engineering facts
Specifics that hold up in production
The load-bearing claims behind CueSync's ETC Eos integration. Numbers, named subsystems, test references — the things you can verify before the show.
Beat events processed in under 5 ms
CueSync processes beat events from Pioneer PRO DJ LINK in under 5 milliseconds on the cue-evaluation path. End-to-end beat-to-fixture latency depends on the operator's protocol chain and venue network; the CueSync portion of that chain is engineered to a strict sub-5-millisecond budget and continuously regression-tested. The OSC send budget is under 2 milliseconds.
13 output protocols, one application
CueSync ships 13 output protocols from a single desktop application: GrandMA2 (Telnet and OSC), GrandMA3 (TCP OSC and UDP OSC), Avolites Titan, ETC Eos, ChamSys MagicQ, Resolume, disguise (d3), TouchDesigner, Unreal Engine 5, QLab (TCP and UDP), MIDI Show Control, Pangolin Beyond, and Custom OSC. Every CueSync edition includes every protocol.
ETC Eos Questions
No — it's an automation layer alongside the desk. For shows without a dedicated Eos op it can drive the console end-to-end; on programmed shows it fires automated cues while the operator keeps manual override.
The standard Eos OSC surface — /eos/cue, /eos/key/go, /eos/chan, /eos/sub, and macro fires. No custom console programming is required beyond enabling OSC.
Yes. Any Eos system that exposes OSC works, including ETCnomad and the Nomad Puck, on a show LAN or a loopback for bench testing.
Different question? Ask us directly.
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.
ETC® and Eos® are trademarks of Electronic Theatre Controls, Inc. CueSync is an independent product and is not affiliated with or endorsed by ETC.