Re: OSCresponderNode

OSCresponder does not have subsample time resolution -- actually, it
CAN'T even under optimal conditions. It can respond only when the
message is received in the client, and this involves a small but
unknown network latency time. The latency can be expected to be within
a certain range, but it isn't a fixed value.

Using OSCresponder for absolute timing precision is, unfortunately,
likely to be a disappointing experience.

Routines/Tasks/Patterns allow better control over event timing for
reasons described in the ServerTiming help file -- however even this
seems not to be wholly sample accurate because of sample clock drift
in the server itself. (I recall a discussion on the list about this a
couple of months ago.)

In terms of timing, Patterns and Routines aren't fundamentally
different. The backend scheduling mechanism for both is the same.

Don't have time at the moment to read over your examples and
brainstorm... perhaps later.
hjh


On Wed, May 7, 2008 at 6:36 AM, Joe Mariglio <joe.mariglio@...> wrote:
> Hi all,
>
> I'm trying to trigger subsample accurate grains using OSCresponderNode, but
> I'm running into a rate limitation that ends up sounding like ring
> modulation, with the modulator frequency at a multiple of 44100/64, which
> also happens to be server's sample rate over blockSize.  Nevertheless, I've
> determined it's not scsynth but rather OSCresponderNode itself which limits
> the response rate to this frequency.


--
James Harkins /// dewdrop world
jamshark70@...
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users