[chuck-users] coordinating rhythmic timing with unpredictable OSC events

Kassen signal.automatique at gmail.com
Thu May 3 11:06:07 EDT 2012

On Thu, May 03, 2012 at 07:54:01AM -0700, [chriswicks] wrote:
> Hello all!  I'm quite new to ChucK, and I have a question concerning rhythmic
> timing.


> Is there any way to hack it so that it waits to add the shred until it's lined
> up with everything else (quantized, so to speak).  I'm not sure if I'm properly
> expressing the problem, so let me know if there's some way I can further
> clarify.

Yes, I see. In that case I'd structure the shred like this;

-define UGens and other stuff you need
-advance time for sync
-some sort of loop or structure generating your melody

So far you seem to be missing the 2nd point. What exactly this would
be like depends on the structure, but the shred should wait for
something like the start of the next bar, or some VM-wide event
indicating a new section.

A very simple example of a structure like that is the series of
"otf_X.ck" files in your examples directory. Those will always sync,
no matter at what time they enter the VM or in what order. 

It sounds a bit like you will need something a bit more advanced, but
it's not clear to me yet how the other things you are currently
running are syncing to each other so it's a bit hard to say how new
stuff will sync to those.


More information about the chuck-users mailing list