Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Final frame may be truncated #37

Open
robmcmullen opened this issue Sep 29, 2022 · 0 comments · May be fixed by #38
Open

Final frame may be truncated #37

robmcmullen opened this issue Sep 29, 2022 · 0 comments · May be fixed by #38

Comments

@robmcmullen
Copy link

If the bitstream cache doesn't happen to be filled to an int (32-bit) boundary, the final mp3 frame may be truncated, resulting in a non-fatal error when playing that final frame, e.g.:

$ mpv test.mp3 
[ffmpeg/demuxer] mp3: Estimating duration from bitrate, this may be inaccurate
 (+) Audio --aid=1 (mp3 1ch 44100Hz)
AO: [pulse] 44100Hz mono 1ch float
A: 00:00:03 / 00:00:04 (92%)
[ffmpeg/audio] mp3float: invalid new backstep -1
A: 00:00:03 / 00:00:04 (94%)

Exiting... (End of file)
@robmcmullen robmcmullen linked a pull request Sep 29, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix for truncated final frame. robmcmullen/shine
1 participant
@robmcmullen