2 summary:: a clock that synchronizes its tempo with the server
3 categories:: Libraries>JITLib>NodeProxy
4 related:: Classes/TempoClock
12 can be anything that responds to the message code::set(key, val, ...):: e.g. a link::Classes/Synth:: or a link::Classes/NodeProxy::. The control key set is "tempo". otherwise TempoBusClock works just like a link::Classes/TempoClock:: .
18 a = { |tempo=1| Ringz.ar(Impulse.ar(tempo), [501, 500], 1/tempo) }.play;
20 Task { loop { "klink".postln; 1.wait } }.play(t);
28 // in ProxySpace, a TempoBusClock can be added together with a ~tempo NodeProxy:
30 p = ProxySpace.push(s);
32 p.clock; // now the ProxySpace's clock is a TempoBusClock
35 ~out = { Ringz.ar(Impulse.ar(~tempo.kr), [501, 500], 1/~tempo.kr) * 0.3 };
38 // patterns and tasks are synchronized:
41 ~out2 = Pbind(\dur, 1, \note, Pwhite(0, 7, inf));