-
-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: SponsorBlock skipping a segment at the end of a video in playlist and doesnt autoplay the next video in playlist #3524
Comments
I cannot reproduce the issue when using that video in playlist. The sponsor at the end auto skips correctly and the next video in the playlist starts playing. Are you using Bluetooth speakers or headphones? |
I am using bluetooth headphones |
But when i disconnect them, the problem still occurs. |
Try turning off Bluetooth, restarting your device, and try again with Bluetooth off. It sounds like the same issue as #3015 |
Just tried turning off and restarting, but still the same issue. No autoplay |
Someone that can reproduce the issue needs to try building locally and make the change described here. |
Dupe of #3015 |
But its not a duplicate. 3015 says that turning off bluetooth worked, but my issue isnt fixed by that. |
The issue is the same, you are talking about the solution |
Bug description
This is the same issue I brought up many months ago in two separate bug reports (#68) and (#46). It was resolved, but I discovered a new video where SponsorBlock skipping a segment at the end of a video (the video is in a playlist) somehow disables the autoplay of the next video in a playlist. I was listening to my watch later playlist and found this example (https://www.youtube.com/watch?v=-cIHLgGZByY). Not sure if others may be able to replicate my issues. Just wanted to bring it up. And yes, of course the video works when I turn off SponsorBlock because there isnt any skipping of segments.
Error logs
No response
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: