Sound Control Protocol for ew D1

SSC Developer‘s guide for evolution wireless D1 | 17/56
General SSC Address Schema
An alternative representation of the same SSC Reply in a format that unbundles the SSC Address
Tree into an array of SSC Addresses is:
RX: { "osc": { "schema": [
{ "out1": { "xlr1": {} }},
{ "out1": { "xlr2": {} }}
] }}
SSC Clients MUST be able to understand both bundled and unbundled Replies.
Note that the responses are empty JSON objects if the address is an SSC Container for more ad-
dresses, JSON null if the address is an SSC Method Address.
The method /osc/schema may be called with a null parameter. This is equivalent to querying for the
root address schema.
The SSC Client is able to enumerate the complete SSC Address Space of the SSC Server by starting
with a query for the address root scheme { "osc": { "schema": null }}, and recursively que-
rying all the SSC Addresses where the replies point to SSC containers.
5.1.6 SSC Method parameter range reflection - /osc/limits
The /osc/limits method allows clients to query what kind of values and what range are accepted
by the server in an SSC Method call as parameter values. The response of the request is always a
JSON array containing a JSON object describing properties of the addressed SSC Method.
The property list is extensible for application-specific features as well as for revised versions of this
specification.
Currently defined optional properties are:
• type string "Number", "String", "Boolean", or "Container"
• min number minimum valid value
• max number maximum valid value
• inc number recommended user interface increment value
• units string String describing value units (preferably SI)
• desc string descriptive text, meant for display to the user
• option string array of all allowed options for the value
• option_desc string array with description text relating to the option values
The language for "units", "description", and "option_desc" MAY depend on /device/language, see
section 5.2.9.
Examples:
TX: { "osc": { "limits": [
{ "out1": { "xlr1" : { "level" : null }}} ] }}
RX: { "osc": { "limits": [
{ "out1": { "xlr1" : { "level" : [{
"type": "Number",
"min": -10,
"max": 18,
"inc": 3,
"units": "dB",
"desc": "output level"
}] }}} ] }}
TX: { "osc": { "limits": [ { "main_format": null } ] }}
RX: { "osc": { "limits": [ { "main_format" : [{
"type": "String",
"desc": "main output mode",
"option": [ "analogue", "digital" ],
"option_descr": [ "analogue", "digital AES3" ]
}] } ] }}
Similar as described for /osc/schema, the SSC Server may format the Method Replies in bundled
or unbundled representation of the SSC Addresses, and the SSC Client MUST be able to understand
either.