[PD] readsf~ and latency problems

[Krzysztof Czaja]

hi,

1. from object arguments and 'open' message format you quote
I imply you are using readsf~ (as in the subject) and not sfplay~.

2. From the values used in your open message I imply you are using
a .wav soundfile.

3. The readsf~ (and soundfiler) objects assume there is a 'data' chunk
right after a 'fmt' chunk in a .wav file.  If your sound was saved in
wavelab or some such windowish app, there could be another chunk in
between, like a 'PAD' chunk.  If so, then readsf~ reads only from this
extra chunk (which is usually all zeros) -- and you 'really have to work
out how big your header is'...

Krzysztof


Michael Edwards wrote:
...
> The second problem is with sfplay~ and its open message.  When I 'open'
> a longish file (that every other sound player seems to like well enough)
> without setting the optional header size etc. and then try to play it
> with 'sfplay~ 2 1000', I get no output.  When, however I give arguments
> like "open 0 40 2 2 l" it plays ok, but of course skipping some samples
> and creating a click.  Do I really have to work out how big my header is
> etc. to get this object to work?  Any hints out there?