What are multicam and sync clips?
Two cameras, a lav, and a boom become one clip you can cut — Final Cut's containers for keeping a shoot in sync.
Multicam clips and sync clips are Final Cut Pro containers that bind separately recorded sources into a single synchronized clip. A multicam clip holds multiple camera angles you can switch between while editing; a sync clip typically marries picture with separately recorded audio. Either way, the timeline treats the group as one unit.
What's the difference between a multicam clip and a sync clip?
Both solve the same underlying problem — footage of one moment arrived as several files — but they're built for different situations. A multicam clip arranges its sources into named angles and gives you the Angle Viewer, where you watch every camera at once and cut or switch between them live; each cut in the timeline remembers which angle is active, and you can change your mind per-edit forever after. A sync clip (Final Cut calls the command Synchronize Clips) simply locks its components together into one clip with no angle-switching interface. Its classic job is dual-system sound: the camera's picture joined to the recorder's clean audio, with the scratch track disabled. Rule of thumb: several cameras you'll cut between, make a multicam; one camera plus external audio, a sync clip is lighter and enough.
How does Final Cut sync the angles?
When you create either container, Final Cut lines the sources up using whatever evidence they carry. Audio waveform analysis is the everyday workhorse — every device heard the same room, so matching the waveforms aligns the files, no slate required. Timecode is the precision option when cameras and recorders were jammed to a common clock on set. Beyond those two, Final Cut can fall back on markers you set at a common frame or on each file's recorded start time, which is coarser. In practice, run-and-gun shoots live on waveform sync, and broadcast-style shoots with synced timecode get frame-exact alignment for free.
Why do interview shoots rely on them?
Because the standard interview setup is inherently multi-source: a wide and a tight camera on the subject, sometimes a third on the interviewer, plus a lav and a boom running into a separate recorder. Grouped into a multicam clip, that whole setup edits like a single interview — punch in to the tight camera on the emotional beat, go wide when the subject gestures, and never think about sync again. It also keeps the edit honest later: when a line needs to be shortened, cutting to the other angle hides the join without a jump cut. For long-form interview projects, building multicam clips is typically the first act of organization after ingest.
Once the interview is synced, the work turns editorial: pull selects, build a stringout, and move toward a rough cut — with FCPXML carrying the containers between tools.
What happens to them in transcription and round-trip workflows?
This is where containers earn or lose their keep. In FCPXML, multicam and sync clips appear as their own element types (mc-clip and sync-clip), so an outside tool sees the container, not a flattened pile of source files. A transcription tool has to look inside it and choose the right audio — ideally the clean recorder track, not a camera's scratch mic — and a round-trip tool writing a sequence back should reference the containers themselves, so the timeline that lands in Final Cut still lets you switch angles. Tools that flatten to a single source file lose exactly the flexibility the container existed to provide. When evaluating any transcription or AI-assist tool for interview work, "does it understand multicam and sync clips" is a sharper question than most feature-list items.
Doza Assist reads Final Cut libraries — multicam and sync clips included — through XML, so a large library transfers as kilobytes of structure with no re-transcode, and the story work happens locally on your Mac. See how wedding filmmakers use it on multicam ceremonies.
Common questions
Do multicam clips duplicate my media?
No. The container references the original files; nothing is copied or re-rendered when you build one. That's why you can group hours of footage into multicam clips in seconds and delete or rebuild the containers freely.
Is audio sync or timecode sync better?
Timecode is exact when every device was genuinely jammed to a common clock, so use it when you have it. Waveform sync is the practical default for everything else and is usually accurate enough that you can't see the difference — it only struggles when a source's audio is too quiet, too distant, or missing.
Will a transcription tool use the right audio from a multicam clip?
Only if it understands the container. A tool reading the library via XML can find the components and prefer the clean external-recorder audio over a camera scratch track; a tool that just ingests one media file may transcribe the worst microphone on set. It's worth verifying with your own footage.
Doza Assist reads FCP multicam and sync clips via XML, transcribes and labels speakers locally, and returns selects to your timeline.
Free trial: every feature on your first 2 minutes — no account, no card · 30-day money-back guarantee · Requires a Mac with Apple Silicon (M1 or later)