-
... s - Collection of key / value pairs for the HS synth. dur i - Duration value or pattern / stream of durations for corresponding Pbind(s). pbindData i - A collection of Pbind pairs or a collection of Pbind pair collections, defining possibly ...
-
... etImplemented; } } ScalarPatchOut : PatchOut { // floats,NumberEditors, numeric pattern players, midi, wacom // things that are not ON the server init { if(bus.isKindOf(BusSpec),{ // ignore bus = nil; }); } rate { ^\scalar } synthArg { ^sou ...
-
... tImplemented; } } ScalarPatchOut : PatchOut { // floats, NumberEditors, numeric pattern players, midi, wacom // things that are not ON the server init { if(bus.isKindOf(BusSpec), { // ignore bus = nil; }); } rate { ^\scalar } synthArg { ^so ...
-
... ct to all. object must be reproducible as a compileString! . (closed functions, patterns with no open functions) at(key) returns an object from the space at that key (see superclass). join(channel, nickname) join a channel with a nickname l ...
-
... this then move the mouse left/right/up/down - classification should follow same pattern. s.boot; ~treebuf = Buffer.loadCollection(s, ~treedata.flat, ~treedata[0].size); ( x = { PlaneTree.kr(~treebuf, [MouseX.kr(0,1), MouseY.kr(0,1)]).poll } ...
-
... ------------------------------------------------------------------------------//PATTERNS::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: //_______________________________________________________________ ...
-
... ngths are now variable within a line, but as the result the total duration of a pattern became variable too so lines are not always playing in sync. This, however, adds to overall unpredictabilty and I've decided to leave it like that for t ...
-
... ------------------------------------------------------------------------------//PATTERNS::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: //_______________________________________________________________ ...
-
... ithmic scheduling. Among the things that clocks "play" are routines, tasks, and patterns. To see how a clock "plays" a routine, first examine how a function works in a routine. The first argument (and usually the only argument) to a routine ...
-
Binary messages The pattern for a binary message is RECEIVER OPERATOR OPERAND For example 2 * 3 is a receiver (the object to which a message is sent), a binary operator, and an operand. ////////////////////////////////////////////////////// ...