[PD-dev] [ pure-data-Bugs-1122560 ] writesf~ 64-bit distorted files

[SourceForge.net]

Bugs item #1122560, was opened at 2005-02-14 11:15
Message generated for change (Comment added) made by pdman
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1122560&group_id=55736

Category: None
Group: None
Status: Open
Resolution: None
Priority: 8
Submitted By: thewade (pdman)
Assigned to: Nobody/Anonymous (nobody)
Summary: writesf~ 64-bit distorted files

Initial Comment:
It sounds like writesf~ .wav files in 64-bit PD are
written at twice the sampeling rate.
If I writesf~ a .wave file, the readsf~ that file back
in (using 0 200 2 2 l as part of the open message, as
readsf~ complains about bad .wav headders even from
writesf~) it plays twice as fast as it should. I cannot
fix this by adding the -rate message.

AMD64 laptop
2.6.10-lsm kernel
PD from CVS as of late January, early Febuarary I think

----------------------------------------------------------------------

>Comment By: thewade (pdman)
Date: 2005-02-28 13:53

Message:
Logged In: YES 
user_id=1179250

I have uploaded a test file created using the broken
writesf~ to my website:
http://www.aproximation.org/test.wav
As sourceforge apparently wont allow files of that size
(approx 1900kb) to be uploaded.

----------------------------------------------------------------------

Comment By: thewade (pdman)
Date: 2005-02-27 20:02

Message:
Logged In: YES 
user_id=1179250

I guess I can read in files and write files out, provided I
override headers (I got aplay to play the audio file by
specifying -f dat) but I still think this is a bug. I should
be able to send [open /myfile.wav< to writesf/readsf and
write/read a file with valid headers. I have attached a mono
wave file written with pd to this ticket.
Thanks!
-thewade

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1122560&group_id=55736