hmm
I know of the NRT issues in the event framework to render some things
that need a clock. The problem there (as I can tell) is exactly the
other way around; scsynth has no TempoClock; May look at first as if
we solve one we get the other but I dont think I get the idea. Unless,
I am missing something.
Ron, did you mean a server side implementation of TempoClock?
I have been looking at the lang and server scheduling code; it seems
to me that the cleanest approach to implement sample scheduling in
scsynth is by creating a new message queue for the new sample
scheduled bundles; process these packets in parallel with the osc
messages queue in the run loop (using an also new priority queue).
This of course implies the creation of several new classes/structs to
deal with samples instead of osc timestamps mostly.
for example for SC_ScheduledEvent we'd have SC_SampleScheduledEvent
something like: