Checklist
Describe the bug
Update: Might be due to SABR.
I tested the same timestamp now with MWEB and WEB extraction points, as well as Safari WEB inbetween.
The timestamp works as expected with Safari WEB, so maybe the absolute timestamp is overridden by the earliest relative SABR package that includes the respective timestamp?
I mean like SABR might produce a chunk starting at 00:51, the timestamp queries 00:55, but the next chunk starts at 00:56, which is interpreted as too late, so the 00:51 chunk restarts.
This would also make the underlying SponsorBlock timestamps inaccurate and possibly unfixable.
Also noteworthy, the player is completely unable to start from a second inside such a hypothetical chunk.
If a chunk starts at 00:51 and the next starts at 00:55, you can tap on the bar at 00:54, but it starts from 00:51 regardless.
Update end, original report below
For many videos with SponsorBlock segments, their timestamps oftentimes do no longer match the point the player jumps to after tapping one or have it automatically trigger.
Not only SponsorBlock, but also timestamps in the video description behave like this for me, with an amount of mostly 3-4 seconds being too early.
It also offsets for the "Unskip/Skip" overlay it seems, but not very clearly observable, since it has a inherent offset for the "Unskip".
This happens for me since 5.2.0 or .1, but only since beta2 I paid closer attention.
Effectively, I can not verify a pending timestamp submission by tapping on the timestamp, and existing segments also produce a 3-4 seconds sponsor message leftover for example, but also other timestamps are now not as effective (e.g. comments addressing a point in the video).
I've noticed this over multiple videos across multiple channels and it does not fail for me, but some mismatches are smaller and less noticeable, so I cautiously set the frequency lower.
Version
5.2.1beta3
Frequency
Often (80-90% of the time)
Device
Miatoll, LineageOS 22.2
Steps to reproduce the bug
(1)
- open a video with existing SponsorBlock segments, e.g. https://www.youtube.com/watch?v=XJMbeG3tXjc
- tap on any timestamp of any segment
- player jumps to a time noticeably earlier than timestamp ("00:06:55 Unpaid / Self Promotion" even jumps to 06:49 in player for me, while most other videos only did only 4 seconds)
(2)
- open any video with or without SponsorBlock segments
- skip to arbitrary point
- on SponsorBlock tab, tap "Start" or "End" button to set a pending timestamp
- tap the pending timestamp
- player jumps to point multiple second before timestamp
(3) (Outside of SponsorBlock)
- open a video with timestamps in description (or maybe in comments, not sure
- tap any timestamp
- player jumps to point multiple second before timestamp.
Additional context
There is a inconsistency in the amount of time timestamps trigger an early point. The example above shows 6 seconds, but I mostly see 3-4, sometimes also just 1 second, if not perceived imprecise (the player time does not refresh when quickly pausing and unpausing).
Checklist
Describe the bug
Update: Might be due to SABR.
I tested the same timestamp now with MWEB and WEB extraction points, as well as Safari WEB inbetween.
The timestamp works as expected with Safari WEB, so maybe the absolute timestamp is overridden by the earliest relative SABR package that includes the respective timestamp?
I mean like SABR might produce a chunk starting at 00:51, the timestamp queries 00:55, but the next chunk starts at 00:56, which is interpreted as too late, so the 00:51 chunk restarts.
This would also make the underlying SponsorBlock timestamps inaccurate and possibly unfixable.
Also noteworthy, the player is completely unable to start from a second inside such a hypothetical chunk.
If a chunk starts at 00:51 and the next starts at 00:55, you can tap on the bar at 00:54, but it starts from 00:51 regardless.
Update end, original report below
For many videos with SponsorBlock segments, their timestamps oftentimes do no longer match the point the player jumps to after tapping one or have it automatically trigger.
Not only SponsorBlock, but also timestamps in the video description behave like this for me, with an amount of mostly 3-4 seconds being too early.
It also offsets for the "Unskip/Skip" overlay it seems, but not very clearly observable, since it has a inherent offset for the "Unskip".
This happens for me since 5.2.0 or .1, but only since beta2 I paid closer attention.
Effectively, I can not verify a pending timestamp submission by tapping on the timestamp, and existing segments also produce a 3-4 seconds sponsor message leftover for example, but also other timestamps are now not as effective (e.g. comments addressing a point in the video).
I've noticed this over multiple videos across multiple channels and it does not fail for me, but some mismatches are smaller and less noticeable, so I cautiously set the frequency lower.
Version
5.2.1beta3
Frequency
Often (80-90% of the time)
Device
Miatoll, LineageOS 22.2
Steps to reproduce the bug
(1)
(2)
(3) (Outside of SponsorBlock)
Additional context
There is a inconsistency in the amount of time timestamps trigger an early point. The example above shows 6 seconds, but I mostly see 3-4, sometimes also just 1 second, if not perceived imprecise (the player time does not refresh when quickly pausing and unpausing).