-
Notifications
You must be signed in to change notification settings - Fork 374
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
Playback time inaccuracy #1055
Comments
This might be an issue with the file, i know there was a but in FFmpeg some time ago. |
I have same issue many times. |
Yeah, this is fix trouble, but maybe should integrate it in app? |
I believe I'm experiencing this on mp3 files with CBR encoding as well, it might not anything to do with VBR headers. I will try this weekend to take notes on detailed reproduction steps and then will post them here. |
Just confirmed while listening in the car. I paused audio for about 30 seconds while I was order food at a drive through restaurant. When I hit the play button to resume, audio had jumped forward by about 2 or 3 minutes, so I hat to hit the rewind button 6 or 7 times to get back to where I was previously. Audio file is CBR mp3 at 128 kbps, stereo encoding, about 8 hours in length. Unfortunately I want able to capture detailed repro steps because I was in the car. Will try to repro again in the next few days. |
I have the same issue; mp3val shows: "921939 MPEG frames (MPEG 1 Layer III), no tags, CBR" The file is an audiobook and contains about 6h of audio at 80kbit/s. |
Thanks for the report. Thats unfortunatelly a limitation right now and there is nothing we can do about. However, once ExoPlayer supports this better, Voice will get that behavior too. For now I can only recommend to convert your files to a more modern format like m4b / aac |
On long audio files, the displayed elapsed playback time-keeping seems to be inaccurate, so that it slowly "drifts" from the actual elapsed time. For example, if I play a file for 20 minutes, the elapsed time actually progresses 21 minutes instead of 20. This means that upon exiting the app and coming back, playback resumes from 1 minute later than expected, meaning a large chunk of audio is skipped.
This is easy to see at the end of playback when you finish a file, and the elapsed time displayed is a larger number than the total length of the file, as in the attached screenshot.
The text was updated successfully, but these errors were encountered: