The OSC protocol
OSC is the acronym for Open Sound Control. This protocol was created to send orders between different applications using the network, a bit like MIDI but more flexible. Many software programs support this protocol and it is therefore a simple way to communicate several applications.
The OSC uses the UDP network protocol.
An OSC device can be declared in Modulo Player.
To be able to send orders to a third party application, it is necessary to know the IP address of the machine where the application and the communication port are hosted.
The IP address is a bit like the street and the port a bit like the number of the mailbox in the street.
To send orders, it is therefore imperative to enter this information correctly, otherwise the order will not be received by the third-party application.
In the same way to receive orders from a third party application in Modulo Player: It is necessary to choose the port on which you want to receive the orders and in the third party application it is necessary to say that we will send commands to the IP address of the Modulo Player.
An OSC message is composed of a path and sent values.
A path is defined by a sequence of words separated by / for example it can be /modulo/task/1 This string is defined arbitrarily but it is imperative that the sender and receiver use the same syntax.
The values sent can be Boolean, integers, float or strings.
Use of the OSC protocol of the Modulo Player:
Modulo Player has an integrated protocol for receiving and sending orders in OSC: This protocol and “Touch OSC”: https://hexler.net/products/touchosc were used to create user interfaces on tablets or telephone when the IU did not exist in Modulo Player.
So we’re going to use a preset for Touch OSC.
This preset is loaded into the tablet or phone connected in network with the Modulo Player using the Touch OSC Editor application, the documentation is available on this “page”: https://hexler.net/products/touchosc
The input and output ports are by default the ones used in Touch OSC.
we will activate “trigger enable” and “feedback” on the OSC device, to receive orders using the OSC Modulo Player protocol and to send information back to TouchOSC.
For those who want to go further, the OSC Modulo Player protocol is described on this “link”: http://support.modulo-pi.com/modulo-player-manual/1/en/topic/osc
It is possible to use this protocol with any application to communicate with Modulo Player in OSC.
Manual use: Task:
A task can also be triggered by using the OSC device as a trigger.
We create a task, we add the OSC device as a trigger.
Manual use: Digimap:
It is also possible to create a digimap that will receive a value from an OSC device.
We add a touchpad in touch osc.
We create a digimap, we patch it to the x-position of a media.
We create a second digimap and patch it to the y-position of a media.
sending an OSC command to a device:
You can also send commands to an OSC application using a task.
For example, we will create two tasks to move a button in the TouchOSC application.
Need more help with this?
Don’t hesitate to contact us here.