Why Does OBS Audio Drift Out of Sync by the End of the Sermon?

The short answer: a fixed offset is a delay — growing desync is a clock

There are two audio-sync problems and churches routinely fix the wrong one. A stream that’s consistently off by the same amount all service has a delay — solved once with a sync offset, covered in our audio delay guide. But a stream that starts in sync at the call to worship and is lip-flappingly wrong by the closing prayer has drift — and no offset can fix it, because the error is growing. Set it right at 9:05 and it’s wrong again by 9:40.

Drift means two clocks in your chain disagree about how long a second is. Tiny disagreement, compounding every minute, across the longest continuous audio sessions in amateur production — because a 75-minute church service gives drift more runway than almost any other streaming use case. Here’s where the disagreement lives and how to end it.

Culprit 1: the sample-rate mismatch (fix this first)

The classic: your audio interface or console USB output runs at 44.1kHz while OBS runs at 48kHz — or vice versa, or Windows quietly set one device differently from another. Every mismatch forces continuous resampling, and resampling under real-world load is where sync goes to die slowly.

The audit takes ten minutes. Pick one rate — 48kHz is the video-world standard — and set it in all three places: OBS (Settings → Audio → Sample Rate), the audio device itself (its control panel or the console’s USB settings), and Windows (Sound settings → each device → Advanced, where per-device rates hide). Then restart OBS so everything renegotiates. One rate, everywhere, no exceptions — including the spare USB mic someone plugs in for the testimony.

This single audit resolves the majority of church drift complaints. Two more culprits cover the rest.

Culprit 2: the USB clock that runs slightly wrong

Every audio interface keeps time with its own hardware clock, and inexpensive USB devices can run measurably fast or slow — not enough to hear in a three-minute video, plenty across a full service. The fingerprint: drift that persists after the sample-rate audit, always in the same direction, roughly proportional to service length, and tied to one specific device.

The honest fixes: try a different USB port (controller contention is real), take the console’s feed by a different path if one exists, and — if a budget interface drifts every single week — that device is telling you it’s the weak link in a chain your whole stream depends on. This is a case where the budget conversation has data behind it.

Culprit 3: the overloaded machine dropping audio buffers

Sometimes the audio chain is innocent and the computer is the bad clock: a CPU or encoder running out of headroom starts dropping audio buffers, and every dropped buffer is a few milliseconds of desync that never comes back. The fingerprint is diagnostic gold: drift that only appears on busy Sundays — the full-band weeks, the Christmas service — and worsens late, exactly tracking the 40-minutes-in resource story.

This is where guessing ends and telemetry earns its keep: Tech Manager samples CPU, encoder load, and memory every five seconds, so the health report shows whether load was climbing while the sync slid. If it was, you don’t have an audio problem — you have an overload problem wearing an audio costume, and the fixes are the encoder ones: hardware encoding, a lighter preset, 720p.

Why drift haunts churches specifically — and what ends it for good

Drift is the perfect church-booth failure: invisible at the top of the service, unmissable by the end, gone by the time anyone investigates Monday, and dependent on which volunteer plugged in what. Which is why the booths that never fight it twice share the same structure this whole series keeps arriving at — a settings baseline so sample rates can’t silently diverge between operators (the whodunit fix), telemetry so busy-Sunday overload is a chart instead of a vibe, and an audio seat someone actually owns — the ears, often a student who will catch drift at minute five that a busy solo operator wouldn’t notice until the sermon.

Run the ten-minute audit this week. Then give the audio chain an owner, and drift joins the list of problems your booth used to have.

Better livestream audio: Why your church livestream sounds bad, and how a separate stream mix fixes it. See also the three classic livestream audio problems · getting the sound board into OBS, vMix, or an ATEM.