OSC

This topic includes:

▪Introduction

▪Configuration

▪Sample

▪Address Space & Available Commands

▪Troubleshooting

Introduction

OSC stands for OpenSoundControl.
OSC is a widespread format to communicate between systems, and used for remote control of MADRIX 5.

There are many software applications or hardware controllers available, which offer support for OSC.

The remote sender controlling MADRIX 5 is called client.
MADRIX 5 is the receiver and called server.

Configuration

General

Make sure to start MADRIX 5 first, and then the third-party controller.

In MADRIX 5

In order to use remote control over OSC, you need to set the correct settings.

▪Go to the menu Preferences > Remote Control > OSC

▪A new window will open.

▪Enable Server - Activates reception of OSC messages and input. Is required for the main functionality of remote controlling MADRIX 5.
- Network Port - Defines the network port on which the OSC server is listening for messages. The default value is 9001.

▪Enable Feedback - Activates sending out OSC messages and output.
- It sends states and data from the MADRIX 5 Software back to the remote controller, such as the value of the Master.
- Controller and MADRIX 5 can therefore automatically be in sync.
- This also means, that even changes to MADRIX 5 via another remote-control instance, such as MIDI, will be synced with OSC.
- Destination Network Port - Defines the network port to which the OSC server is sending messages. The default value is 9002.

Your settings will be saved in the MADRIX 5 Setup file.

In Third-Party Controllers

Make sure to configure your remote controller [client]!

For example, in TouchOSC:

▪Go to the menu Edit > Connections > OSC

▪Set up
- Connection 1: UDP
- Host: 127.0.0.1 [127.0.0.1 is the local host, meaning the same computer if you are running MADRIX 5 and TouchOSC on the same computer. Enter the correct host address of the computer running MADRIX 5 if both applications are on different computers.]
- Send Port: 9001 [Use the same Server Network Port as set up in MADRIX 5, as explained above.]
- Receive Port: 9002 [Use the same Feedback Network Port as set up in MADRIX 5, as explained above.]
- Zeroconf: Default

▪Confirm with Done

Sample

The MADRIX 5 Installer includes a sample file, which you can load in TouchOSC.

1] During the setup of MADRIX 5, choose Examples from the list of components.

2] After the installation, you can find the example on your hard disk.

▪Navigate to C:\Users\Public\Documents\MADRIX5 Samples\remote\osc\madrix.tosc

3] Load the sample in TouchOSC via menu File > Open...

4] This is what the sample user interface looks like:

Address Space & Available Commands

Since OSC is a very open protocol, there are many feasible possibilities, and implementations are often based on best practices.
In order for you to control MADRIX 5 remotely, you need to know the available address space and list of commands. You will find the complete list and more details below.
 

Details

▪Support: MADRIX 5 supports OSC clients, whose address space can be freely configured, since it is a custom address space defined by MADRIX 5.

▪Case Sensitivity: The address space is case-sensitive. [Make sure to correctly use capital and small letters.]

▪Data Types: OSC offers usage of several data types. MADRIX 5 is using values of the types integer [i, int, INT, INT32] and float [f, float, FLOAT, FLOAT32].
- All other OSC data types are currently not used.
- See the following examples to identify which data type is required as listed in the address space below.
- Examples for integer values: 0, 55, 255, -10
- Examples for float values: 0.0, 1.84, 20.0, -2.72

▪Address Patterns: Each OSC address starts with / and separates items also via /
- The last item of an address pattern is called the Method, which is the function or functionality.
- All items before the Method are Containers, basically grouping items together.

▪Values To Pass: Methods often require one or more Arguments, which is the exact values that should be used.
- In the table below, arguments are listed as single arguments [...] or multiple arguments [...] [...] [...], which would be three arguments in this case.

▪Arguments: x means a value you can define individually.

▪Arguments: N means the last index number that is available, which depends on how you are using the software; for example, as to how many Cue Lists you have created.

▪Arguments: N-1 means that the function works with an index, and this index starts with 0.
- You will have to calculate the regular number minus one to get the last available index number.
- For example, you may have two Cue Lists, which are normally written as 1 and 2. Since it is a zero-based index, they are 0 and 1 instead.

▪Address Space: The table below includes Containers, Methods, Arguments and additional comments for more information, which are indicated with //

▪Feedback: In general, building OSC user interfaces without expecting and including Feedback from MADRIX 5 is easier than building them with Feedback from MADRIX 5.

Example

▪Address: /Output/Master
Valid Range Of Integer Arguments: (From) 0 (To) 255

Address Space

Notes

▪FeedbackAll - Is a single command to initially sync all available functions with the client once in order to update the values of the client with the current values of the MADRIX 5 server. It is an initialization.
- Is sent automatically by MADRIX 5 once if the connection, including Feedback, has been established successfully.
[TouchOSC supports this message, since it is useful and important to start MADRIX 5 first, and then TouchOSC, since this will ensure that the connection and sync work successfully right away.]
- Otherwise, Feedback usually works after a value has been changed on the MADRIX 5 user interface in order to send out data at least once.

TouchOSC Examples

Notes:

▪In TouchOSC, do not activate Messages > OSC > Feedback, but only Receive. Otherwise, you could create an endless feedback loop!

▪While TouchOSC is opened, you will probably not be able to find MIDI devices in MADRIX 5, due to a restricted or exclusive access from TouchOSC.

Troubleshooting

▪You can use the Logfile for troubleshooting as it will include many messages regarding OSC.
- Learn more »Tools

▪One such message in the Logfile is: 'The OSC sender has subscribed to this session and will get feedback.' It confirms that the client has successfully connected and registered this session with the server to receive feedback.