[PD-dev] [ pure-data-Bugs-3579737 ] wavinfo wrong output - fmt block size related

[SourceForge.net]

Bugs item #3579737, was opened at 2012-10-24 05:13
Message generated for change (Tracker Item Submitted) made by charlesgg
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3579737&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: externals
Group: v0.43
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Charles Goyard (charlesgg)
Assigned to: Nobody/Anonymous (nobody)
Summary: wavinfo wrong output - fmt block size related

Initial Comment:
While using wavinfo on wav files (converted with ffmpeg), I noticed the sample count is wrong (real large).
The problem comes from the fact that ffmpeg always uses a 18 bytes block size for the fmt section, while wavinfo seems to assume it's always 16 bytes.
The standard says if type is PCM then size should be 16, but can be 18 for other formats.
wavinfo should either refuse to read the malformed wav file or use the actual fmt block size, not return nonsense. This involves splitting the wave_t structure in two or maybe using an union.

Attached is a sample wav file.

Note that readsf~ is able to read the file.

Thank you

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3579737&group_id=55736