-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Not the same playback position when changing players #4497
Comments
For me, Newpipe has always resumed a little behind where I pause it when I switch to other apps. I thought that was a feature, trying to maintain continuity. But only something like 5-10 seconds. If that is indeed how the code works, maybe there is a bug in it? |
also but not so related.... if you play video A, then play video B, then go back to video A... video A will start from the beginning I can open a new issue if my comment here is not sufficient. |
@MD77MD Do you have Resume turned off? |
ok so i did turn on resume in history settings... however the problem is still there... could you try yourself.. maybe its only my device. |
#4506 playback position from video B to video A bug |
No ripple here for one year already... |
@ildar I never had this problem. So nothing to fix until someone provides 100% reproducible procedure |
I see.
I have it reproducible on 0.21.10 this way:
1. Open a video's page.
2. tap "Play in background". Video starts playing. Remember the time value
"t1". Notice the current video time advances. Wait a few seconds (or
minutes if you like).
3. tap "Play in window". Notice that video time jumps BACK to the "t1"
value.
Could you please check this sequence? Thanks!
|
Yep, can reproduce with popup and background buttons |
yep... its there |
Checklist
Steps to reproduce the bug
It does not always happen, I don't know why
Actual behaviour
The playback position is current minus about 20s
Expected behavior
Same playback position when changing players
Screenshots/Screen recordings
Logs
Device info
The text was updated successfully, but these errors were encountered: