How to sync two action cameras and cut between the angles

Last updated 2026-08-31 · 7 min read

What is the short version?

Two cameras filmed the same run — one on the bike or in the cockpit, one at the side of the track. Cutting between them is what makes a clip feel like a broadcast rather than a home video, and the whole thing collapses if the two recordings are even half a second out.

1. Go to Vizard Agent and upload both recordings.
2. Say which moments matter — the overtake, the braking point, the finish.
3. Say the format and the length you need.

What do you need before you start?

Two recordings that genuinely overlap in time, and some idea of the moment the clip is being built around. Vizard Agent can find the alignment itself from the sound, but it cannot align two runs that were never happening simultaneously in the first place.

• Both files. The same run, two positions.
• Sound on both. Even rough audio is enough to align.
• The key moment. The overtake, the pass, the save.
• The format. Vertical for social, landscape for a channel.
• A length. Ten to fifteen seconds cuts hard.

What do you type into Vizard Agent?

Say what should drive the cutting rather than listing the cuts. Vizard Agent decides where to change camera from what you tell it about the action, so "change angle whenever it adds speed, especially into braking and overtakes" is a far more useful instruction than a numbered edit list.

Prompt

Variants worth knowing:

• Name the moment. The overtake, not "the good bit".
• Say how often. Every one or two seconds reads as broadcast.
• Slow motion sparingly. On the single most important instant.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real two-camera race edit. The step that decides whether any of it works is the fifth, where the exact time offset between the two cameras is calculated — and the sixth, where that alignment is checked rather than assumed.

1. Reads the technical information on both uploaded files.
2. Extracts thumbnails from each to see the angles and rough sync.
3. Views the frames from camera one, then camera two.
4. Extracts detailed samples and the audio for precise alignment.
5. Calculates the exact time offset between the two recordings.
6. Checks the sync visually, side by side, and views the result.
7. Searches the catalogue for a high-energy track, downloads candidates and measures their loudness and energy.
8. Maps the rhythmic peaks of the music so the cuts can land on them.
9. Tests the vertical framing for each angle, including a separate pass on the cockpit view.
10. Maps the overtake precisely in both cameras and checks the cockpit view at the decisive instant.

Steps five and six are the ones people skip. Vizard Agent aligns the recordings from their audio and then looks at the two streams side by side to confirm it, because a cut between two angles that are a few frames apart looks like a mistake rather than an edit.

What does the result look like?

The source recordings for the run this page is written from measured 1920x1080, H.264, 60fps with AAC audio — high frame rate, which is what makes a slow-motion beat on the overtake hold up. The delivery was a short vertical cut, angles changing every second or two.

The effect is specific and hard to fake: the same overtake seen from outside and then from the cockpit, in sequence, with the sound continuing unbroken underneath. That continuity is only possible because the two cameras were aligned first.

When does this not work well?

Multi-angle cutting depends entirely on the two recordings actually describing the same moment, and there are several ways that fails. Vizard Agent tells you when the alignment is uncertain rather than quietly cutting to an angle that shows something else.

• No usable audio on one camera. Alignment gets much harder.
• Runs that do not overlap. Two different laps cannot be intercut.
• One camera much shakier. Cutting to it every second is unwatchable.
• Very different frame rates. Slow motion suffers on the lower one.
• A tiny overlap. Two seconds in common is not an edit.

How do you fix a result that came back wrong?

Say which cut feels wrong and what it should show. Vizard Agent keeps the calculated offset, the framing tests and the map of the key moment, so a cut can be moved or an angle swapped without the alignment work being repeated.

• "The overtake is on the wrong camera." Swapped from the mapped moment.
• "It cuts too often." Held longer between changes.
• "The slow motion is on the wrong beat." Moved to the mapped instant.

How does Vizard Agent compare to doing it yourself?

By hand this is the classic tedious job: dragging two clips against each other on a timeline until the sound lines up, then discovering it drifted, then cutting between angles by eye and hoping the rhythm holds. Vizard Agent does the alignment arithmetically and checks it visually.

Common questions

How does it sync the cameras? From the audio. Vizard Agent calculates the exact offset between the two recordings and then confirms it visually.

What if one camera has no sound? It becomes harder. Vizard Agent falls back to matching visible events, which is less precise.

How often should the angle change? Every one or two seconds for an action edit. Vizard Agent holds longer where the action is slower.

Can it handle three cameras? Yes. Vizard Agent aligns each one to the same reference and cuts between all of them.

Does the music matter? A great deal. Vizard Agent maps the track's rhythmic peaks and lands the cuts on them.

Can I get a landscape version? Yes. Vizard Agent re-frames from the same aligned sources without re-syncing anything.

What about slow motion? Used sparingly. Vizard Agent puts it on the single most important instant rather than throughout.

Does high frame rate help? Considerably. Vizard Agent gets clean slow motion from 60fps footage that 30fps cannot give.

What if the two cameras look different? Vizard Agent evens out the exposure and colour between them so the cuts do not flash.

Can it find the overtake itself? Usually, if you say roughly when. Vizard Agent then maps the precise frames in both cameras.

Does this work for sports other than racing? It works anywhere two cameras covered one event — a lift, a jump, a goal, a stage performance. The technique is the alignment, not the sport, and Vizard Agent treats them all the same way.

Why not just cut it by eye? Because a few frames of drift between angles is visible to everyone and explainable by nobody. Vizard Agent removes that failure mode by measuring the offset instead of estimating it.

Can it keep the original engine sound? Yes. Vizard Agent can run the original audio under the music, which is usually what makes a racing edit feel real.