Go to Manage Devices. It can be accessed both from Startup Configuration
or from the Edit menu after the Composer has been started.
Go to the OSC / Server section.
Here you can select the network Adapter and Port you want to receive OSC messages through. Choose -any- for listening on all available adapters. The default settings are usually suitable.
Please note that Aximmetry can only receive and send OSC messages via UDP.
If you also want to send OSC messages to external devices, go to the OSC Out / UDP section.
Here you have to specify all the target devices you want to send OSC messages to. Click Add and specify the IP (or Hostname) and Port of the target device.
Repeat it for all desired devices.
Please note that for outputting OSC messages Aximmetry use the same adapter you selected in the Server section.
The usual scenario is that the incoming OSC messages only contains an address and a single floating point number (or alternatively an integer, logical or double value). This kind of messages can be used to control properties and buttons just like with MIDI or DMX controllers.
Right-click the name of a numeric or a logical property or a control board button and choose Assign OSC...
Then simply send the appropriate OSC message from your controller device (e.g. move a fader or press a button) and the assignment is made.
(If you write your own controller software, please note that in order to operate a button you have to send a value 1 then after a short while a value 0. It corresponds to the concept of controller button push = 1, release = 0).
To see and manage all the OSC assignments you made in your compound go to File / Properties / OSC Assignments.
Controlling Flow graph
You can also build controlling structures within the flow graph using the OSC modules.
For the OSC messages containing a single floating point number (or alternatively an integer, logical or double value) you can use the OSC Scalar module.
For the module you have to specify an OSC Address.
It can be entered manually, but you can also use the Learn function. Turn On Learn
then move/press a fader/button on your OSC controlling device. The address will be filled automatically.
If the OSC message contains an arbitrary number of floating point values representing a 2D or 3D position or any arbitrary series of numbers you can use the OSC Vector module.
OSC messages can contain any number of arguments of various types. To handle any general case use the OSC Method module.
It outputs a collection with each argument assigned the keys 1, 2, 3 etc. In this example below we’ve received a message with 5 arguments of types float, string, Nil, integer and a logical true (,fsNiT).
In order to access the individual arguments you can use the standard Collection modules. E.g. if you need the second string argument use the Collection Text module:
To acess the second argument enter 2 into the Key property (please pay attention for not entering the number into the Index property which is incorrect in this case).
You can access the other arguments similarly.
On handling the collection data type in general see more info, see Pin Data Types - 04 - Transformation, Collection.
Sending OSC output
For the opposite scenario, when you want to control external devices from Aximmetry via OSC use the OSC * Out modules.
Scalar and vector output
For single numeric values or a series of numbers use the OSC Scalar Out and OSC Vector Out modules.
For these, you have to specify an output Device (from the list you’ve created in the initial setup, see above), and a target address.
The actual sending of the message can be performed in two ways. You can send it at a specific time by triggering via the Send pin. Alternatively you can turn On Auto Send, in this case each time the Argument value is changed it is sent automatically.
For sending arbitrary number of arguments of any type use the OSC Out module.
E.g. to achieve the message structure we’ve seen above do the following:
Please note that we do not add any argument for Key = 3. In this case a Nil element will be inserted as the third argument.