When you generate a depth or time overlay in DiveHUD, it starts from when your watch started recording, which is rarely the exact frame your camera started rolling. A few seconds off and the numbers stop feeling real. Here's how to get it frame-accurate.
Find a sync point in your footage
Look for a moment you can identify in both your video and your dive data:
- The splash: the moment you duck-dive or drop below the surface, where depth starts climbing off zero
- A known depth marker: if you touched a line or platform at a marked depth, that's an exact reference point
- The ascent: the last few seconds before you break the surface, where depth drops back toward zero
Duck-dive entry is usually the easiest. It's a clear visual event, and it's the exact moment your DiveHUD depth counter starts moving.
Line it up in your editor
- Place your dive footage on the main track and your DiveHUD overlay on the track above it (see how to add your overlay in CapCut, or why Screen blend beats a green screen, if you haven't set the blend mode yet).
- Scrub to the frame in your footage where you break the surface and start descending.
- Slide the overlay clip left or right on the timeline until depth
0lines up with that frame. - Scrub forward to a few points later in the dive and check the numbers still feel right. If your watch's GPS or barometric sampling rate is low, there can be a slight lag between real depth changes and what the counter shows, so a one or two frame nudge is normal.
Trim and export
Once it's aligned, trim both clips to the same length so the overlay doesn't run past your footage or cut out before it, then export. A few seconds of care here is the difference between an overlay that looks pasted on and one that looks like it was always part of the shot.
