generated from ReVanced/revanced-patches-template
-
-
Notifications
You must be signed in to change notification settings - Fork 311
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(YouTube): Non-1.0x playback speeds resetting to 1.0x after entering "x responses" in comments and unpausing the video #4168
Labels
Bug report
Something isn't working
Comments
MPUltraX
changed the title
bug: non-1.0x playback speeds resetting to 1.0x after entering "x responses" in comments and unpausing the video
bug: (YouTube) non-1.0x playback speeds resetting to 1.0x after entering "x responses" in comments and unpausing the video
Dec 19, 2024
also happens in Picture-In-Picture mode randomly |
This comment has been minimized.
This comment has been minimized.
Yes.
|
Ok I can reproduce now. Need to go into a comment thread for the issue to show. |
This is an issue that is also reproduced on unpatched YouTube, so Google should fix it This commit shows an example of fixing the issue on the patch side |
LisoUseInAIKyrios
changed the title
bug: (YouTube) non-1.0x playback speeds resetting to 1.0x after entering "x responses" in comments and unpausing the video
bug(YouTube): Non-1.0x playback speeds resetting to 1.0x after entering "x responses" in comments and unpausing the video
Dec 22, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
If a non-1.0x playback speed is set, when going to the comment section and pressing "x responses" and pressing the back button, the playback speed will reset to 1.0x upon pausing and unpausing the video. The default playback speed setting in Settings > Revanced > Video doesn't matter.
App: YouTube 19.46.42
Patches: 5.5.1 default
Error logs
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: