Audio and video tracks carry presentation timing so the player knows when to show or play each part. Bad timestamps, discontinuities or an implementation issue can cause drift or jumps even with complete data delivery. A fixed delay control cannot repair every timing defect. A useful report describes whether the error stays fixed, grows gradually or begins suddenly at one transition. Those patterns suggest different timing failures and help avoid using a global delay slider to conceal a fault that changes during the item.
Distinguish constant offset
A stable lag differs from increasing drift. Use a clear audiovisual cue at the opening and again several minutes later, keeping the output path unchanged. If the gap remains about the same, a fixed delay adjustment may be appropriate after checking its scope. If the gap grows, presentation clocks or source timing need a different investigation. Write down whether sound leads or lags rather than saying merely that it is off, since the direction matters when evaluating available correction controls.
Compare another source
One problematic asset can have malformed timing. Compare another item on the same client and, if practical, the affected item on a second supported client. A single asset failing at the same moment across clients may contain problematic timestamps or a transition issue. A single device failing across many assets points elsewhere in the playback or output chain. Neither comparison is absolute proof, but together they give a more useful starting point than repeatedly increasing the buffer without checking the pattern.
Report the moment
A reproducible timestamp helps an operator inspect the source. Record the media time of the first visible mismatch, how long playback had been running and whether seeking or restarting restores alignment. For a live feed, include a real-world time and time zone so the operator can find the relevant segment. Keep account tokens and private URLs out of the evidence. A short description of a visible clap, door close or spoken line is often sufficient to identify a repeatable synchronization cue.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
A programme jumps after a source transition and audio remains displaced from then onward. Sound and picture align until one programme boundary, then stay separated by a fixed amount. Reporting the boundary and the direction of the jump helps distinguish a discontinuity in track timing from a gradually growing clock mismatch or a permanent soundbar delay setting.
Questions about this topic
Does a bigger buffer fix all timestamps?
No. Buffering cannot reliably repair malformed or inconsistent presentation timing already present in the supplied tracks.
Can this happen in a local file?
Yes. It is not inherently a network fault. Stored files also contain timestamps, so the same class of issue can occur without internet delivery.
