Cutsio Blog

How to Fix Audio Delay in DaVinci Resolve

Fix audio delay in DaVinci Resolve by separating monitoring latency from timeline sync, then checking sample rates, timecode, clip alignment, and playback hardware.

What is the fastest way to fix audio delay in DaVinci Resolve?

Short answer: determine whether the delay is only in your headphones or is baked into the timeline. Wired monitoring can expose a playback-latency problem; waveform and clap alignment can confirm a real sync problem.

Audio that sounds late while monitoring is not always out of sync in the exported file. Bluetooth headphones, USB interfaces, display audio, and software monitoring can add latency between the timeline and what you hear. A clip that is genuinely misaligned shows a consistent offset when the waveform, mouth movement, or sync marker is compared on the timeline.

Test the same section through the computer speakers, a wired headset, and the exported file if possible. This simple comparison prevents you from moving a perfectly aligned audio clip to compensate for a monitoring delay.

How do you fix monitoring latency from Bluetooth or an audio interface?

Short answer: use wired monitoring for sync-critical work, select the intended audio output in Resolve, and avoid changing clip timing until the monitoring path is confirmed.

Bluetooth adds buffering because the signal must be encoded and transmitted before it reaches the headphones. Similar latency can come from a display, USB interface buffer, or audio driver. For a reliable sync check:

1. Connect wired headphones or use the computer’s built-in speakers.
2. Open Resolve’s audio I/O settings and confirm the intended output device.
3. Play a section with a clear clap or consonant.
4. Compare the sound to the visible action.
5. Export a short test if the monitoring path is still uncertain.

Do not correct a monitoring problem by slipping every audio clip. That can make the delivered file wrong even though it sounds better through one delayed device.

How do you fix audio that is actually out of sync?

Short answer: compare the audio waveform with a visible sync event, unlink the clips if necessary, and slip the audio by the smallest measured amount.

Use a clap, camera flash, hand impact, or a clear mouth movement as the reference. Zoom in on the timeline and find the waveform spike that corresponds to the event. If the sound occurs after the visual event, move the audio earlier; if it occurs before, move it later.

For a small constant offset:

1. Duplicate the timeline or save a project version.
2. Unlink the audio and video if they are linked.
3. Move the audio by the measured number of frames or samples.
4. Check the beginning, middle, and end of the recording.
5. Relink the clips after confirming the correction.

If the offset changes over time, do not apply one constant slip. Investigate sample-rate conversion, variable frame rate, separate recorder clocks, or a camera that changed frame rate during recording.

Can a sample-rate mismatch cause audio drift?

Short answer: different recording sample rates can contribute to a long-session sync problem, but first verify the actual media metadata and whether the issue is constant or cumulative.

Most video projects use 48 kHz production audio, while some music and voice workflows use 44.1 kHz. Resolve can often resample media, but a mismatch combined with a recorder or capture workflow can create problems. Check the clip’s audio attributes and the project’s audio settings before stretching anything.

If the first clap aligns but the final clap drifts, compare the durations of the camera recording and external audio. The correct fix may be a verified sample-rate conversion or a small time stretch applied to the duplicate audio file, not repeated frame-by-frame nudging.

Keep the original recording unchanged. Render a corrected working copy, then compare it with the source at multiple sync markers before replacing the production audio.

How do you fix sync drift from variable-frame-rate footage?

Short answer: transcode variable-frame-rate screen or phone recordings to a stable constant-frame-rate editing file before doing detailed sync work.

Variable-frame-rate media can report a nominal frame rate while changing its actual cadence during capture. This is common in phone recordings, screen captures, and some web downloads. The audio and video may align near the start and drift later even though neither track was manually moved.

Create a verified constant-frame-rate intermediate, preserve the original file, and replace the working clip in a duplicate timeline. Match the project frame rate and compare at several timecodes. If the recording includes a separate external audio source, sync the stable intermediate to that source using the original clap or waveform reference.

How do you sync separate camera and recorder tracks?

Short answer: use a common sync event when available, then check drift across the full duration before accepting the link.

The most reliable options are:

• a visible and audible clap;
• timecode recorded by both devices;
• waveform matching when the camera captured usable reference audio;
• a slate or repeated sync event in long recordings.

After the initial alignment, inspect more than the first minute. A camera and recorder can start together and slowly separate. Long interviews, concerts, and events need at least one midpoint and end check.

If the tracks are significantly different in duration, confirm that neither file was conformed to a different speed or frame rate before attempting a stretch. Make the smallest correction that preserves pitch and intelligibility.

How do you prevent audio delay before the next edit?

Short answer: record production audio at a known sample rate, capture a sync event, avoid Bluetooth for critical monitoring, and test the full workflow before recording a long session.

Use a checklist:

• set the camera and recorder to the intended production sample rate;
• capture a clap or slate at the beginning and end of a long take;
• check that both devices use the intended frame-rate convention;
• avoid changing speed settings after recording begins;
• label camera and recorder files consistently;
• test the first minute in Resolve before editing the entire session;
• preserve the original audio and camera files.

If the team uses Cutsio to transcribe interviews, remove silence, or prepare a rough cut, use it as a discovery and pre-edit layer. Confirm sync in the finishing NLE before mastering the final audio.

How do you repair sync drift in a long recording?

Short answer: confirm that the drift is real, measure it at multiple sync points, and correct a working copy only after checking frame rate, sample rate, and variable-frame-rate media.

Mark the first clear clap, a midpoint event, and the final sync event. If the first point is aligned but the last point is late, calculate the change across the full duration rather than applying the same frame offset everywhere. A small time stretch may be appropriate for a verified sample-rate or clock mismatch, but it should be applied to a duplicate file and checked for pitch or artifact changes.

If the camera or screen recording uses variable frame rate, create a constant-frame-rate intermediate first. If the external recorder and camera used different clocks, use the measured start and end difference to guide the correction. After the repair, check speech, music, and room tone at several points and keep the original files available for comparison.

When the recording contains multiple speakers or cameras, do not check only the host’s first sentence. Compare a guest response, a camera cut, and a section with music or room tone. A correction that fixes one track can expose a different delay on another. Save the repaired sync as a new timeline version, then export a short review file and listen outside Resolve before committing the correction to the master.

If the sync problem appears only after a particular edit, inspect the cut itself. A transition, speed change, compound clip, or retimed audio region can make the delay look like a recording problem. Temporarily remove the edit from a duplicate timeline and compare the underlying clips. Restore the creative treatment only after the underlying sync is correct.

FAQ

Why is audio delayed only when I wear Bluetooth headphones?

Short answer: the wireless monitoring path adds latency. Test with wired headphones or speakers before changing the timeline.

How do I know whether the delay is constant or drifting?

Short answer: compare a sync event at the beginning, middle, and end. The same offset indicates a constant slip; a growing offset indicates drift.

Should I stretch audio to fix drift?

Short answer: only after verifying sample rate, frame rate, and source duration. Stretch a working copy and check multiple sync points before delivery.

Does changing Resolve’s project sample rate fix an existing recording?

Short answer: not automatically. Project settings affect playback and processing; an existing mismatch may require verified conversion or replacement media.

Can I fix sync after exporting a review cut?

Short answer: yes, but correct the source timeline first and upload a new version so reviewers do not approve an out-of-sync file.