Ops
Related Doc:
package synth
Constructs a GraphFunction, on which then for example play can be called.
This allows conversions to Group so that something like Server.default.freeAll becomes possible.
Wraps the body of the thunk argument in a SynthGraph, adds an output UGen, and plays the graph
in a synth attached to a given target.
Wraps the body of the thunk argument in a SynthGraph, adds an output UGen, and plays the graph
in a synth attached to a given target.
the target with respect to which to place the synth
audio bus index which is used for the synthetically generated Out UGen.
if >= 0, specifies the fade-in time for a synthetically added amplitude envelope.
if negative, avoids building an envelope.
the relation between the new synth and the target
the thunk which produces the UGens to play
a reference to the spawned Synth
Wraps the body of the thunk argument in a SynthGraph, adds an output UGen, and plays the graph
on the default group of the default server.
Wraps the body of the thunk argument in a SynthGraph, adds an output UGen, and plays the graph
on the default group of the default server.
the thunk which produces the UGens to play
a reference to the spawned Synth
Allows the construction or named controls, for example via "freq".kr.
Importing the contents of this object adds imperative (side-effect) functions to resources such as synths, buses, buffers. In general these reflect the OSC messages defined for each object, and send them straight to the server. For example, a
Synthhas functionnewMsgwhich returns an OSC message to instantiate the synth of the server. After importingOps, you will be able to directly launch a synth usingSynthDef.playorSynth.play. You will be able to directly allocate and read buffers, and so forth.The reason why these functions are separated from the rest of the API is to allow other frameworks such as SoundProcesses to avoid side-effects which they handle differently (e.g., using STM).