-
Notifications
You must be signed in to change notification settings - Fork 17
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
Warning: Xing stream size off by more than 1%, fuzzy seeking may be even more fuzzy than by design! #708
Comments
https://sourceforge.net/p/mpg123/bugs/275/ This discussion suggests it is an issue that libmpg123 encounters if the LAME/Xing header for an mp3 file does not match the file contents. e.g. if a Variable bitrate file has constant bit rate information in the Xing header. |
Reproducible example with an audio file, and specific version numbers for librosa, libmpg123 (if used by librosa), or whatever underlying package is relevant |
Mp3 file from here: https://xeno-canto.org/157067 Warning is being raised by librosa (or something under the hood that librosa uses, like audioread). Using librosa
raises the warning. We could filter warnings at the point of loading audio. |
It's not really an us problem, but it is an annoying thing for users to see flooding their stdout. Hiding warnings (or some subset of them? If that's possible) might be helpful for helping new users not to be overwhelmed. |
let's find a way to filter it out as specifically as possible |
I have tried wrapping the
But I still can't silence the warning. @sammlapp I don't think I understand how Warnings are handled well enough to fix this issue. |
I also tried wrapping the import statements with the warning filter, e.g.
|
OK it looks like the problem might be that libmpg123 is printing directly to stderr. It's a C library, not a python package, so I assume the Python warnings system is not going to catch these. You should be able to catch this with redirect_stderr, but apparently that doesn't work either. bastibe/python-soundfile#435 |
These warnings/errors are being raised on reading some mp3 files.
I tried converting some mp3 files that raise this warning to WAV by doing:
And they still raise the warning.
The text was updated successfully, but these errors were encountered: