OSCSched

Extension

Description

The bundle is kept on the client until the last possible moment, and then actually sent to the server in a time stamped bundle, just before it is due to be executed.

Bundles can be scheduled for precise execution using relative seconds, relative beats, absolute seconds or absolute beats. Bundles can be scheduled on multiple servers, with exact simultaneous execution times.

Bundles can be easily cancelled up until the time they are sent to the server. They are sent to the server just before execution.

The Tempo class is used to specify what the tempo is, and is used for all beat <-> second calculations. A default global Tempo object is used, or you can create a specific Tempo instance.

There is a default global OSCSched that can be addressed through class methods. It uses the SystemClock and the default global Tempo. You may also create individual instances that maintain their own scheduling queues, tempii, and time epochs.

The default clock used is the SystemClock, but you may also specify to use the AppClock.

An optional clientSideFunction can also be supplied that will be evaluated on the client at the exact time as the OSC bundle is scheduled to happen. This could be used to show a change in the gui or to update some setting on a client side object.

All of these methods exist as both

class (the default global scheduler) OSCSched.tsched(seconds,server,bundle,clientSideFunction)

and instance methods (a specific scheduler). oscSched = OSCSched.new; oscSched.tsched(seconds,server,bundle,clientSideFunction)

All of the x-methods establish a block such that a subsequent schedule using another x-method will cause the previous one to be cancelled. This is particularily useful when you are controlling something from a gui or process, and change your mind before the event you have triggered comes due. Another example is a pattern that returns delta beat values, repeatedly scheduling its next note at the time of playing the current one. To switch the pattern with another or abruptly start it over, simply do so: if you used xsched, then the previously scheduled event will be cancelled. In most cases, you will wish to create a private instance of OSCSched when using this technique.

Class Methods

.global

.initClass

.tsched

.xtsched

.sched

.xsched

.qsched

.xqsched

.tschedAbs

.schedAbs

Instance Methods

.tsched

.xtsched

.xtschedFunc

.sched

.xsched

.qsched

.xqsched

.tschedAbs

.schedAbs

.aschedFunc

.schedAtTime

.xschedAtTime

.xschedBundle

.tschedAbsNext

Examples

Absolute Beat / Time scheduling

continuing with the scheduler and defs created abovec.clear; // execute the example below all at once // the functions execute at the server event time // note the imprecision ( c.beat = 32.0; // beat 32 is now c.schedAbs(36.0,s,i,{c.beat.postln}); // in c.schedAbs(39.0,s,o,{c.beat.postln}); // out c.schedAbs(41.0,s,o,{c.beat.postln}); // out c.schedAbs(40.0,s,i,{c.beat.postln}); // but first in c.schedAbs(43.0,s,i,{ c.beat.postln; c.schedAbs(42.0,s,o,{ "this will never happen, its already in the past".postln; }); c.schedAbs(46.0,s,o,{ c.beat.postln; }); }); )

scheduling a function( c = OSCSched.new; c.beat = 32.0; // beat 32 is now c.aschedFunc(36.0,{c.beat.postln}); // in c.aschedFunc(39.0,{c.beat.postln}); // out c.aschedFunc(41.0,{c.beat.postln}); // out c.aschedFunc(40.0,{c.beat.postln}); // but first in c.aschedFunc(43.0,{ c.beat.postln; c.aschedFunc(42.0,{ "this will never happen, its already in the past".postln; }); c.aschedFunc(46.0,{ c.beat.postln; }); }); )

Exclusive x-methods