Resolume Arena + Timecode: CueSync's Sub-Frame Sync in 2026

Why Timecode for DJ/VJ?

Timecode is the way to lock pre-rendered video content to a musical performance. When you need a specific visual cue to hit on a specific beat — the title card to appear on the drop, the lyric video to roll when the verse starts, the logo animation to land on the downbeat — you need a shared clock that both CueSync and Resolume follow.

Without timecode, you rely on operator reflexes or audio-reactive triggering. Both work, but neither is frame-accurate for pre-rendered content. Timecode is.

CueSync's approach to timecode is to be the master clock for the entire rig. CueSync Theatre Edition (coming soon) generates the 5 timecode formats documented in pricing.ts — LTC, MTC, Art-Net Timecode, sACN Timecode, and TCNet — and Resolume Arena locks to whichever format you prefer. CueSync can also receive Ableton Link as an input for tempo sync (available in every edition). The result: perfect sync between your lighting automation and your video playback, with drift protection built in.

This guide covers Theatre Edition territory — LTC and MTC generation live there. For audio-reactive Resolume workflows using the DJ Edition, see the real-time Resolume sync guide.

Resolume Arena's Timecode Support

Arena supports three timecode inputs:

1. SMPTE LTC (Linear Timecode) — audio-based timecode delivered through a hardware audio input
2. MTC (MIDI Timecode) — same concept but over MIDI
3. Ableton Link — peer-to-peer tempo and phase sync over the local network

Each has trade-offs.

SMPTE LTC is the video industry standard. Frame-accurate (at 24/25/30 fps), audio-delivered, works with any rig that has an audio interface, widely understood. Latency is ~1 frame.

MTC is the same concept but over MIDI cables or virtual MIDI. Easier to route on a single machine, no audio interface needed. Frame-accurate.

Ableton Link is peer-to-peer beat/phase sync over TCP. Sub-millisecond accuracy, no configuration, works over local network between any Link-compatible apps. This is the best option for tight musical sync between Resolume and CueSync when both run on networked Macs.

Setup: SMPTE LTC from CueSync to Resolume

Requires CueSync Theatre Edition.

Step 1: Enable LTC generation in CueSync

1. Settings → Protocols → Timecode
2. Select Generate LTC
3. Choose frame rate (24, 25, 29.97, 30)
4. Route LTC output to your audio interface's physical output

Step 2: Route the LTC signal to Resolume

Your audio interface sends the LTC signal out as a normal audio channel. Route that channel back into Resolume's machine (or the same machine) via:

• Physical loopback: audio out → audio in via a cable
• Aggregate device: macOS aggregate device exposing CueSync's output as Resolume's input
• Virtual audio: BlackHole or Loopback virtual audio driver

Step 3: Configure Resolume

1. Open Resolume Arena → Preferences → SMPTE
2. Select the audio input carrying the LTC signal
3. Arena displays the incoming timecode when CueSync starts transmitting

Step 4: Lock clips to timecode

In Arena, each clip can be configured to trigger at specific timecode values. Right-click a clip → Trigger → Timecode → set the target time. When CueSync's generator reaches that value, Arena fires the clip automatically.

Alternative: Ableton Link for Sub-Millisecond Sync

If you're running CueSync and Resolume on the same machine or on the same local network, Ableton Link is the fastest path to tight sync and requires zero configuration.

Setup

1. In CueSync: Settings → Protocols → Ableton Link → enable
2. In Resolume: Preferences → Link → enable
3. Both apps immediately join the local Link session

What Link gives you

• Shared tempo (BPM)
• Shared beat phase (where in the bar each app thinks it is)
• Shared quantum (larger phrase boundaries — bars, 4-bar cycles)

What Link does not give you

• Frame-accurate clip triggering (you still need OSC or timecode for that)
• Multi-day absolute timecode (Link is musical-time only, not wall-clock)

For DJ sets where you want Resolume clips to sync to CueSync's beat detection, Link is the right choice. For pre-rendered show content that must hit specific timecode positions, use SMPTE LTC.

Drift Protection

The whole point of using CueSync as the master clock is drift protection. In a typical rig:

• Lighting runs on one clock (CueSync's internal)
• Video runs on another (Resolume's internal)
• Audio runs on a third (the DJ software or mixer)

Even tiny clock drifts compound over a multi-hour show, and by the end nothing lines up. Using CueSync's timecode generator as the source of truth for Resolume means Resolume's clock is disciplined by CueSync's, and drift is eliminated.

For touring shows where video content is tightly pre-rendered, this is the difference between a show that still lines up at song 15 and one that needs a re-sync every few tracks.

Hybrid Workflow: Timecode + Audio-Reactive

CueSync Theatre Edition (coming soon) is designed to run reactive and timecoded workflows simultaneously. A common pattern:

• Timecoded: pre-rendered visual content (title cards, artist animations, specific music video clips) fire off LTC positions
• Audio-reactive: background layers (particle effects, audio-reactive shaders, energy-tracking color fills) react to live audio analysis over OSC

The audio-reactive layer runs on top of the timecoded layer, so you get tight synchronization on the pre-built content and live responsiveness on the ambient background. This is how festival stages handle artist-specific visual content while still reacting to the live mix.

Drift Test

Before going live, run a drift test:

1. Start CueSync's LTC generator
2. Start a clip in Resolume locked to LTC
3. Let it run for 30 minutes
4. Verify the clip is still on-time against a wall clock

If drift is happening (rare on modern gear but possible with sample-rate mismatches), check your audio interface's sample rate, Resolume's frame rate setting, and any aggregate device configurations.

Try It

Theatre Edition (coming soon) will ship with the complete timecode generator plus sACN and Art-Net Timecode for video server lock. For DJ-focused audio-reactive Resolume work that doesn't need frame-accurate clip triggering, the DJ Edition Resolume guide covers the OSC workflow available today.

Download CueSync and check the Resolume integration page for deeper setup references.