AIR-Series OSC Documentation

ManualsBrandsMidas ManualsDigital Stagebox Mixers12-Input Digital Mixer for iPad/Android Tablets with 4 PRO Preamps, 8 Line Inputs, Integrated Wifi Module and USB Stereo Recorder

Table Of Contents

X AIR Mixer Series Remote Control Protocol
- 1. Description
- 2. Client messages

X AIR Mixer OSC Document (fw 1.11) 1/4

X AIR Mixer Series Remote Control Protocol

(firmware 1.11 or higher)

1. Description

The X AIR mixers are using a communication protocol that is compatible to standard OSC with MUSIC

Group specific extensions (e.g. parameter enquiry, subscriptions).

OSC packets are received on UDP port 10024 and replies are sent back to the requester's IP/port.

The corresponding Parameters.txt file contains all relevant details about OSC paths and

parameter ranges.

2. Client messages

Operation

OSC address

Parameters

Comments

1.0 info

request

/info or /xinfo

None

Server responds with /info or

/xinfo message

1.1 status

request

/status

None

Server responds with /status

message

1.2 remote

request

/xremote

None

Triggers server to send all

parameter changes to maximum

eight active clients. Timeout is 10

seconds.

1.3 set single

parameter

<OSC path-

formatted

parameter

name>

<string|int|float|blob

value>

Sets the value of a console

parameter, if it exists and value is

in range.

1.4 get single

parameter

<OSC path-

formatted

parameter

name>

None

Requests the value of a console

parameter. If it exists, new value is

echoed back by server

1.5 subscribe

to meter

values

/meters

<int chnmeterid,

optional>

Results in regular updates to batch

of meter values as a single binary

blob, to OSC address <id>. Meter

values are signed integer 16 bit,

resolution 1/256 dB

see description for "Meter

subscriptions"

Summary of content (4 pages)

PAGE 1
X AIR Mixer Series Remote Control Protocol (firmware 1.11 or higher) 1. Description The X AIR mixers are using a communication protocol that is compatible to standard OSC with MUSIC Group specific extensions (e.g. parameter enquiry, subscriptions). OSC packets are received on UDP port 10024 and replies are sent back to the requester's IP/port. The corresponding Parameters.txt file contains all relevant details about OSC paths and parameter ranges. 2. Client messages Operation 1.0 info request 1.
PAGE 2
Server messages Operation 1.0 info request OSC address Parameters Comments /info or /xinfo Name=value pair strings e.g. “device_version=1.2”. First four are defined, and required. Further args are implementation dependent 1.1 status request /status 1.3 set single 1.4 get single parameter 1.
PAGE 3
List of Meter IDs: /meters/0 CHANNEL: 8 channel meters (pre-fader l/r, gate and comp gain reduction, post-fader l/r meters, gate key, comp key) -> returns one integer size value and 8 short signed integer values (16 bit) as single binary blob /meters/1 ALL CHANNELS: 16 mono + 5x2 fx/aux + 6 bus + 4 fx send (all pre) + 2 st (post) + 2 monitor -> returns one integer size value and 40 short signed integer values (16 bit) as single binary blob /meters/2 ALL INPUTS: 16 mic, 2 aux, 18 usb -> retur
PAGE 4
/meters/7 AUTOMIX GAINS: 16 gains (auto mixer) -> returns one integer size value and 16 short signed integer values (16 bit) as single binary blob /meters/8 DCAS: 4 dcas -> returns one integer size value and 4 short signed integer values (16 bit) as single binary blob /meters/9 RECORDER: 2 record, 2 play -> returns one integer size value and 4 short signed integer values (16 bit) as single binary blob Snapshot operations • The first "name" or "index" values are put in the temporary buffer and may be use