How CueSync Detects Beats: Inside the Sub-15ms Analysis Engine

The Core Claim

CueSync's marketing line is simple: real-time audio analysis across 14 protocols at sub-15ms latency. The "sub-15ms" number is the headline spec; this post explains what it means for a working rig and which CueSync features it enables.

What's Publicly Documented

Here's what CueSync's official documentation says about the beat engine (FAQ, integrations page, and landing pages):

• Latency: "Our beat detection algorithm runs at under 15ms latency, which is imperceptible to the human eye. This includes audio analysis, pattern matching, and output signal generation." (FAQ)
• Audio inputs: Pioneer PRO DJ LINK (native reader), any CoreAudio (macOS) or ASIO (Windows) audio interface, MIDI Clock, Ableton Link.
• Exposed events: Beat, phrase, energy, and drop triggers (DJ Edition landing page).
• Track Structure Analysis: "AI-powered breakdown of intros, builds, drops, and breakdowns — know the track before it plays." (DJ Edition landing page)
• Frequency analysis: The homepage and landing pages describe "real-time audio analysis" with frequency-band reactivity. Exact band splits and algorithm details aren't published.
• Deployment: Runs on macOS 12+ and Windows 10/11, with Linux planned (FAQ).

Everything else about the engine's internals — algorithm choices, specific FFT window sizes, confidence scoring, ML vs classical DSP — is not publicly documented. This post describes the observable behavior and the features that ride on the engine.

Inputs: Where the Audio Comes From

Pioneer PRO DJ LINK (Native)

Per the Pioneer DJ Link integration page, CueSync reads CDJ/DJM beat phase, BPM, master tempo, and track metadata directly over Ethernet — "no audio analysis latency." When you're on compatible Pioneer hardware (CDJ-3000, CDJ-2000NXS2, DJM-V10, DJM-A9, DJM-900NXS2, XDJ-XZ), this is the most accurate beat data possible because CueSync is reading what the CDJ already knows from the rekordbox-analyzed beat grid.

Audio Interface Input

For any other audio source — vinyl, live bands, Serato, Traktor, Ableton, microphones — CueSync listens to a line input via CoreAudio (macOS) or ASIO (Windows). The analysis engine runs on that signal and emits events. Professional audio interfaces with tuned low-latency drivers reduce the capture latency component of the sub-15ms budget.

Ableton Link

CueSync joins Ableton Link sessions on the local network and reads tempo and phase from Link peers. This is useful for Ableton-driven DJ sets and for tightly coupling CueSync's events to an Ableton Live master clock.

MIDI Clock

Tempo sync from any MIDI Clock source is also supported as an input.

Stage 3 — Beat, Phrase, and Energy Events

The analysis pipeline emits a stream of musical events that the Routing Editor can subscribe to. Per the DJ Edition landing page, the exposed event types are:

• Beat — individual beat detection locked to the music's tempo
• Phrase — phrase-boundary detection for 8-bar and longer structural changes
• Energy — continuous energy level tracking for dynamic intensity changes
• Drop — detection of drops and major transitions
• Track Structure — the DJ Edition landing page describes this as "AI-powered breakdown of intros, builds, drops, and breakdowns — know the track before it plays"

Each event is available as a trigger in the Routing Editor. You bind events to protocol outputs — beat to fixture pulses, phrase to scene changes, drop to full-rig moments — and CueSync dispatches them in real time.

Latency: The Sub-15ms Target

The official spec, per CueSync's FAQ: "Our beat detection algorithm runs at under 15ms latency, which is imperceptible to the human eye. This includes audio analysis, pattern matching, and output signal generation."

That budget covers the complete path from audio input to protocol output. Human perception of audio-visual desync becomes noticeable around 20-40 ms, so sub-15 ms is below that threshold — the lights appear to move in lockstep with the music, not chasing it.

The internal implementation breakdown isn't publicly documented. What IS documented is the observable behavior: sub-15ms end-to-end, on-device processing, no cloud dependency. That's what matters for a show.

Pioneer PRO DJ LINK: The Cheat Code

When you're running Pioneer CDJs or XDJs, CueSync bypasses audio analysis entirely for BPM and beat phase. PRO DJ LINK is Pioneer's proprietary Ethernet protocol that carries BPM, beat phase, track metadata, and master tempo from the CDJ's internal clock — which is synced to the track's rekordbox-analyzed beat grid.

CueSync reads PRO DJ LINK natively (no Beat Link Trigger or external bridge required) and uses the CDJ data as the primary beat source. Audio analysis still runs in parallel for energy and frequency data, but the timing information comes from the deck.

This is the most accurate beat source possible in a DJ rig because there's no inference involved — CueSync knows what the CDJ knows.

Compatible hardware: CDJ-3000, CDJ-2000NXS2, XDJ-XZ, DJM-V10, DJM-A9, DJM-900NXS2.

Ableton Link as a Second Source

For Ableton-centric rigs, CueSync joins the Ableton Link session and reads tempo and phase from Link peers. This gives sub-millisecond phase alignment between CueSync and any Link-compatible app on the local network — better than SMPTE and easier to set up.

Link is a receive-only source on DJ Edition (CueSync doesn't push tempo back, but it locks to whatever the Ableton Link session is doing). Combined with audio analysis, it's the right choice for Ableton-driven DJ sets.

On-Device, No Cloud

Everything above runs on your laptop. There's no network dependency for the analysis, no telemetry, no cloud service the show depends on. If the Wi-Fi drops or the venue has hostile network infrastructure, CueSync keeps running — only the network-protocol outputs (Art-Net, sACN, OSC) care about the local LAN.

This matters because live shows are hostile environments. A system that needs to phone home mid-performance is a system that will fail mid-performance.

Why This Matters for Lighting

A cheap color organ in the 1980s could flash a light on bass hits. That's not what stage automation is. The difference between "reacts to loud sounds" and "understands what the music is doing" is the difference between a strobe that flashes mechanically on every kick drum and a lighting rig that builds tension through a 16-bar phrase, drops on the drop, and fades during the breakdown.

CueSync's multi-stage pipeline exists to give the routing editor a rich event stream — not just "beat, beat, beat" but "beat (confidence 0.87), phrase boundary (bar 16), energy delta +0.3, drop predicted T+800ms, bass-band pulse (intensity 0.92)." Feed that into the Routing Editor and you get musical lighting instead of mechanical flashing.

Try It

Download CueSync free and open the Protocol Monitor while playing a track. You'll see the beat events fire, the energy meters move, and the phrase boundaries trigger. It's the same analysis engine that drives every CueSync rig in production.

For the broader picture, see what is music-driven lighting automation and 5 ways AI is changing live event production.