[PD] Wav file corruption with writesf~

[Hans-Christoph Steiner]

On Sunday, Apr 18, 2004, at 18:50 America/New_York, thewade wrote:

>>> Can anyone tell me why my wav files are written corrupted on both my  
>>> windows
>>> and linux machines using [writesf~]?
>>
>> Sending the message \"open -wave -bytes 4 -rate 44100 /tmp/foo.wav\"
>> works for me when I want 32-bit floating point. \"-bytes 2\" should  
>> write
>> a normal 16 bit wav file. Try using all the flags to write an explicit
>> header for your wav file instead of no flags and trusting that the
>> header will come out right.
>
> Ive tried the above, but still cant get aplay or lame to recognize  
> files. audacity opens them fine, and can save them, but even then lame  
> and aplay cant read them!
> I dont know what to do. THe only thing I can do is move them to my  
> windows machine and open->save as the soundfiles in soundforge. That  
> seems to repair them.
>
> Is there something I can do to see where exactly in the sound file the  
> problem is happening? Some sort of wave file analysis tool?
> Are aif files loseless, just like wav files?
> What are my alternatives?

AIFF files are a very similar format to WAV in that an AIFF file can  
hold many different types of audio.  But the default for AIFF as it is  
for WAV is generally uncompressed and lossless.

.hc

________________________________________________________________________ 
____

Man has survived hitherto because he was too ignorant to know how to  
realize his wishes.
Now that he can realize them, he must either change them, or perish.
		                                     -William Carlos Williams

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1648 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20040418/08bb795a/attachment.bin>