[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sc-devel] [RFC] sample accurate scheduling



Hi James,

Is it correct to add, "however an individual client will be able to maintain sample accurate scheduling with only one sample clock"?

RJK

On Dec 2, 2007, at 1:13 AM, James McCartney wrote:

On 12/1/07, James McCartney <asynth@xxxxxxxxx> wrote:
The issue of hardware clock drift was certainly understood when
deciding to use OSC time stamps. SC3's goal was not sample accurate
scheduling, but accurate distributed scheduling based on a shared
clock (NTP time). So even on servers running at different sample
rates, you get simultaneous events. An anchor point and rate scalar
can be computed between the actual hardware rate and OSC time on each
server and broadcast to interested clients.

To be more clear this should read:

In order to support sample accurate scheduling however, an anchor
point and rate scalar  can be computed between the actual hardware
rate and OSC time on each server and broadcast to interested clients.

--
--- james mccartney
_______________________________________________
Sc-devel mailing list
Sc-devel@xxxxxxxxxxxxxxx
http://www.create.ucsb.edu/mailman/listinfo/sc-devel