Hi all,
about the clock issue: Patterns with tempo alterations break in
asScore - it is a language issue not a server issue. My point was
simply that
the blocking clock has two tempo controls - one to control tempo
another to control timebase (i.e., to keep it a little faster than
the sample clock's timebase). For score generation we need
something similar where the "timebase tempo" is as fast as possible.
about sample position versus timestamp scheduling: I think the jury
is out on that. Certainly the first step is to just do the
blocking clock, but it is not out of the question that short term
clock jitter will still create audible artifacts.
RJK
On Dec 1, 2007, at 2:09 PM, Jan Trutzschler wrote:
I think Scott is right. I think the server should only have the
option to run its scheduler on the hardware's sample clock.
j
On Dec 1, 2007, at 6:32 PM, Scott Wilson wrote:
Why not simply use timestamps in seconds and then maintain OSC
compatibility rather than implement a new message and queue? If
the clock is the same everything should align correctly, yes?
_______________________________________________
Sc-devel mailing list
Sc-devel@xxxxxxxxxxxxxxx
http://www.create.ucsb.edu/mailman/listinfo/sc-devel
_______________________________________________