[PD] Wav file corruption with writesf~

[thewade]

> > 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?

Thanks for the help!
-thewade