[PD] writesf~ bug?

[Jorge Cardoso]

Hi,

I have been playing around with writesf~, trying to save '.au' files (nextstep), and I'm 
getting weird results. I'm hoping someone else can verify this.

I have a Windows machine running PD 0.37.0.
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 
always the same).
Also it seems that field 2 of the file header (data size) is filled with zeroes when, according to 
http://brandt.kurowski.net/projects/lsa/wiki/view.cgi?doc=588, it should be filled with ones.

I made a test patch (see attach) to reproduce these results . 

I experimented re-arranging the file manually and it can be played afterwards...

Hope someone can shed some light on this.

Thanks,
jc 

Ps: I sent this message to the pd-dev list, but it seems that that list is kind of dead so I'm re-posting it here...
---
Jorge Cardoso <-> jorgecardoso at ieee.org

Centro de Investigação em Ciência e Tecnologia das Artes (CITAR)
Univ. Católica - CRP -> Escola das Artes -> Dept. Som e Imagem 
Rua Diogo Botelho 1327
4169 - 005 Porto
Portugal 

"Whether you believe you can, or whether you believe you can't, you're absolutely right." - Henry Ford  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: writesf~bug.pd
Type: application/octet-stream
Size: 923 bytes
Desc: writesf~bug.pd
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20040106/66e15f86/attachment.obj>