-----Original Message----- From: Krzysztof Czaja [mailto:czaja@chopin.edu.pl] Sent: quarta-feira, 7 de Janeiro de 2004 9:22 To: Jorge Cardoso Cc: pd-list@iem.at Subject: Re: [PD] writesf~ bug?
hi Jorge,
Jorge Cardoso wrote: ...
When I use writesf~ to save a file in 'au' format (using
the -nextstep flag) the resulting
file is malformed (I can't open it with any sound program). After a little inspection to the generated file it seems to
me that the file is always
big-indian encoded (it also seems that the -little/-big
flags have no effect, the file is
indeed (except that I got them always little-endian, i.e. "dns.").
Yep, I meant little-endian...
Looks like soundfiler_writeargparse() is broken: the `logic' of its .snd file forming part is to have machine-endian as default, unless for a -big or -little flags both picking a secondary default, which is little-endian.
It really makes no sense to have those flags since the next/sun format (as all other that I know of) is independent of the machine architecture.
The code has not been corrected, since probably nobody uses next/sun format anymore, while aiff and wav's endiannes is fixed.
Well, I still (have to) use it :)
I fixed the code dealing with the endianess, and the size field code also. I have tested it in Linux and it it seems to be working now, but I would
appreciate if someone could compile it for Windows since I haven't been able, yet, to build PD in Windows (any pointers on this would be appreciated too ;).
Bye, jc
Jorge Cardoso <-> jorgecardoso@ieee.org
"Whether you believe you can, or whether you believe you can't, you're absolutely right." - Henry Ford