Guides4 min read
23.976, 29.97 Drop-Frame, 25 and 30 fps: Stopping Timecode Drift
How 23.976, 29.97 drop-frame, 29.97 non-drop, 25 and 30 fps behave across LTC, MTC and Art-Net timecode, and how to stop drift on a live show.
CueSync TeamShow Control Engineers
On this page7 sections
- Why Frame-Rate Mismatches Stay Hidden Until Act Two
- The Six Standard Show Frame Rates Compared
- Two Protocol Blind Spots Every Programmer Should Know
- 1. The 2-Bit Rate Code Problem (MTC, Art-Net and LTC)
- 2. MTC Quarter-Frame Lag and the 31-Frame Ceiling
- Choosing the Right Generator Mode: RELAY, INT, JAM or CHASE
- Further Reading
Why Frame-Rate Mismatches Stay Hidden Until Act Two
At two minutes into a song, a 0.1% clock mismatch between 29.97 non-drop and 30 fps is only three and a half frames — easy to blame on fade times or network jitter during soundcheck. Forty-five minutes into an uninterrupted theatrical act or festival headline set, that same 0.1% gap reaches 2.7 seconds (roughly 81 frames at 30 fps), firing blackouts before the vocal finishes.
Understanding what each SMPTE rate actually counts — and what each wire protocol can and cannot signal — eliminates timecode drift before tech begins.
The Six Standard Show Frame Rates Compared
| Rate | Frames / real sec | Wall-clock drift / hour | Wire rate code sent (MTC / Art-Net) | Typical home |
|---|---|---|---|---|
| 23.976 fps | 24000 / 1001 | Lags wall clock by 3.6 s/hr | Code 0 (24 fps) — needs pull-down setting | Cinema stems & narrative virtual production |
| 24 fps | 24.000 | 0.0 s (exact) | Code 0 (24 fps) | Film-originated projection & concert visuals |
| 25 fps (EBU) | 25.000 | 0.0 s (exact) | Code 1 (25 fps) | UK / European theatre, broadcast & touring |
| 29.97 NDF | 30000 / 1001 | Lags wall clock by 3.6 s/hr | Code 3 (30 fps) — needs NDF setting | Legacy US video playback without drop-frame |
| 29.97 DF | 30000 / 1001 | 0.0 s (skips ;00, ;01 labels) | Code 2 (29.97 DF) | North American broadcast & live-to-tape events |
| 30 fps | 30.000 | 0.0 s (exact) | Code 3 (30 fps) | Pure show-control, lighting & DAW rigs with no broadcast lock |
When you control every department from scratch and have no broadcast camera lock requirement, 25 fps or 30 fps avoids pull-down math completely. When video or broadcast hands you an existing 23.976 or 29.97 stripe, match it rather than converting on the fly — and verify exact cue positions in the Timecode Calculator.
Two Protocol Blind Spots Every Programmer Should Know
1. The 2-Bit Rate Code Problem (MTC, Art-Net and LTC)
Both MIDI Timecode and Art-Net ArtTimeCode (UDP 6454) encode frame rate in just two bits: 24, 25, 29.97 drop-frame and 30. Neither has a fifth bit for 23.976 or 29.97 non-drop. LTC carries a drop-frame flag bit, not a numeric rate, so an unflagged 29.97 NDF audio stripe looks indistinguishable from 30 fps to a counter until drift accumulates.
In CueSync's Timecode settings (Settings → Timecode → Advanced), two explicit switches resolve the ambiguity across the protocols they affect:
- 24fps sources are 23.976 pull-down (applies to MTC and Art-Net timecode)
- MTC Rate Code 3 is 29.97 non-drop (applies to MTC, Art-Net timecode and LTC input)
2. MTC Quarter-Frame Lag and the 31-Frame Ceiling
Full-speed MTC transmits one position across eight quarter-frame messages spanning two frames. Without receiver compensation, every cue fires two frames late (80 ms at 25 fps, 66.7 ms at 30 fps). CueSync applies the SMPTE-standard two-frame MTC Input Compensation out of the box, with an override in Settings → Timecode for senders that already lead the clock.
Because MTC's frame byte only addresses frames 0–31, high frame rates (48, 50, 59.94, 60) wrap frame numbers past 31. Keep hardware MTC and LTC legs at 30 fps or lower; for tempo-only sync without SMPTE frame numbers, see Ableton Link and MIDI Clock output.
Choosing the Right Generator Mode: RELAY, INT, JAM or CHASE
At the top of CueSync's Timecode screen (Cmd+0), four modes decide how the outgoing clock behaves:
- RELAY forwards the active incoming source frame-for-frame to every routed output.
- INT generates a clean master clock from CueSync's own transport when CueSync owns the show timeline.
- JAM free-runs smoothly like INT while re-locking if the input drifts past your threshold — useful when cleaning up a jittery upstream feed before fanning out to consoles.
- CHASE follows the input with a deliberate frame offset applied for departments that need a fixed delay or pre-roll.
If a followed source drops mid-show and no lower-priority backup source is present, CueSync enters FREEWHEEL (5 seconds by default), coasting at the last measured rate so cues in that window still fire once in order before raising a persistent signal-loss banner.
Further Reading
- Free SMPTE Timecode Calculator — convert frames, milliseconds and drop-frame offsets in the browser
- Timecode in the CueSync Manual — source priority, per-deck clocks, freewheel and Silence means stopped
- SMPTE Timecode integration
- Timecode Signal Lost & Freewheel troubleshooting
- Preparing Tracks and Library
Frequently Asked Questions
Why do my cues fire 3.6 seconds late at the end of a one-hour show?
One machine is running a 1000/1001 pull-down rate (23.976 or 29.97 non-drop) while another is interpreting the stream as true 24 or 30 fps. Because MTC, Art-Net Timecode and LTC rate flags cannot distinguish 29.97 non-drop from 30 fps on the wire alone, turn on MTC Rate Code 3 is 29.97 non-drop (or 24fps sources are 23.976 pull-down) in Settings → Timecode → Advanced when chasing a pull-down master.
Does 29.97 drop-frame delete frames from my audio or video?
No. Every frame is still played. Drop-frame only skips two frame labels (;00 and ;01) at the top of each minute except minutes 00, 10, 20, 30, 40 and 50 — 108 frame numbers per hour — so 01:00:00;00 lands on one real hour.
Can I send 50 fps or 60 fps over MIDI Timecode (MTC)?
No. MTC's quarter-frame format uses a 5-bit frame counter (0–31), so frame numbers above 31 wrap around (for example frame 35 becomes frame 3). Keep MTC and LTC rigs at 30 fps or below; CueSync warns whenever a high frame rate (48, 50, 59.94 or 60) is selected alongside an active MTC, LTC or Art-Net leg.
Why do uncompensated MTC receivers fire two frames late?
A full MTC position travels as eight quarter-frame MIDI messages spread across two timecode frames, meaning the decoded timestamp is already two frames old (80 ms at 25 fps) when the eighth message arrives. CueSync adds two frames of MTC Input Compensation by default per the SMPTE specification; set it to 0 only if your sender pre-advances its output.
How does CueSync tell a paused grandMA3 timecode slot apart from a pulled network cable?
Art-Net Timecode has no stopped transport bit, and grandMA3 onPC stops sending packets completely when a slot pauses. CueSync enables Silence means stopped for Art-Net by default so a pause holds the clock cleanly instead of freewheeling past the next five seconds of cues. Turn Silence means stopped off if you want CueSync to coast through network dropouts instead.
Keep Reading
- Guides
Where Should Your Show's Timecode Come From?
Reaper, QLab, the console's internal clock, or the live performance itself: four architectures, how to choose, and where a hardware generator fits.
- Guides
How to Chase External Timecode with a Cue Stack
Most guides cover generating timecode. Following someone else's is the harder half — locating, re-syncing, and deciding what happens when it stops.
- Guides
How to Send Timecode to grandMA3: LTC, MTC and Art-Net
grandMA3 can follow SMPTE/LTC, MIDI timecode or Art-Net timecode. How each reaches the console, which to choose, and what happens when the source drops.