Bluetooth Headset A/V Sync Issues and Fixes for Streamers

Bluetooth Headset A/V Sync: Measure and Fix Codec Delay for Streaming

Measure Bluetooth headset sync with the headset in the same state it uses while you stream. Bluetooth headsets add codec and profile delay to the audio path before the microphone signal reaches your streaming software. Bluetooth audio latency can be much lower with LC3 at about 20 to 30 ms or aptX Low Latency at about 40 ms, while SBC commonly sits around 150 ms when both sides support it.¹²

The profile matters as much as the codec. On Windows, opening a Bluetooth microphone can make the OS select HFP instead of A2DP, which changes the audio path and can change the measured sync offset.³ Your webcam still adds its own video pipeline delay, commonly measured in the same 60 to 100 ms range as other USB camera paths.⁴ The total A/V offset your viewers experience is the sum of those audio and video path delays, because total latency is the accumulated delay across each stage in the capture and render chain.

For most streamers, the combination of Bluetooth headset delay and webcam video delay produces a total offset between +120 and +300 ms. That is large enough to be clearly audible as lip-sync desync at any volume. Measuring the combined offset with the 5-clap test gives you one number to enter in OBS regardless of the individual contributions from each device. You do not need to know your Bluetooth codec delay separately.

How Bluetooth codec and profile delay affects A/V sync

Inside a Bluetooth headset's wireless audio path, audio samples leave the microphone, pass through the headset's audio profile, get encoded or packetized for transmission, decode at the receiving end, and then enter the OS audio stack. A2DP playback can use SBC, AAC, aptX, aptX Adaptive, or LDAC depending on support; LE Audio can use LC3; and HFP handles microphone capture and communications audio.⁵ Every stage adds latency, and the profile switch can matter more than the headline codec name.

SBC is the mandatory baseline for A2DP, so it is the fallback most pairs can use. Echobox lists SBC at about 150 ms, AAC and LDAC at about 200 ms, aptX at about 70 ms, aptX Adaptive at about 50 to 80 ms, and LC3 at about 20 to 30 ms.¹ Qualcomm's aptX Low Latency page lists approximately 40 ms latency for aptX Low Latency, which explains why compatible low-latency pairs can measure much smaller offsets than SBC or AAC pairs.²

Because the Bluetooth delay adds on top of webcam video delay, a normal positive webcam offset can become a larger positive offset. A setup that looks fine with a wired USB microphone can look late as soon as the headset microphone enters HFP mode. The 5-clap test measures the result that actually reaches the browser, not the theoretical codec number from a spec sheet.⁴

Why the total offset matters more than codec math

The 5-clap test measures the combined audio and video path that reaches the browser, so it is more useful than adding codec numbers by hand. OBS only needs the total offset for the headset microphone source you measured. Trying to calculate the delay from individual codec specifications ignores the OS audio stack, driver buffering, and webcam processing stages that also contribute to the final gap. A single measured value captures all of those stages at once, which is why the five-clap result is the number that actually fixes the problem in your stream output.

Entering the total in OBS once is simpler than chasing each contribution separately. If you later swap codecs through a headset app, the measured number already accounts for the new path, so you only re-measure rather than re-derive codec math. That single value is what keeps the stream output aligned, because OBS applies one correction to the headset microphone source regardless of how the delay was built up.

Measuring the combined offset

Run the 5-clap test with your Bluetooth headset microphone selected in the audio input dropdown and your webcam in the video input dropdown. The test does not separate Bluetooth codec delay, HFP profile delay, and webcam video delay; it measures the total gap between audio and video as both arrive in the browser. This combined measurement is exactly what you need for OBS.

Before testing, check whether your OS or headset app reports the active Bluetooth profile or codec. Windows documents that it selects HFP when an application opens the microphone input, and that A2DP and HFP behavior depends on the Windows version, headset capabilities, and radio support.³ If you cannot see the active profile, treat the measured value as authoritative and do not guess from codec charts.

Testing in the exact Bluetooth profile you stream with

A2DP and HFP are different Bluetooth audio paths, not just two names for the same connection. A2DP is high-quality stereo playback, while HFP provides mono capture and playback for microphone use.⁵ If your headset reconnects, your OS updates Bluetooth policy, or your streaming app opens the mic, the active path can change. Re-run the five-clap test in the same profile you use during streaming so the OBS offset reflects the production path instead of the listening-only path.

Fixing and maintaining Bluetooth A/V sync

After measuring, enter the total offset in OBS Advanced Audio Properties for your Bluetooth headset microphone source. StreamShark documents the OBS workflow as Audio Mixer gear > Advanced Audio Properties > Sync Offset (ms), where the value delays an audio source in milliseconds.⁶ If you monitor audio live through OBS, verify the correction in a recording or stream output, because OBS forum troubleshooting notes that sync offset may affect output encoding without changing monitor audio in some configurations.⁷ Because Bluetooth codec and profile delay can add substantial latency compared to wired USB microphones, a Bluetooth headset often needs a larger correction than a wired mic, commonly in the 100 to 280 ms range when paired with a normal USB webcam.⁸

Building on this, re-measure whenever the headset reconnects in a different Bluetooth profile. Codec latency can differ sharply between SBC, AAC, aptX variants, and LC3.⁸ If the offset changes, replace the old OBS value with the new measured value rather than adding a second correction on top of it.

Switching to a wired USB microphone is the most reliable fix for streams where Bluetooth profile switching causes variable sync. A wired microphone eliminates Bluetooth codec and HFP variability, while an audio interface with direct monitoring gives you a low-latency headphone path for the mic input. SSL's SSL 2 MKII guide describes the MIX control as a low-latency monitor path that lets you hear connected inputs before they pass into the computer, with input-to-output latency under 1 ms.⁹ The trade-off is losing wireless convenience, but the sync calibration becomes much more stable.

When Bluetooth profile switching makes calibration unstable

If your headset changes profile between sessions, the offset can jump even when the camera stays the same. A2DP, HFP, SBC, AAC, aptX, and LC3 are not interchangeable paths; they change the audio-side delay before OBS applies any correction. When the headset cannot stay in one profile, the stable fix is a wired USB microphone or an audio interface with direct monitoring so the sync value no longer depends on Bluetooth behavior.

When to use this

Why Windows switches your headset to HFP mode matters when you use a Bluetooth headset or wireless microphone as your streaming audio source, when you notice larger-than-expected sync gaps a standard USB microphone measurement does not explain, or when your headset reconnects in a different Bluetooth profile and your previously calibrated sync seems off.

Examples