Why the estimate jumped instead of moving on smoothly: the first read
(start), a seek, a state change, a new track, or a position update that
disagreed with the estimate by more than the resync threshold (resync,
also sent after PlaybackClock.resync reads the position again).
Why the estimate jumped instead of moving on smoothly: the first read (
start), a seek, a state change, a new track, or a position update that disagreed with the estimate by more than the resync threshold (resync, also sent after PlaybackClock.resync reads the position again).