Updated: September 4, 2026
The problem multi-camera creates
Covering a keynote with three cameras produces three separate recordings of the same forty minutes, each started at a slightly different moment, each with its own clock drifting at its own rate. Before an editor can cut between them, all three have to be lined up to the frame.
Done properly, that alignment takes minutes. Done badly, it takes an afternoon per session, and on a conference with eight sessions it becomes the largest single cost in post-production.
The work that prevents it happens on the shoot day, and mostly in the first ten minutes of it.
Timecode is the professional answer
Timecode is a running clock recorded into every file. When every camera and every audio recorder carries the same clock, the edit software lines them up automatically, and it stays lined up across a recording of any length.
Two things have to be true for this to work. All devices must agree on the timecode, which is achieved either by feeding them from one source or by jam-syncing them from a master. And they must be set to the same frame rate, because timecode running at one rate against footage at another produces an offset that grows through the day.
Jam-syncing means connecting each device briefly to a master clock so it adopts the same time, then disconnecting. Internal clocks drift, so this is repeated periodically, typically at the start of the day and again after a few hours, and always after a battery change on a device that does not hold the clock.
The habit worth building is checking, not assuming. Photograph the timecode display on every device after jamming. It takes thirty seconds and it is the only evidence you have if something is wrong later.
When timecode is not available
Plenty of cameras used on corporate work do not support timecode. Audio sync is then the reliable fallback, and it works well provided every camera records some audio.
The requirement is that each camera has a usable reference track, even a poor one from the on-board microphone. Editing software matches waveforms across clips and aligns them, and it does this accurately as long as the sound is recognisably the same event.
This is why a camera at the back of a ballroom should still be recording audio, and why muting a camera to save card space is a false economy. A silent camera cannot be synced automatically and has to be aligned by eye.
The slate, and why it still exists
A clapperboard looks like something from a film set and belongs at a conference for exactly the same reason: it makes a single, unambiguous moment visible and audible on every recording.
You do not need a real slate. A sharp handclap in front of all cameras before a session works identically, provided every camera can see and hear it. Do it once at the start of each session, in a place all lenses can see, and say what it is so the editor knows.
This is a backup rather than a primary method, and it costs nothing. When the timecode turns out to be wrong on one camera, the clap is what saves the session.
Practical settings to agree before doors open
- Frame rate, identical across every camera, decided and written down
- Shutter, set to avoid flicker against the room's lighting and the LED wall
- Colour temperature, matched manually rather than left on automatic, so cameras do not drift apart during a session
- Picture profile, the same on all bodies, so the grade starts from one place
- Card and file naming, distinct per camera, because three cards of identically named files is an avoidable disaster
- Recording continuously or per session, agreed in advance, since mixed approaches complicate the sync
Automatic white balance deserves the emphasis. In a room where stage lighting changes colour during a presentation, cameras left on automatic will each make their own decisions at their own moments, and the cut between them becomes visible in a way no grade fixes cleanly.
Getting sound from the room
The best audio at a corporate event does not come from any camera. It comes from the venue's sound desk, as a direct feed of the microphones already mixed for the room.
Arrange this in advance with the AV team rather than on the morning. You need to agree where the feed comes from, what level it arrives at, and what connector it uses. Bring adapters, because the answer is never the one you expected.
Record that feed to a dedicated recorder with timecode where possible, and also record a backup from a camera microphone. A desk feed can fail silently, and a room track lets you rescue a session. It also gives the editor a reference for applause, laughter and the general sound of the room, which a clean feed lacks entirely.
Coordinating this is part of the wider relationship with the venue's AV crew, which we cover in working with venue and AV vendors.
Where sync usually breaks
A handful of causes account for nearly every sync problem on corporate multi-camera work, and all of them are avoidable once you know to look.
A camera set to a different frame rate. Usually one body that was used for something else the week before and never reset. It will look fine on its own and refuse to line up with anything.
Long recordings that split into segments. Many cameras break a long take into several files. That is harmless if the segments are continuous, and it becomes a problem when one camera splits at a different point and an editor assumes the files match one to one.
A battery change mid-session. The camera stops, someone swaps the battery, and the new file starts with a gap that nobody recorded the length of. Note the time when it happens.
Drifting clocks on long days. Devices jam-synced at eight in the morning can be measurably apart by late afternoon. Re-jam at lunch as a matter of routine.
Variable frame rate footage. Phones and some hybrid cameras record at a rate that fluctuates. It syncs at the start and drifts progressively, which is the most frustrating version of this problem to diagnose.
What to do at the end of each session
Sync problems are cheap to fix on the day and expensive to fix a week later. Build a short routine between sessions.
Check that every camera actually recorded and did not stop on a full card or a flat battery. Confirm timecode is still matching across devices. Note anything unusual in a shooting log: a camera restarted mid-session, a battery change, a moment when someone walked in front of a lens. Back up cards before the room is reset, not at the end of the day.
That log is what the editor reads first. A line saying that camera two stopped for four minutes during the second panel saves an hour of confused searching, and it costs ten seconds to write.
We shoot conference and corporate work with matched settings and locked sync as standard, and we hand over footage that assembles rather than footage that needs rescuing. Other articles on event coverage are on the blog, how we plan a shoot is described in the run of show, and there is more about the team on the about page. If you have an event coming up, send us the agenda.