score provides various features to ease the management of parameters. These are specially useful when writing complex processes (e.g automations).
When a parameter of a declared device defines a set of values (e.g parameters defining an XYZ position or an RGB color), items in this array can accessed independently using a special syntax: a parameter address may be followed by an integer (starting from zero) in brackets, which will select a given member.
For example, using
aDevice:/anAddress@ as a destination address of an automation will send the automation value to the second element in the array.
If the array contains sub-arrays (for instance for a matrix), it is possible to address sub-elements like this:
For instance, given
aDevice:/anAddress == [ [a, b], [c, d] ]
the above address will change the value of
Note that without specifying an index, messages and automations sent to array parameters (i.e.
list) will affect all items in the array.
Parameters of a device may be declared with a specific unit (for instance, parameters defining a position in space or a color). score embeds an automatic unit conversion mechanism for advanced automations.
When using these parameters in ports of processes, it is also possible to set an unit set on them, with the same syntax than for array indexing: using
aDevice:/anAddress@[angle.radian] as a destination address of an automation will send the value in this unit (ie. radian). The value will be converted back to the address’s original unit when sent over the network protocol, which may be for instance degrees.
The complete list of supported units is available in the libossia documentation.
In the case of multi-dimensional quantities (for instance, colors, 3D positions), it is also possible to select a single component:
as the output of an automation will only update the red component.
This also works with different units: for instance, if the device has a parameter declared with the
color.rgb unit, it is possible to control its hue with
It is possible to control a set of addresses with pattern matching.
For instance, given the following OSC device:
It is possible to send an automation to
to control all the levels with a single curve.
The complete reference of the supported pattern matching syntax is available here.