Drift means the sound-picture gap grows or changes during playback. It can involve source timestamps, clock handling or a decoder path. A fixed offset may align the start but become wrong later, so record when drift begins and whether seeking resets it. Compare early and late synchronization with the same output settings, and note whether a seek restores alignment. Those observations distinguish continuing rate drift from one abrupt offset and give support a more useful timeline than a single approximate delay value.
Compare another source
One asset can have faulty timing. Play another known working item for a similar duration on the same output path. If only one asset drifts, inspect its edition and track selection before changing system-wide audio settings. If many unrelated items drift after comparable elapsed time, the client or common output route deserves attention. A second supported client can add evidence, but keep the media rendition and audio track consistent so different source timing does not undermine the comparison.
Distinguish interruption jumps
A sudden offset after a transition differs from gradual drift. Record whether the gap grows smoothly or appears suddenly after an advert, seek, pause or format change. A sudden jump can remain fixed afterwards and may be a discontinuity rather than continuing clock drift. Watch whether a restart resets the gap to zero and how quickly it returns. These patterns matter because a one-time delay adjustment can help a fixed offset but will progressively lose accuracy if the two tracks keep diverging.
Report elapsed time
Support needs the point and duration, not only out of sync. For recorded material, include both the scene timestamp and how long the current playback session had been running. Seeking straight to the same scene may not reproduce a problem that depends on uninterrupted elapsed time. For a live source, add real-world time and time zone. Describe the first and later lead or lag direction, selected audio track and whether seeking resets the issue, while keeping private account addresses out of the report.
A practical sequence
- Check an early and late cue
- Compare an equally long control item
- Note gradual versus sudden change
- Report elapsed time and seek recovery
An example
Dialogue begins aligned, becomes late after twenty minutes, and realigns after reopening the stream. The opening is aligned, the gap grows over twenty minutes, and seeking briefly restores sync before the gap returns. This pattern is different from a permanent Bluetooth offset and gives support a reason to investigate ongoing timestamp or clock handling rather than repeatedly enlarging a fixed delay.
Questions about this topic
Can a fixed delay repair this permanently?
Not if the offset continues changing. It can align one moment while the continuing rate difference makes later moments wrong again.
Is it always network speed?
No. A stable connection can still carry media or encounter playback timing that drifts.
