You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before opening an issue make sure that there are no duplicates and that you are on the latest version. Describe the bug
SponsorBlock skips the segment but gets stuck in a loop, and keeps skipping and playing the part of the video
Expected behavior
I would expect it to skip the segment and not get stuck in a loop
iSponsorBlockTV server (please complete the following information):
OS: Raspbian
Running on Docker
Apple TV (please complete the following information):
Device: AppleTV 4K
OS: tvOS 18.1
Additional context
Log from Portainer:
2024-11-18 23:51:20,066 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:56:23,173 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Subscribe completed, status 200 OK
2024-11-18 23:56:23,245 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Connected to device YouTube on TV (YouTube on TV)
2024-11-18 23:56:23,246 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Subscribing to lounge
2024-11-18 23:56:23,856 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:42,018 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:42,906 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:43,620 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:45,128 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:44,481 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:45,960 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:46,612 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:47,623 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:49,111 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:48,281 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
The text was updated successfully, but these errors were encountered:
Confirming the same experience with similar entries on identical hardware and software, but different video.
2024-12-02 04:29:53,348 - iSponsorBlockTV-o4275umu71q6mu13ejjaoponcm - INFO - Playing video oNmR2YZO2gw with 1 segments
2024-12-02 04:29:54,001 - iSponsorBlockTV-o4275umu71q6mu13ejjaoponcm - INFO - Skipping segment: seeking to 405.847
2024-12-02 04:29:55,472 - iSponsorBlockTV-o4275umu71q6mu13ejjaoponcm - INFO - Playing video oNmR2YZO2gw with 1 segments
2024-12-02 04:29:56,134 - iSponsorBlockTV-o4275umu71q6mu13ejjaoponcm - INFO - Skipping segment: seeking to 405.847
Thanks for opening an issue, it seems like YouTube has rolled back a change they did a while ago that allowed to skip more precisely, down to the millisecond. Now it only allows second precision, which can cause these sorts of loops. Maybe implementing a minimum skip time could fix this issue
+1, I get this issue occasionally, especially when there's a short segment at the very start of a video (start time of the segment is 0:00). I think that the lack of precise time-setting in the client is part of the issue, I think that adding something like a half second or rounding up the end segment timestamp (maybe both) would probably help?
Before opening an issue make sure that there are no duplicates and that you are on the latest version.
Describe the bug
SponsorBlock skips the segment but gets stuck in a loop, and keeps skipping and playing the part of the video
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect it to skip the segment and not get stuck in a loop
iSponsorBlockTV server (please complete the following information):
Apple TV (please complete the following information):
Additional context
Log from Portainer:
2024-11-18 23:51:20,066 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:56:23,173 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Subscribe completed, status 200 OK
2024-11-18 23:56:23,245 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Connected to device YouTube on TV (YouTube on TV)
2024-11-18 23:56:23,246 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Subscribing to lounge
2024-11-18 23:56:23,856 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:42,018 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:42,906 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:43,620 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:45,128 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:44,481 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:45,960 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:46,612 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
2024-11-18 23:57:47,623 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:49,111 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Playing video Cpl373FOntY with 1 segments
2024-11-18 23:57:48,281 - iSponsorBlockTV-tuhgq2ppgmpkive0lbgevh92fp - INFO - Skipping segment: seeking to 493.814
The text was updated successfully, but these errors were encountered: