A constant lip-sync error keeps sound ahead of or behind the picture by roughly the same amount. That is different from an offset that grows during the program.
Before adjusting a delay control, establish the direction, consistency and audio route.
Use a clear visible event
Spoken dialogue can work when mouth movement is easy to see. A legitimate sync test with an intended simultaneous flash and sound is more controlled. Avoid inferring timing from an edited action scene where the mix or cut can be deliberately offset.
Watch several moments. If the relationship remains similar, a fixed adjustment may be relevant. If it starts aligned and gradually diverges, one delay value may hide the problem briefly without addressing it.
Record the path: player, television, receiver or soundbar, and headphones if used. Picture processing and sound processing can add different delays. The same source can therefore need a different investigation after the connection route changes.
Read what the control actually does
Some settings delay sound, some affect another stage and some offer automatic compensation. Do not assume a plus sign always moves the relationship in the direction you expect. Read the manual, record the original value and make a small single change.
Replay the same moment after the change. Keep all other processing fixed. If the result worsens, restore the original rather than stacking another delay control elsewhere in the chain. Multiple compensations can make the setup difficult to understand.
| Question | Record |
|---|---|
| Which arrives first? | Sound or visible event |
| Is the error stable? | Several moments across playback |
| Where is sound routed? | Every component and connection |
| What changed? | One control, old value and new value |
Verify ordinary operation afterward
Check a new playback start, a seek and another familiar source. A correction may be specific to an application or input. Keep that scope in the log so that another program is not adjusted blindly to match a different route.
If no supported control can correct the observed direction, use a stable alternative path where available and report the limitation. Exact source, time and route information is more useful than a single claim that the television is slow.
- Use a clear event with an intended sound/picture relationship.
- Describe which side leads.
- Confirm the offset stays broadly constant.
- Change one documented timing value.
- Recheck starts, seeks and another source before keeping it.
Useful answers
Should I use one delay value for every app and input?
Only if the actual routes behave consistently. Test and record the scope rather than assuming it.
Is gradual drift the same as a constant lip-sync offset?
No. A growing error needs a different investigation from a stable timing difference.