GUIDES · 2 OCTOBER 2026 · 4 MIN
How to sync a multicam DJ set by sound
Timecode rarely survives a club night. Cameras start and stop, clocks are an hour off, the drone records no sound at all. Sound is the one thing every angle shares, so that's what to sync on.
Why timecode isn't enough in a club
Timecode works when every device is jammed to one clock and nobody touches it. A night out rarely looks like that:
- action cams and phones have no timecode, only the time the file was made;
- many cameras run record-run timecode, which stops whenever the camera does;
- device clocks disagree: an hour apart, sometimes on the wrong date (a recorder that thinks it's last month is common);
- a roaming camera makes dozens of short takes, and each one needs its own place.
The clock is still a good first guess. The sound decides.
Make the recorder the reference
Record the mixer's output to a recorder (a Zoom H8, an H6, or a USB recorder off the booth output) and make that the master. It runs the whole night without a gap, it's clean, and every camera hears a version of the same music through the PA.
Line each camera up against the recorder, not against another camera. Two camera mics that both hear a loud room match each other badly; a camera against the desk feed matches well.
Two details that trip people up:
- Long recordings are split into several files (a WAV tops out at 4 GB, and many recorders cut at 2 GB). Join the parts in order before you sync, or sync each part on its own.
- Some recorders write left and right as two mono files (Tr1 and Tr2 on a Zoom). Keep them together as a stereo pair, or the mix ends up on one side.
When the camera's sound is useless
Next to a loud PA, a camera's built-in mic often clips or gets flattened by its limiter: the waveform turns into a solid block and the beat disappears. Matching waveforms then finds nothing, or the wrong spot.
What still works:
- match the sound's envelope (how loud it is over time) instead of the raw waveform;
- match short windows at several points along a long take, not one spot at the start;
- check that those points agree. If they all fall on one straight line, the sync is right even when each single match is weak.
Drift: the five-hour problem
No two devices run at exactly the same speed. A few parts per million sounds like nothing, but over a five-hour set it adds up to frames, sometimes most of a second. A camera that's spot on at the start is visibly late at the end.
Measure the offset near the start and near the end of every long take. If the two differ, the take has to be stretched to the recorder's time, not just slid.
Cameras with no sound
Drones and some action cams record no audio. Place them by their clock first, corrected by the offset you found for another device on the same clock. Then check against the light: club lights flash on the beat, so the brightness of a drone shot pulses with the music. Two or three flashes that agree within a fraction of a second are a good sign. One match on its own isn't, because the lights flash on every beat.
How to check a sync
- Play the recorder and the camera's own sound together in mono. In sync, they sound like one source; a few milliseconds off, you hear a flam or a hollow, phasey sound.
- Zoom into a kick drum on both waveforms: the transients should line up.
- Check the start, the middle and the end of every long take.
In Premiere Pro or DaVinci Resolve
Both editors can sync by sound. In Premiere Pro, select the clips and create a multi-camera source sequence with the synchronize point set to Audio. In DaVinci Resolve, select the clips in the media pool and use Auto Sync Audio, Based on Waveform. Both work well for a handful of clean clips. On a five-hour night with crushed camera sound, drift and dozens of roaming takes, expect to fix a fair number by hand.
BeatPilot