RME Audio AVB Tool User Manual page 44

Half-rack madi-avb converter with outstanding analog connectivity
Hide thumbs Also See for AVB Tool:
Table of Contents

Advertisement

Request:
curl --header "Content-Type: application/json" --request POST --data
'{"osc":{"schema":null}}' avb-tool.local/api/v2/self
Response:
{
 
"osc": {
 
"schema": {
 
"osc": {
 
"version": null,
 
"schema": []
 
},
 
"device": {
 
"entity_id": null,
 
"entity_model_id": null,
 
"entity_capabilities": null,
 
"entity_name": null,
 
"vendor_name": null, ①
 
"model_name": null,
 
"firmware_version": null,
 
"group_name": null,
[... continues]
① "vendor_name" Object
This schema can then be used to identify the possible parameters, for example the vendor name.
Sending an empty value null triggers a response with the current value of the requested object.
The first two levels of the schema ({"osc": {"schema": {...}}}) must be omitted. Only the
encapsulated objects (device, input, output, routing etc.) are used.
To request the "vendor_name" object of the connected device, we run the following command. It is here
outlined in more detail.
Request of vendor name:
curl \ ①
 --header "Content-Type: application/json" \ ②
 --request POST \ ③
 --data '{"device": {"vendor_name": null }}' \ ④
 avb-tool.local/api/v2/self ⑤
① cURL command to send an HTTP POST request
② header: application/json
③ request type "POST"
④ JSON object sent to the device, 'null' to get current value
⑤ URL or IP of the device on the network with path to API
39 | 8.4. Remote Control Overview
RME AVB Tool User's Guide

Advertisement

Table of Contents
loading

Table of Contents