|
From: Chris B. <ch...@cn...> - 2007-11-06 03:19:54
|
Mike Keithley wrote: > On Sun, 4 Nov 2007, Chris Bagwell wrote: > > -Mike Keithley wrote: > -> -Any history you can provide on these WAV files would also help (were > -> -they created with earlier version of SoX or another application?). Can > -> -you read the monkey.wav file that comes with SoX source code? > -> - > -> -Chris > -> - > -> The wav files I tested were made by sox 13.0. Monkey.wav would not play. It > -> gives > -> > -> "sox soxio: Failed reading rc/monkey.wav': Could not find data chunk." > -> > -> > -Could you also run your command line with "-V4"... It should print a > -list of chunks that it does sucessfully process. I'm curious were the > -problem first starts. > - > -Chris > - > I got the following output from > sox -V4 src/monkey.wav test.wav > > sox: SoX v14.0.0 > sox auto: Detected file format type: wav > sox wav: WAV Chunk fmt > sox wav: WAV Chunk FF? > sox soxio: Failed reading `src/monkey.wav': Could not find data chunk. > I don't know the exact problem but from your output I'll take a guess of the general area. Right after the "fmt" chunk should be the "fact" chunk. Instead of finding that, it found "FF?". I looked at monkey.wav and the only occurance of "FF" is at the very beginning of the file where it has "AIFF". So it seems maybe the file somehow did a rewind. SoX does use fseek() to jump to the next chunk faster and in fact new to 14.0.0 is changing to fseeko() to seek into larger files. So I'm guessing something about Slackware doesn't like fseeko(). Hopefully, this gives some hints for others to help pinpoint the problem faster. Chris |