sox doesn't like gramofile wav files

[Charles Hallenbeck]

Hi Cheryl -
What you describe is nearly inevitable. It happens because the
recording is terminated by interrupting the program (grammofile)
so it never has an opportunity to write the true length of the
recording in the wav file header. Simply copying the resulting
wav file (with sox) to another file will result in the true
length being placed in the new header instead of "infinity" which
the original header contains. I use "arecord" to do my recording
and the same thing happens with it. Terminating the actual
recording with a ^C leaves the output file header containing
"infinity" for a file length. In my case I use scripts a lot, so
in my scripts I usually direct the arrecord output to /tmp, and
then within the script I use sox to copy it to my working
directory, where it ends up with a proper length.

Chuck


On Thu, 9 May 2002, Cheryl Homiak wrote:

> Anybody have any idea why this might be happening.
> I use gramofile to make a recording, but since i haven't figured out how to
> reliably handle gramofile's filters I want sox to convert the wav file, since
> it's recording on 1 channel but recorded as two-channel. but frequently (not
> sure if allways) sox tells me that there is a premature EOF on the file.
> Now, if I make an ogg file of the original wav file, convert back to wav, and
> then run it through sox, there's no problem, but who wants to do all that?
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
Visit me at http://www.valstar.net/~hallenbeck
The Moon is Waning Crescent (7% of Full)