Lip sync and audio delay in home cinema: fixing the setting nobody labels properly

Three frames. That's roughly the point where most people start noticing a mouth moving slightly ahead of or behind the words coming out of it — somewhere around 100 to 120 milliseconds, depending on the person and the content. Below that, you generally can't consciously pick it, but plenty of home cinema owners are living with far more than three frames of drift and blaming the streaming service, the disc, or "the way movies are mixed these days." It's almost never any of those things. It's a delay chain with too many links, and a setting that half the AVR manuals don't explain properly.
I get asked about this more than almost anything else in the digital front-end world, which tells me the industry hasn't solved a problem it insists it solved a decade ago. Bit-perfect audio playback is largely a settled argument. Lip sync in a full home cinema chain, with a processor, a projector, and sometimes a soundbar or wireless surrounds in the mix, is not settled at all. It just fails quietly, in a way that make people think their gear is broken when the actual fault is timing.
Where the delay actually comes from
Every device in the signal path adds processing time, and video processing is almost always slower than audio processing. A projector doing frame interpolation, HDR tone mapping, or scaling can add anywhere from one to several frames of latency before the image even reaches your eyes. Meanwhile the audio, especially if it's just being decoded and passed through an AVR without heavy DSP, arrives comparatively quickly. The result: sound leads picture.
Add a wireless surround system, a soundbar with virtual height processing, or an outboard Atmos processor doing object-based rendering, and you can stack additional audio-side delay too, sometimes cancelling out the video lag, sometimes compounding it depending on the combination. There's no universal rule for which direction you'll drift, which is exactly why "audio delay" as a fixed setting exists on nearly every AVR and processor, usually buried in an audio setup menu rather than anywhere near video settings, which is its own small design failure on the part of manufacturers.
The Denon AVR-X3800H (check price) — a receiver I've spent a fair bit of time with — buries its lip sync adjustment under Audio Setup rather than anywhere related to video processing, and I understand why from an engineering perspective (it genuinely is an audio-domain fix) but it's a terrible spot for it from a usability perspective. Most owners never find it unless a forum post tells them where to look.
The HDMI handshake problem nobody talks about
Here's the bit that trips people up. HDMI has a built-in mechanism for exactly this problem, defined in the HDMI specification as audio/video delay reporting, where a display is supposed to tell the source device how much processing delay it's adding so the source can compensate automatically. In practice, this works inconsistently. Some displays report accurate numbers. Some report nothing. Some report a number that was accurate for one picture mode and wildly wrong for another, because switching from a standard mode to a game mode or a motion-smoothing mode changes the display's internal latency, and very few consumer displays update that reported figure dynamically when you change modes mid-session.
This is particularly relevant for projection setups, which is where I see the worst of it. A projector like the Sony VPL-XW5000ES (check price) handles HDR tone mapping and image processing in ways that add measurable latency, and if you've got frame interpolation or a motion setting engaged for smoother panning, that number goes up further. If your AVR trusted the HDMI-reported delay when you were in a low-latency picture mode, and you later switched to a smoother, more processed mode for a film, your sync just quietly drifted and the AVR has no idea because it never re-polled the display.
The honest fix, and the one I actually recommend over trusting automatic HDMI negotiation, is to set audio delay manually and by ear, then leave it alone unless you change picture modes. It's less elegant than "the spec handles it," but the spec handling it depends on manufacturers implementing the reporting correctly and consistently, and that's not guaranteed. If you want the technical detail on how the audio/video sync mechanism is meant to work, HDMI Licensing Administrator's own specification documentation covers it, though it's dense reading.
Doing the manual adjustment properly
Most AVRs and processors offer lip sync delay in a range from zero up to somewhere around 200 milliseconds, adjustable in small increments, sometimes as fine as 1ms steps. The process that actually works is unglamorous: play a scene with clear dialogue and clean lip movement — a news broadcast, a talking-head interview scene, anything with a static camera on a face — and nudge the delay up or down in small steps until the drift disappears. Do this at the end of your whole calibration chain, after speaker levels and subwoofer settings are dialled in, because there's no point tuning sync before your system is even configured correctly.
A trick that's saved me time more than once: don't try to spot sync on fast dialogue or a wide shot. Use a scene where a single face fills a decent chunk of the frame and speaks slowly. Sync errors are far easier to hear on plosive consonants — hard "p" and "b" sounds — because the visual mouth closure is sharp and unmistakable, so a small drift becomes obvious rather than subliminal.
If you're running an outboard processor and separate amps in a proper theatre build, the delay chain gets a layer more complex again, because you may have DSP happening in more than one box. This is one of the reasons a genuinely built-out room, the kind covered in Building a home cinema: the core components, benefits from a single point of lip sync control rather than trying to split the adjustment across multiple devices. Pick one device in the chain, set the delay there, and treat everything else as fixed latency you're compensating around.
Wireless surrounds and soundbars complicate this further
Wireless rear speakers, common in a lot of soundbar-based and even some AVR-based Atmos setups, introduce their own transmission delay on top of everything else, and it's rarely trivial. I've measured wireless surround kits adding 20 to 40ms of extra delay compared to a wired rear channel on the same processor, which doesn't sound like much until you're already sitting on a HDMI-induced video lag and it stacks. Most receivers handle inter-speaker delay (the surrounds arriving in time relative to the front channels) separately from overall audio-to-video delay, and conflating the two is a common troubleshooting mistake. If your surrounds sound out of time with your fronts, that's a distance/delay calibration issue, usually handled by the AVR's room correction routine. If your whole soundtrack is out of time with the picture, that's the separate lip sync setting. Different problems, different menus, and fixing one won't touch the other.
Streaming apps add their own variable
If you're watching via a smart TV app rather than a dedicated source device, you've added another unpredictable layer, because the app's own decode and buffer pipeline has latency that can shift between a software update on the TV and the next. I've seen sync drift appear on a system that was previously fine, purely because a TV's built-in streaming app got an update that changed its internal buffering. This is one of the more annoying multiroom-adjacent problems, related to but distinct from the resampling issues covered in the best DACs and network streamers — it's not a sample rate problem, it's a timing problem, but the symptom of "something's not right and I can't explain why" feels similar to the listener.
My honestly slightly contrarian take here: I don't think AVR manufacturers should ever have let HDMI's automatic delay reporting become the default, invisible-to-the-user assumption. It works often enough that people assume it's solved, and then it silently breaks the moment they change a picture mode or update a TV's firmware, and there's no indicator telling them why. A visible, simple manual override should be the first thing in setup, not a buried menu item under Audio Setup that most owners never find.
A quick diagnostic order that actually works
When someone tells me their system has developed a sync problem, I ask them to check things in a specific order rather than guessing. First, confirm the picture mode hasn't changed — motion smoothing and HDR tone mapping settings are the most common silent culprits. Second, check whether the fault exists on a wired disc source as well as streaming; if it's disc-only or streaming-only, the fault sits in that specific pipeline, not in the AVR's delay setting. Third, if it's present everywhere, go straight to the manual lip sync adjustment rather than fighting with HDMI settings or firmware updates that may not fix anything.
I was setting up a mate's room in Fortitude Valley a few months back — new projector, same old AVR — and the sync was out by what felt like a good 80ms after he'd switched the projector into its smoother motion mode for sport. Took about four minutes to walk him through the manual dialogue-scene test and dial it back in. He'd been living with it for weeks assuming it was a "streaming thing." It wasn't. It was a menu he'd never opened.
Get the delay chain sorted once, note the number down somewhere (a phone note works fine), and you've got a reference point for next time you change a display mode or add a device to the chain. It's not glamorous work, but it's the difference between a system that just works and one that quietly annoys you every single session without you being able to say exactly why.
Common questions
- Why does my TV app sometimes have sync but my Blu-ray player doesn't, on the same AVR?
- Each source has its own decode and buffer pipeline, so latency isn't fixed across your whole system. A firmware update to a smart TV's streaming app, for instance, can change its internal buffering without touching your disc player at all. Check each source separately rather than assuming one delay setting fixes everything.
- Should I trust my AVR's automatic HDMI lip sync correction?
- It's worth trying first since it costs nothing, but don't assume it's permanently correct. It relies on your display accurately reporting its processing delay, and that figure often doesn't update when you switch picture modes like motion smoothing or HDR tone mapping. A manual check after any display setting change is the safer habit.
- Does adding wireless surround speakers cause lip sync problems?
- It causes a related but separate issue. Wireless surrounds add transmission delay relative to your wired front channels, which affects inter-speaker timing, not overall audio-to-video sync. Your AVR's speaker distance and room correction routine handles that separately from the lip sync delay setting.
- How much delay adjustment is normal on a modern AVR or processor?
- Most units offer somewhere between 0 and roughly 200 milliseconds of adjustable delay, in small increments. Needing 60 to 100ms of correction isn't unusual, particularly with a projector doing heavy image processing or HDR tone mapping.
Theo here. By day I write software, by night I argue with people on forums about whether bit-perfect playback is "solved" (it mostly is, and then it isn't). I cover the digital end — DACs, streamers, servers, the whole messy ecosystem of getting a file to sound its best. My promise to you: I'll separate the genuine engineering from the audiophile folklore, and I'll never tell you a $500 streaming bridge sounds "blacker" unless I can explain why.
Software engineer; network-audio and DAC specialist
More from Theo Mensah
Dongle DAC power limits: when a phone can't drive headphonesDongle DACs are brilliant until they aren't. Here's how to work out whether your phone-and-dongle rig actually has the current to drive your headphones.
DNS and multiroom: why your streamer drops out at the worst timeMultiroom dropouts are rarely your Wi-Fi. Here's why DNS resolution quietly breaks streaming apps, and how to fix it for good.
Parallel vs series IEM crossovers: why multi-driver in-ears sound so differentWhy do two IEMs with the same driver count sound nothing alike? The crossover topology is doing more work than the drivers themselves.
Streaming a subwoofer's EQ filters: why your network player might be the bottleneckYour sub's miniDSP or app-based EQ can only act on a signal your streamer hasn't already mangled. Here's where network audio and bass management actually interact.
Amplifier gain structure: the setting that decides your noise floorGain mismatches between DAC, preamp and power stage quietly wreck dynamic range. Here's how to actually set gain structure instead of guessing at the volume knob.
Bass management by the numbers: what your AVR's crossover and slope actually doCrossover frequency gets all the attention, but slope, distance settings and speaker size flags quietly decide whether your bass management works or fights itself.