Behringer x32: Difference between revisions

From The Munich Maker Lab's Wiki
Jump to navigation Jump to search
(Created page with "We got some new overkill audio equipment, so we put some mqtt into it :D == Protocol == It has a proprietary network interface used by the Behringer control so...")
 
Line 8: Line 8:


There are some simplified commands like 'volume up' for easy use, and the possibility to directly bridge to the x32's protocol. The x32-protocol also uses paths, so you can just append the x32-path to the topics mumalab/audio/x32/set or mumalab/audio/x32/get to set or get arbitrary paths.
There are some simplified commands like 'volume up' for easy use, and the possibility to directly bridge to the x32's protocol. The x32-protocol also uses paths, so you can just append the x32-path to the topics mumalab/audio/x32/set or mumalab/audio/x32/get to set or get arbitrary paths.
(For now, this only works for single float values and is mostly untested!)
You can send it pure json and get back json


=== Topics ===
=== Topics ===
Line 20: Line 20:
|| increase or decrease the master volume in 5% increments
|| increase or decrease the master volume in 5% increments
|-
|-
| mumalab/audio/x32/set/… || float or int || set path of mixing table to a specific value
| mumalab/audio/x32/set/… || json || set path of mixing table to a specific value
|-
|-
| mumalab/audio/x32/get/… || "get" || replies value of path in the same topic
| mumalab/audio/x32/get/… || "get" || replies value of path as json in the same topic
|-
|-
|}
|}

Revision as of 21:37, 11 August 2016

We got some new overkill audio equipment, so we put some mqtt into it :D

Protocol

It has a proprietary network interface used by the Behringer control software. It was reverse engineered, the mappings can be found here: File:UNOFFICIAL X32 OSC REMOTE PROTOCOL (1).pdf.

We use this python library to interface with it.

There are some simplified commands like 'volume up' for easy use, and the possibility to directly bridge to the x32's protocol. The x32-protocol also uses paths, so you can just append the x32-path to the topics mumalab/audio/x32/set or mumalab/audio/x32/get to set or get arbitrary paths. You can send it pure json and get back json

Topics

Topic Values Description
mumalab/audio/x32/command "volume up"

"volume down"

increase or decrease the master volume in 5% increments
mumalab/audio/x32/set/… json set path of mixing table to a specific value
mumalab/audio/x32/get/… "get" replies value of path as json in the same topic