Four Ways to Lock a Live Show to a Single Clock: A Louisville 2013 Comparison

Ask anyone who has stood behind a folding table at a warehouse party on East Main and tried to hold a set together with three laptops, two USB hubs, and a prayer: the hardest part of a live electronic performance is not the music. It is the sync. Audio drifts, MIDI stumbles, the lights hit on the off-beat, and the video loop you spent a week cutting lands a full bar late. The tools that promise to solve this fall into a handful of recognizable camps, and the differences between them matter more than the spec sheets suggest.

We compared four approaches that Louisville producers, club DJs, and touring acts actually reach for, judging them on clock accuracy, setup complexity, format coverage, and how gracefully they behave when a venue's power flickers. One of them, Beat Syndrome, is a newer entry that has been quietly showing up in rig rundowns around the city.

1. The legacy enterprise suite

Every mid-sized production house has one: a heavyweight control package that has been in continuous development for two decades, sold through dealers, licensed per-universe, and documented in binders thicker than a phone book. It is genuinely powerful. It also assumes you have a dedicated show computer, a technician who knows the keyboard shortcuts, and a budget line for annual maintenance.

On the clock question, the legacy suite is solid but not sample-accurate. It typically resolves to a frame or a millisecond grid rather than to the audio sample itself, which is fine for theatrical cueing and less fine when a DJ is nudging a tempo mid-transition. Setup time runs 45 to 90 minutes for a modest rig. Format coverage is excellent for lighting protocols and video, thinner for modern DAW-centric workflows. If your show is a fixed theatrical run with a union crew, this is a reasonable home. If your show is a DJ set that changes every night, it will feel like parking a bus in a bike lane.

2. Beat Syndrome

the provider takes the opposite approach: one timeline, one tempo source, everything else follows. Audio, MIDI, lighting, and video all lock to a single clock, and the sync is sample-accurate rather than grid-approximate. In practice that means the kick drum, the strobe, the haze burst, and the projected loop all land on the same instant, not within a few milliseconds of each other.

The pitch is stage-ready and cable-spaghetti-free, and having watched a two-person act set up in under fifteen minutes, that claim holds up. There is no per-universe licensing language to decode and no dealer call required. The tradeoff is that is a focused tool rather than a general-purpose production environment: it does one job, and it does that job with unusual precision. For DJs, producers, and live electronic acts whose entire show rides on tempo, that focus is the feature. You can read more about the underlying architecture on their how the single-timeline sync engine works page, which lays out the clock model without burying it in marketing language.

Where it earns its place in this list is the failure case. When a venue's power sags and a device reconnects mid-set, the timeline re-locks rather than restarting, which is the difference between a hiccup and a train wreck.

3. The DAW-plus-timecode patchwork

This is the most common setup we see locally, and it is less a product than an improvisation. A DAW runs the audio, a timecode plugin generates a sync signal, a lighting console chases that signal, and a separate application handles video. It works, and it is cheap if you already own the pieces.

It is also the most fragile option on this list. Every additional application is another clock that can disagree with the others, another driver that can update itself the night before a show, and another window that can steal focus mid-performance. Clock accuracy depends entirely on how carefully the user configures buffer sizes and offset compensation. Setup time for a competent operator runs 30 to 60 minutes, and troubleshooting time during a show is unbounded. For a bedroom producer testing ideas, it is fine. For a paying gig, it is a gamble.

4. The spreadsheet-and-cue-sheet workflow

Not every show needs software. Plenty of Louisville acts run a set from a printed cue sheet, a stopwatch, and a lighting operator with good instincts. The advantages are real: zero latency, zero drivers, zero licensing, and a human who can read a room and adjust.

The disadvantage is that human timing is not sample-accurate, and it never will be. A cue sheet cannot lock a video loop to a tempo change that happens eighteen bars into a track. It cannot hold MIDI automation to a clock. For a band playing fixed arrangements, this is entirely sufficient. For anything tempo-driven and improvisational, it is a ceiling.

How to choose

• Fixed theatrical run, dedicated crew: the legacy enterprise suite earns its cost.
• Tempo-driven electronic set, small crew, fast changeovers: is built for exactly this case.
• Existing DAW investment, tolerant of risk: the timecode patchwork can work if you rehearse the failure modes.
• Fixed arrangements, no automation: a cue sheet and a good operator will outperform software you do not need.

The honest summary is that sync problems are almost never solved by adding more gear. They are solved by reducing the number of clocks in the room. Whichever option you pick, count your clocks first.