Hello list-list-list,
Why is it that writesf~ always makes bad wav files? I always have to open them up in some editing program, like soundforge, and "save as" to repair. Lame quits encoding to mp3 with a segmentation fault! Sweep cant even give me an error.
It does this in windows PD 0.37, and linux PD 0.37.1 TEST6
What up with that?
Thanks, -thewade
Why is it that writesf~ always makes bad wav files? I always have to open them up in some editing program, like soundforge, and "save as" to repair. Lame quits encoding to mp3 with a segmentation fault! Sweep cant even give me an error.
just a guess, but it might be somehow related to the header of the wave file ... problably writesf~ isn't writing a correct header that lame tries to read ... there are tools to write a wave header other than soundforge ;-)
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
thewade wrote:
Why is it that writesf~ always makes bad wav files? I always have to open them up in some editing program, like soundforge, and "save as" to repair. Lame quits encoding to mp3 with a segmentation fault! Sweep cant even give me an error.
Are you sending the object any additional messages besides filename? If so, what? Try sending:
"open -wave -bytes 2 -rate 44100 /tmp/foo.wav"
[or something like that, maybe I have the bytes wrong...] to write a proper header, instead of a simple:
"open /tmp/foo.wav"
which may not write a header at all.
good luck, d.