Your stream or recording looks great in the preview window, but when you play it back, the gunshots land a half-second after the muzzle flash. Or the commentary track drifts further behind the gameplay the longer the recording runs. Sometimes it’s the opposite — audio arrives early. Either way, it makes the footage nearly unusable for uploads, and it’s one of the most common complaints among Elgato, AVerMedia, and generic HDMI capture card owners.
The good news: this is almost never a defective card. Audio desync in captures comes from mismatched buffer settings, sample rate conflicts between Windows and your capture software, GPU encoder lag, or a simple chain-of-devices problem. Most fixes take under ten minutes and involve settings menus rather than new hardware. Work through the fixes below in order — they’re sorted from quickest to most involved — and in the vast majority of cases you’ll be done by fix three or four. If you’re chasing this issue ahead of a big stream or upload schedule in 2026, don’t panic-buy a new card yet.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Windows and capture software disagree on sample rate | Check Settings > System > Sound > Properties against the capture device’s format setting; if one says 48,000 Hz and the other says 44,100 Hz, that’s your problem | Easy |
| Audio offset in OBS/Streamlabs is set incorrectly | In OBS, open Tools > Advanced Audio Properties and look at the Sync Offset column — anything other than 0 ms you didn’t set yourself is suspect | Easy |
| Capture software audio buffering too high or too low | Desync is constant across the whole recording (not drifting), typically 100–500 ms | Easy to medium |
| Game audio processing (surround virtualization, EQ software) adds latency | Desync only affects game/desktop audio, not microphone; check if SteelSeries Sonar, Dolby Atmos, Nahimic, or DTS Sound Unbound is running | Medium |
| Encoder overload causing audio/video pipeline drift | Desync grows worse the longer the recording runs; OBS stats dock shows skipped frames or render lag | Medium |
| HDMI handshake or passthrough chain delay | Desync appears only when a console or passthrough TV is in the chain; direct connections are fine | Medium to hard |
Fix 1: Set a Manual Audio Sync Offset in OBS
What causes it
Capture devices process audio and video through different pipelines. Video goes through the HDMI capture chip, while audio may take a slightly different path through the card’s internal buffer. The result is a constant offset — usually the audio arriving 50 to 400 milliseconds late.
How to check
Record a 30-second clip of gameplay with a sharp, repeated audio event — clapping once per second into your mic works, or a game with consistent gunshot sounds. Watch the clip and note roughly how many milliseconds the audio lags or leads. Frame-by-frame stepping (pause and press the period key in VLC) helps you count frames at 60 fps, where each frame is about 16.7 ms.
What to do
In OBS Studio, open Tools > Advanced Audio Properties. Find your capture card’s audio source in the list. In the Sync Offset column, enter a positive value to delay audio or a negative value to advance it. If audio lags video by 150 ms, enter -150 ms. Click Apply, then record another test clip. Adjust in 20–50 ms steps until it lines up. Streamlabs users: go to Settings > Audio > Advanced, or right-click the audio source in the mixer, select Advanced Audio Properties, and use the same Sync Offset field.
How to undo it
Return to Advanced Audio Properties and set the Sync Offset back to 0 ms, then click Apply.
Fix 2: Match Sample Rates Across Windows and Capture Software
What causes it
When Windows outputs audio at one sample rate and your capture card records at another, the software resamples on the fly. Resampling introduces small delays and, in longer recordings, audible drift where audio slips progressively out of alignment.
How to check
Right-click the speaker icon in the system tray, choose Sound settings, scroll to Advanced > All sound devices, select your output device, and check the format under Properties — typically 24-bit, 48000 Hz. Then open your capture software’s device properties (in OBS: right-click your capture card source > Properties, or Settings > Audio for the global sample rate, which should read 48 kHz).
What to do
Set everything to 48,000 Hz. In OBS, Settings > Audio > Sample Rate: choose 48 kHz. In Windows, set your playback and recording devices to 24-bit or 16-bit, 48000 Hz. If you use a USB microphone, open its own properties under Settings > System > Sound > All sound devices and confirm it’s also at 48 kHz. Restart OBS after changing any rate.
How to undo it
Reopen the same properties windows and restore your previous sample rate selections.
Fix 3: Disable Audio Enhancements and Spatial Sound
What causes it
Audio processing software — Windows Sonic, Dolby Atmos for Headphones, DTS Sound Unbound, Nahimic, SteelSeries Sonar, and motherboard vendor EQ tools — inserts a processing buffer between the game and your capture software. That buffer delays the audio path by 50–200 ms.
How to check
Settings > System > Sound > your output device > Properties. If a “Spatial sound” dropdown shows anything other than Off, that’s active processing. Also check your system tray for Nahimic, Sonar, or similar utility icons.
What to do
Set Spatial sound to Off for your playback device. Close or uninstall third-party audio suites, or at minimum disable their processing effects. If you capture desktop audio through a device like the Elgato Wave Link or Voicemeeter, check its own routing for inserted effects and disable them. Re-record a test clip afterward.
How to undo it
Return to the Spatial sound dropdown and reselect your preferred format, and relaunch your audio utility.
Fix 4: Lower the Capture Device Buffer and Audio Buffering Settings
What causes it
Capture software buffers incoming AV data to smooth out USB hiccups. A buffer that’s too large delays audio; one that’s too small causes dropouts that the software patches with silence, producing skew.
How to check
In OBS, open your capture card source’s Properties. On Elgato devices, look for the “Audio Input Device” and buffering options; on UVC-based generic cards, check for an “Activate/deactivate buffering” or latency preset (typically labeled Low / Normal / High).
What to do
Set the device latency or buffering to its lowest stable setting. For Elgato 4K-capable cards in 4K Capture Utility, check Settings > Device for an audio delay compensation option and enable it. In OBS with UVC devices, toggle the buffering option off, test, then back on, and keep whichever yields sync. Also make sure the card is plugged into a USB 3.0 or faster port directly on the motherboard rear I/O — front-panel or hub connections amplify buffering problems.
How to undo it
Reopen the source Properties and restore the previous latency or buffering preset.
Fix 5: Reduce Encoder Load
What causes it
If your GPU or CPU can’t keep up with encoding, video frames get dropped or delayed while the audio track stays continuous. The result is drift that worsens over a session — a recording that starts in sync and ends seconds off.
How to check
In OBS, enable View > Docks > Stats. Watch for “Skipped frames due to encoding lag” above 1–2%, or “Render lag” climbing. Also check Task Manager’s GPU tab while recording — sustained 100% 3D/Video Encode usage indicates overload.
What to do
In OBS Settings > Output, switch the encoder from x264 to your GPU’s hardware encoder (NVENC, AMD HW H.264/AVC, or QuickSync). Lower the preset one notch (e.g., NVENC from P7 to P6/P5). Drop your recording resolution or framerate one step (1440p to 1080p, or 60 to 30 fps) as a diagnostic — if drift stops, load was the cause, and you can tune from there. Close background apps using the GPU, especially browsers with hardware acceleration.
How to undo it
Reopen Settings > Output and restore your previous encoder, preset, and resolution values.
Fix 6: Simplify the HDMI Chain
What causes it
Every device between your console or PC and the capture card — AVR receivers, passthrough TVs, HDMI switches, adapters — adds processing to the video signal, often far more than to the audio path. TVs in particular apply image processing that delays video by one to three frames.
How to check
Connect the source directly to the capture card, bypassing any receiver, switch, or passthrough TV. Record a test clip and compare sync to your normal setup.
What to do
Run the source directly into the capture card’s HDMI in. If you need display output, use the card’s HDMI passthrough to a monitor, not a TV with heavy processing. On the TV/monitor, enable its Game mode or lowest-latency picture mode. Replace long or old HDMI cables with certified High Speed or Ultra High Speed cables under 3 meters. Avoid HDMI-to-DVI adapters and cheap switchers in the capture path.
How to undo it
Reconnect your devices in the original arrangement and restore the display’s prior picture mode.
Fix 7: Update or Roll Back the Capture Driver and Firmware
What causes it
A driver mismatch after a Windows update can change how the card timestamps audio versus video. Conversely, a brand-new driver may introduce a regression that an older version didn’t have.
How to check
Open Device Manager (right-click Start > Device Manager), expand “Sound, video and game controllers” or “Cameras,” and find your capture card. Note whether it’s using a vendor driver or a generic “USB Video Device” driver. Check the manufacturer’s support page for firmware utilities — Elgato, AVerMedia, and Mirabox all ship updater tools.
What to do
Install the latest firmware and driver package from the manufacturer’s support site, reboot, and re-test. If the desync started immediately after a driver update, use Device Manager > right-click the device > Properties > Driver tab > Roll Back Driver, or uninstall and reinstall a prior version you downloaded yourself.
How to undo it
Reinstall the previous driver version from the manufacturer’s archived downloads, or use the Roll Back Driver button.
Fix 8: Fix It in Post with a Constant Delay
What causes it
Not a hardware cause at all — this is the fallback when hardware-side fixes don’t fully eliminate a constant offset. Editing software can shift the audio track to match, which is lossless in quality terms.
How to check
This only works if the desync is constant from start to finish. Play the beginning and the end of your recording: if the offset is the same number of frames at both points, a post fix will work. If it drifts, revisit Fixes 2 and 5 instead.
What to do
In DaVinci Resolve (free), import the clip, right-click the audio in the timeline, and change the clip’s audio offset, or simply drag the audio track left or right until a visual landmark (muzzle flash, jump landing) matches its sound. In Shotcut, use Properties > Audio > Start delay in milliseconds. In HandBrake you can’t shift audio, but in ffmpeg you can run: ffmpeg -i input.mp4 -itsoffset 0.15 -i input.mp4 -map 0:v -map 1:a -c copy fixed.mp4 — adjust the 0.15 value (in seconds) to your measured offset, using a negative value if audio leads video.
How to undo it
Re-export from the original, unshifted source file, or restore the audio track’s original position in your editor’s timeline.
If Nothing Works
If the desync drifts (rather than staying constant) even at low encoder load with matched sample rates, test the capture card in a second computer. Persistent drift on two machines strongly suggests a failing card or an underpowered USB controller — try a dedicated PCIe USB expansion card or a different chipset port. For live streaming where you can’t tolerate residual offset, route all game audio through OBS and monitor via headphones plugged into your PC rather than the passthrough path, so viewers hear exactly what OBS hears. And as a last resort, a replacement from a manufacturer with strong driver support is cheaper than hours of lost recording time — but exhaust the fixes above first, because in most cases the card was never the problem.
FAQ
Why is my capture card audio ahead of the video instead of behind?
Audio arriving early usually means the video path is delayed — typically by HDMI chain processing (Fix 6) or a large capture buffer (Fix 4). Use a negative sync offset in Advanced Audio Properties to pull audio back if needed.
Does audio desync affect my live stream or only recordings?
Both. Whatever OBS outputs — recording or stream — uses the same audio pipeline, so a sync offset in Advanced Audio Properties corrects the live feed as well as saved files. Test on a private stream key before going live.
Why does the desync get worse the longer I record?
Progressive drift points to a sample rate mismatch (Fix 2) or encoder overload (Fix 5). A constant offset that never changes points to buffering or HDMI path delay instead. Identifying constant versus drifting tells you which fix to apply.
Do I need a different HDMI cable to fix audio delay?
Usually no — cables rarely cause audio-specific delay. But damaged, very long, or non-certified cables can force the capture device into a fallback mode with extra buffering. Try a short, certified cable as a cheap diagnostic before blaming the card.
