-
Notifications
You must be signed in to change notification settings - Fork 57
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
WavReader may be too strict on WAVEFORMATEX data #20
Comments
Thanks for reporting! If the struct has an unexpected size, it might have fields in there that need to be taken into account, or other fields could be at different offsets. It is possible that we can figure out the meaning, or that these fields can be safely ignored, but I would have to look at the file. Are you able to share a file to reproduce this issue? If copyright is an issue, you can truncate the file after the first 100 or so bytes of audio data. (In a hex editor, look for the string |
First 200 bytes of the file are here. |
Thanks! I believe the file is actually valid and Hound was being too restrictive. I pushed a fix to master, could you please confirm that you are now able to read the file? |
Yep! This fixes the problem. Thanks for the quick update! |
Great, I’ll make a new release then. |
Hound v3.3.1 is now on crates.io. |
At least one of the WAV files used by Quake (
pak0.pak/sound/doors/baseuse.wav
) results inFormatError("unexpected WAVEFORMATEX size")
when trying to open it. This file opens and plays successfully in mplayer, VLC and mpv.Using
hound
3.3.0:Output:
Perhaps this should be a warning instead of a fatal error?
(This is using
pak0.pak
with md5sum85fc9cee2035b66290da1e33be2ac86b
)The text was updated successfully, but these errors were encountered: