[PD-dev] writesf~ file type bug

Hans-Christoph Steiner hans at eds.org
Mon Apr 5 21:24:15 CEST 2004


Here is a patch that illustrates a bug in [writesf~]'s file type 
handling.  It doesn't read the file extension and use that type, as it 
seems to say in the help patch.  It defaults to .wav instead, 
regardless of the filename given it.

.hc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 245 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20040405/e2b6325c/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: writesf_open_aiff_bug.pd
Type: application/octet-stream
Size: 837 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20040405/e2b6325c/attachment.obj>
-------------- next part --------------


#N canvas 90 31 446 354 10;
#X msg 23 96 open test.wav;
#X obj 29 209 writesf~;
#X obj 23 118 writesf~;
#X msg 29 190 open test.aiff;
#X text 22 3 According to the [writesf~] help file:;
#X text 17 26 The soundfile format is determined by the file extent
("foo.wav" \, "foo.aiff" \, or "foo.snd").;
#X obj 30 289 writesf~;
#X msg 30 270 open -aiff test.aiff;
#X text 23 165 creates a WAV file called test.aiff.wav;
#X text 17 71 creates a WAV file called test.wav;
#X text 24 245 creates a AIFF file called test.aiff;
#X connect 0 0 2 0;
#X connect 3 0 1 0;
#X connect 7 0 6 0;


________________________________________________________________________ 
____

Using ReBirth is like trying to play an 808 with a long stick.
								-David Zicarelli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 812 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20040405/e2b6325c/attachment-0001.bin>


More information about the Pd-dev mailing list