[PD] floating point soundfiles

Miller Puckette mpuckett at man104-1.ucsd.edu
Wed Jan 9 18:00:36 CET 2002

Hmm, sounds like I should be spending a bit more time on this one..

I do believe I've got chunk-skipping going in my current version of
Pd but it's much too unstable to release right now...


On Wed, Jan 09, 2002 at 12:07:04PM +0100, Krzysztof Czaja wrote:
> hi Miller,
> soundfiler would read 32-bit float .wav files quite willingly, if
> this possibility had not been blocked by rejecting their headers
> -- would you accept them, please?
> Adding ``...else if (format == 32) bytespersamp = 4;'' option to
> .wav portion of open_soundfile() magically allows the soundfiler
> to correctly load such sounds, at least if they were recorded in
> Samplitude (I have not checked other editors).  Why this works?
> Speaking in t_wave terms, soundfiler ignores w_fmttag (which is now
> equal 3), w_navgbytespersec and w_nblockalign fields, using only
> w_nbitspersample (equal 32) as a clue.  All other fields are generic,
> and the original nextstep processing does the trick for sample data.
> Btw, after taking closer look at soundfiler, I would like to know if
> anybody has been using it to load .wav files containing extra chunks
> before data chunk, such as recorded with WaveLab?  I had not been so
> lucky (except in raw mode) without making little changes in the
> sources.  With those changes soundfiler appears to gracefully skip
> unknown chunks and read all the remaining data (both 16, and 24-bit).

More information about the Pd-list mailing list