-
Notifications
You must be signed in to change notification settings - Fork 145
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
Mix_MusicDuration return value incorrect with dr_mp3 backend? #439
Comments
There is possible incorrect meta-data inside of that MP3 file, or the length computing according to a number of frames, even ignoring the case that the last frame may be lesser 🤔 |
Off topic: |
I had suggested it, @slouken had accepted it: #244 (comment) I don't like the revert to minimp3 though, possibly a mistake: Have any of you guys even reported the issue at hand to dr_libs? |
I haven't, but I'm working on an SDL_mixer release and I'd rather use tested code that fixes the length issue than wait for an upstream dr_libs fix. I'll go ahead and report it and if there's a compelling reason to switch back once that's fixed, we can easily revert this revert. |
By the way, |
The duration / LAME tags issue report is at mackron/dr_libs#263 Hopefully it gets resolved soon and we can get back |
Hi all,
Just happened on a potential bug in
SDL_mixer
with the newdr_mp3
backend, thanks to the efforts of @smcv: py-sdl/py-sdl2#243Essentially, with the default
dr_mp3
backend,Mix_MusicDuration
seems to be over-reporting its duration: on my system with the official macOS mixer 2.6.1 binaries, I get 0.209 seconds for the test MP3 (available here: https://github.com/py-sdl/py-sdl2/blob/master/sdl2/test/resources/soundtest.mp3), whereas with the libmpg123 backend it reports 0.1502 seconds for the same file (which @smcv helpfully confirmed was the correct duration in the linked issue above). Since the unit test I wrote based on that 0.209 number has been passing on Windows, macOS, and Linux CI runners (all with thedr_mp3
backend), I'm fairly certain it's not a platform specific issue.Any ideas what's going on?
The text was updated successfully, but these errors were encountered: