X AIR Mixer OSC Document (fw 1.11) 1/4
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
/xremote
None
Triggers server to send all
seconds.
1.3 set single
<OSC path-
name>
<string|int|float|blob
Sets the value of a console
1.4 get single
<OSC path-
name>
None
Requests the value of a console
1.5 subscribe
/meters
<string id>
Results in regular updates to batch
subscriptions"
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
request
parameter
parameter
to meter
values
formatted
parameter
formatted
parameter
value>
<int chnmeterid,
optional>
parameter changes to maximum
eight active clients. Timeout is 10
parameter, if it exists and value is
in range.
parameter. If it exists, new value is
echoed back by server
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
X AIR Mixer OSC Document (fw 1.11) 2/4
Operation
OSC address
Parameters
Comments
1.0 info
/info or
<string server_version>
<string device_version>
Name=value pair strings e.g.
1.1 status
/status
<string status>
Status should be “active” or
dependent
1.3
parameter
<OSC path-
<string|int|float|blob
Echoes the value of a parameter in
1.5
values
<client-
<blob data>
Blob contains meter data (signed
Server messages
request
request
set single
1.4
get single
subscribe
to meter
/xinfo
formatted
parameter
name>
specified id>
(/xinfo: <sting
ip_address>)
<string device_name>
<string device_model>
<string ip address>
<string server name>
..
value>
“device_version=1.2”. First four are
defined, and required. Further args
are implementation dependent
“standby” depending on whether
server is currently able to fulfil
subscriptions. IP address of the form
“192.168.2.1”. Server name is to
uniquely identify this console.
Further args are implementation
response to a get, set or fulfilment of
single parameter subscription, e.g.
/ch/01/mix/fader
integer 16 bit, resolution 1/256 dB)
as single binary blob
Type rules (get/set parameter)
• parameters must be big-endian and 4-byte aligned/padded, as per OSC specification
• float parameters must be in range 0.0 – 1.0
• integer parameters are signed 32-bit values
• boolean parameters will map to OSC integer type
• strings must be null-terminated
Meter subscriptions
meter subscriptions are used to request a set of meter values,e.g.:
/meters ,si “/meters/0” 8 (meterID ,oscvalues <string> <integer>)
Binary OSC message:
2f 6d 65 74 65 72 73 00 2c 73 69 00 2f 6d 65 74 ; /meters.,si./met
65 72 73 2f 30 00 00 00 00 00 00 08 ; ers/0.......
… returns 8 channel meters (pre-fader l/r, gate and comp gain reduction, post-fader l/r
meters, gate key, comp key) of channel 9:
Loading...