Thanks, in fact soundfiler did it. I just had to specify things to override.
_Ricardo
2008/9/8 Derek Holzer derek@umatic.nl
[soundfiler] can also be used here, see the help file. But then you'll have
to provide all information like number of channels, headersize, endianness and bytes per sample.
d.
Ricardo Dueñas Parada wrote:
I was making a recording with writesf~, and my computer suddenly turned off. The file was created, about 200 MB, but It wasn´t closed or finished, so I can´t open with the objects I know on pd.
derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 206: "What most recently impressed you? How is it similar? What can you learn from it? What could you take from it?"
Ricardo Dueñas Parada wrote:
Thanks, in fact soundfiler did it. I just had to specify things to override.
well [readsf~] should have worked as well (you can override headerchunk, frame-offset and whatever). i used [readsf~] in past for repairing soundfiles that were written with [writesf~] without "stop"ing it.
fmgad.sr IOhannes
Yes indeed, I didn´t know that. It worked too. Thans.
_Ricardo
2008/9/9 IOhannes m zmoelnig zmoelnig@iem.at
Ricardo Dueñas Parada wrote:
Thanks, in fact soundfiler did it. I just had to specify things to override.
well [readsf~] should have worked as well (you can override headerchunk, frame-offset and whatever). i used [readsf~] in past for repairing soundfiles that were written with [writesf~] without "stop"ing it.
fmgad.sr IOhannes