[PD] writesf~ errors on 64-bit?

[thewade]

I can read in .wav on 64-bit if I supply use the following readsf~ open
command:
open sound.wav 0 200 2 2 l
Which I understand means: read 0 framse first before playing, skip 200
frames, 2 channels, 16 byte, little endian (pc). I cannot load a file
without skipping frames at the beginning. Is this a known 64-bit bug?
Does anyone else get this?
The help patches are the same way.

Also when I writesf~ I supply:
open sound.wav -wave -bytes 2 -rate 48000 (or 44100)
and a file is created, but when I read it back in through readsf~ the
file playes twice as fast. Another known 64-bit bug?

Thanks for the help!
-thewade