Timecode vs beat grid: two ways to sync a show to music

Every show eventually needs a fixed clock. Somewhere between the shared timeline and the desk, a cue becomes a locked, framed address that a console fires on: that's timecode, and it's necessary. But nobody actually designs a show by thinking in hours, minutes, seconds, and frames. Designers think in beats: the build eight bars before the drop, the breakdown at the two minute mark, the moment the vocal comes back in. That's the real language of a show, and it's why EdiTour is built around the beat grid, not the clock.

What is SMPTE timecode, and why does a show need it?

SMPTE timecode is a signal that gives every frame of a show a unique address in hours, minutes, seconds, and frames (HH:MM:SS:FF), counting against a 24 hour clock. ETC's own quickguide on the format describes it as giving production equipment, lighting, audio, video, "a system wide clock that is referenced by everything else." A lighting console like a grandMA3 reads that signal and fires cues at the exact timecode address they were stored against. MA Lighting's timecode documentation covers how the console can take in up to eight external timecode sources at once, on top of running its own internal clock.

Timecode is a utility. It doesn't know or care what's making the sound, it just counts, frame by frame, forever. That's exactly what makes it good at its job: once a show is locked, timecode is the most reliable way to make sure lighting, video, and pyro all land on the same frame, every single time.

What is a beat grid, and why is it how designers actually think?

A beat grid is what DJ software lays over a track's waveform to mark where the beats and bars actually fall. Serato's own explainer describes beatgrids as the thing that lets features like Sync "snap together" between tracks, and notes that if the grid is wrong, "your mixes will be out." Unlike timecode, a beat grid isn't fixed. It's tied to the music's actual tempo, so if a track speeds up, slows down, or gets pitched, the grid moves with it.

That's closer to how a show actually gets designed. Nobody sits down and says "put the strobe at 00:01:48:00." They say "hit the strobe on the filter sweep, four bars before the drop." Analyzing the track's structure first is what makes that possible: you're marking musical moments, bar 32, beat 3, not clock times, because that's the unit the whole creative conversation already runs on.

So which one should your show actually run on?

Timecode wins when the show is genuinely fixed. Pyro cues, a pre-rendered video sequence, a synced audio stem, anything running off a single locked file wants a hard clock, because those systems have no concept of "the beat moved." A festival headline set with a locked setlist and a heavily produced backing track is a good candidate, especially once video and pyro departments are involved, since those tend to be timecode-native either way.

Beat grid wins whenever the music isn't fixed, and for most DJ and festival sets, it isn't. Tracks get extended, cut short, blended into each other, or pitched up for energy. A timecode-locked show has no way to react to any of that, it just keeps counting whether the music matches or not. A beat grid, tied to the actual tempo of what's playing, keeps a show's cues locked to the music even when the set doesn't go exactly as rehearsed.

Why does EdiTour design in beats even though the show still runs on timecode?

Because the two aren't actually in competition. They're doing different jobs. Timecode answers "what time is it." A beat grid answers "where are we in the music." The clock is what a desk needs to execute reliably. The beat is what a room full of people, lighting, lasers, video, the artist, actually uses to talk to each other while they're designing.

Most tools make you pick one and work in it from the start, which means every department not thinking in that unit is constantly translating. That reconciliation problem usually lands on whoever's coordinating the show. We built EdiTour's shared timeline around musical time, bars and beats, as the native unit, because that's the language the whole creative conversation is already happening in. Timecode still runs the show on show day. It just isn't where the show gets designed.

Can a show use both?

Yes, and most do. It's common to run timecode for the parts of a show that are genuinely fixed while lighting and lasers stay locked to the beat grid for the portions that actually flex. If every department is already agreeing on the same reference before load-in, which system ends up driving the desk on show day matters less, because the design work already happened in the unit that made sense: the beat.

If your show runs on beats more often than it runs on a fixed clock, and if you're designing for a DJ or festival set it almost certainly does, try building your next show's timeline against the actual beat grid instead of a locked clock.