> 1. click in first frame: This happens when using the built in
> .wav support (not libsndfile). Most .wav files are okay, but some
> (in particular, those from http://www-ccrma.stanford.edu/~bosse/)
> have a header which longer than the usual 44 bytes and LAME cant handle this.
> sox and libsndfile have no problem. Not fixed.
I'm not on my machine at the moment, so I can't check this for sure, but
the wave header contains a bit of information from which you can work out
where the actual sound data starts.
I'm pretty sure there's a "filelength" in the header as well as "data
length". I think (filelength-datalength) usually equals 44, but it should
be simple enough to calculate this and do an fseek to get to the data.
Something else to check in these dud wav files is to see whether they were
created on the mac. The macos is notorious for adding spurious stuff to
the start of files.
later
mike
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
