Friday, October 9, 2026
Soundbar Audio Delay: Which Device Should Wait?
A newsreader's lips close on a hard "p", and the sound lands a beat later. Or a beat earlier, which is worse. You open the menus and find two sliders, one on the TV and one on the soundbar, and a question nobody answers on the box: which device should wait? Soundbar audio delay is rarely a fault. It is two machines disagreeing about time, and the fix depends on which one is running ahead.
Key Takeaways
The signal that runs ahead waits: delay the sound once when voices come early, and cut processing when they come late.
- Viewers spot early sound far sooner than late sound, so never push audio ahead to compensate.
- Use one delay control, ideally the soundbar's, and leave the other at zero.
- Bluetooth and compressed optical links run late before you touch anything; a wire or PCM output fixes more than a slider.
- HDMI 2.2's new sync protocol is a reason to check your next TV's spec sheet, not to replace a working bar.
Why does soundbar audio delay happen at all?
Voices drift because the picture and the sound take different routes, and every box on the sound route, from the TV's audio output to the soundbar's decoder, adds its own processing time. The picture is not innocent either. Motion smoothing and upscaling hold the image back while the sound leaves early, so a quick bar under a heavily processed picture puts voices ahead of lips. A slow bar puts them behind. Same symptom, opposite fixes. Even picture modes move it: the Filmmaker Mode settings we looked at recently strip most of that processing, and sync shifts with them.
Direction matters more than size. ITU-R BT.1359, the broadcast recommendation from 1998 that is still in force, found viewers detect sound arriving 45 ms early but only notice late sound at 125 ms. A bar running slightly late can pass unnoticed for years; one running slightly early looks wrong from the first sentence. Thunder follows lightning, never the reverse. This is the most useful number in home AV, and almost nobody quotes it.
Four numbers settle most living-room cases. RTINGS, in a January 2024 study built on 500 latency measurements, found a soundbar's ARC or eARC link often syncs worse than plugging the source into the bar, and that one sound-effects setting added 30 ms. Its headphone test puts typical Bluetooth SBC latency at 150 to 250 ms (as of 2023). Voice modes are processing too, worth knowing if you lean on the dialogue enhancement modes on TVs and soundbars.
Typical Bluetooth SBC Lag
150-250 ms
Late before any setting
RTINGS Latency Measurements
500
ARC drift is common
Cost of Most Fixes
$0
A menu, not a cable
Late vs Early Tolerance
2.8x
Err late, never early
The Bluetooth figure rules options out. A standard SBC link is past the late limit before you open a menu, and a delay slider can only make the early signal wait; it cannot pull late sound forward. The tolerance ratio is our own division of the ITU thresholds.
Your eyes forgive late sound almost three times longer than early sound. Every sync decision follows from that.
Should you set the delay on the TV or the soundbar?
Set it on one device only, preferably the soundbar because it sits last before your ears and sees every input, and use the TV's AV sync setting only when the bar has no delay control of its own. Two stacked delays is the classic mistake. Broadcasters may already hand you a signal out of step, so the table starts with the slack you inherit; its headroom rows are our arithmetic from ITU-R BT.1359 and the EBU's R37.
| Category | Detail | What it means |
|---|---|---|
| ⚖️ Broadcast slack | EBU R37: up to 40 ms early or 60 ms late | ⚠️ Part of the error arrives pre-made |
| ⏱ Early headroom | About 5 ms if a show arrives early | ❌ Any audio advance gets seen |
| ⏱ Late headroom | About 65 ms for every box at home | ✅ A small lag passes unnoticed |
| 🔋 ARC vs HDMI-In | LG S95QR: 65 ms on ARC, near 0 ms on HDMI-In | ✅ Plugging the source into the bar helps |
| 🔋 Optical, Dolby | RTINGS: lag on the order of 300 ms when compressed | ❌ Switch the TV output to PCM first |
| 🔋 Bluetooth bar | Standard SBC alone exceeds the late limit | ❌ No slider can rescue this link |
| 🏁 Who waits | Early voices: the sound waits Late voices: cut processing |
🏁 Delay once; never push sound ahead |
Read the ARC row against the late-headroom row. That single measured hop, if it runs late, spends the whole home margin by itself. RTINGS found bars closer to perfect sync with the source in the soundbar's HDMI input, so a cable move can beat a settings hunt.
If you are unsure which way to nudge the delay, leave the sound slightly late, because nearly three quarters of the noticeable sync window sits on the late side. Derived from the ITU-R BT.1359 detection thresholds quoted above, summed into one window and split by direction.
Does eARC fix lip sync, and where does it still break?
eARC can carry automatic lip-sync data, a feature HDMI first added in version 1.3, but it only works when both devices report their delays honestly, and plenty of chains still drift on particular apps and picture modes.
The real fix is newer. The HDMI Licensing Administrator released HDMI 2.2 in June 2025 with a Latency Indication Protocol, aimed at chains with a soundbar or receiver in the middle, so each device can report its delay. Both ends need it. Exact figures are still being studied, but early indicators suggest it reaches new TVs and bars long before the ones on your wall, so check for it on your next purchase rather than retiring a bar that works.
Picture modes are the other trap. Game mode strips video processing, which makes the picture faster and leaves the sound relatively late, so a delay tuned in Movie mode drifts when a console wakes the TV. The same goes for separate day and night presets, the sort people set up to fight glare in a bright living room: check sync in each one.
- Drift in one streaming app only: leave the global delay alone.
- Optical with Dolby: PCM output cuts decoding time but drops surround formats.
- Both sliders set: zero one of them before judging the other.
Before you touch a slider, check these against your own setup
- Sound arrives before the lips close, on every input: delay it once on the bar.
- Sound trails the lips and the bar uses Bluetooth or optical: change the link.
- Drift on one console only: fix it at that source.
- Your TV and bar both carry an HDMI 2.2 logo: let them sort it out first.
So, which device should wait? Whichever signal is ahead: one delay on the soundbar for early voices, less processing for late ones. This week, put on a newsreader, zero both sliders and watch lips close on a "p": delay early sound in small steps until it stops bothering you, and give late sound a different cable instead.