-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Expected behaviour
When hovering the timeline, the element .theoplayer-preview-time-display shows the estimated time corresponding to that position of the playhead. So that if I click on that point on the timeline, I expect the playhead to land on that time code.
Actual behaviour
However, this calculation is not correct and:
- the longer the stream, the bigger the imprecision
- the farther from the exact timeline bar center, the bigger the imprecision
- the smaller the player width, the bigger the imprecision
This last point seems to indicate that this might be due to some margins on the timeline bar that are not taken into account in the calculation.
Case examples
- on a 10-min stream, even clicking at the very beginning or the very end of the stream the seek lands almost correctly: the difference is ~1 second.
- on a 1h stream, the difference between the time code in the label and the actual seek landing point can be up to ~15 seconds, if seeking to near the end or beginning of the stream (player in fullscreen).
- same case as the latter, but with the player only occupying a fraction of the screen (e.g.: same fullscreen, but with the devTools open), and the delta can be up to 30-50 seconds.
Test streams
https://video-production-1.nbg1.your-objectstorage.com/streaming_playlists/hls/8fbad86e-40ba-43c7-a30c-192085007343/574b5831-0d54-4a9a-adfe-94485a3d4fe7-master.m3u8
https://livesim2.dashif.org/vod/testpic_2s/multi_subs.mpd
Remarks
Possible culprit: --theoplayer-range-padding
This highlights the difference between expected and actual landing point
Padding style - increasing this value increases the imprecision.