logical name of the output. The server does not know about output names, this is purely for client side usage (e.g. in a GUI or help system).
the "shape" or type of output signal, for example (continuous) generic or binary trigger. technically all signals are the same, the shape just indicates the expected shape of that signal.
if defined, specifies the name of an argument (in the spec's args
) which must be of
type Int
, determining the number of channels in this output.
logical name of the output.
logical name of the output. The server does not know about output names, this is purely for client side usage (e.g. in a GUI or help system).
the "shape" or type of output signal, for example (continuous) generic or binary trigger.
the "shape" or type of output signal, for example (continuous) generic or binary trigger. technically all signals are the same, the shape just indicates the expected shape of that signal.
if defined, specifies the name of an argument (in the spec's args
) which must be of
type Int
, determining the number of channels in this output.
Specification of a UGen output. Note that this describes one logical output. A UGen with a variable number of output channels can be seen has having _one_ logical output. For instance, the
In
UGen has one output signal, even if that signal may have any number of channels. In contrast, thePitch
UGen has two discrete logical outputs, one indicating the status ("hasFreq"), the other giving the actually seen frequency.logical name of the output. The server does not know about output names, this is purely for client side usage (e.g. in a GUI or help system).
the "shape" or type of output signal, for example (continuous) generic or binary trigger. technically all signals are the same, the shape just indicates the expected shape of that signal.
if defined, specifies the name of an argument (in the spec's
args
) which must be of typeInt
, determining the number of channels in this output.