Behringer X32 / Midas M32 Control Software BETA

Controls Behringer X32 and Midas M32 consoles — full size, Compact, Producer, Rack, Core, M32R and M32C — over OSC on UDP port 10023, the same protocol X32-Edit uses. Fader levels in dB, relative fader moves for dials and +/- buttons, mutes and channel names. The handler subscribes to the console with /xremote, so the variables follow what the operator does on the surface.

Setup: protocol OSC, enter the IP of the console, leave the port on 10023 and leave Connection is Persistent unchecked — the handler holds its own socket. The console needs no setting: OSC is always on. Choose in the device settings which strips publish variables.

Variables written (prefix = sanitized device name), four per published strip:
{prefix}ch01_fader_db — fader in dB, one decimal (-inf at the bottom)
{prefix}ch01_fader_pos — fader position 0–100: the dB scale is not linear (0 dB sits at 75), so a panel fader or rotary follows this one
{prefix}ch01_mute (1 muted, 0 live), {prefix}ch01_name (the scribble strip)
Strip keys: ch01–ch32, auxin01–auxin08, bus01–bus16, dca1–dca8, main
{prefix}connected, {prefix}model, {prefix}console_name

Behringer X32 and Midas M32 consoles are remote controlled over OSC on UDP port 10023 — the protocol X32-Edit and the mixing apps use. This handler holds its own socket, subscribes with /xremote and mirrors fader, mute and name of the chosen strips into Fantago variables.

Connection

• Protocol OSC (over UDP), port 10023. Leave Connection is Persistent unchecked: the handler holds a socket of its own, because it also receives every change made on the console.
• The console needs no setting. Fantago and the console must reach each other both ways — the console answers to the port the request came from.
• On the first answer the handler reads the state of every published strip, and again whenever the console comes back after being unreachable.
• Only the commands sent from Fantago are logged. Log every message received adds the full trace for troubleshooting.
• Four variables per strip are published, for the groups chosen in the device settings (default: channels 1–32 and Main LR, 132 variables). Commands work on every strip, published or not.

Relative fader moves

Fader: Adjust starts from the level the console holds now, including a move just made on the surface, so a +/- button or a dial never makes the fader jump. Two units:

• dB — natural for buttons (+3 dB, −6 dB). From -inf a raise starts at −60 dB.
• % of the travel — the same feel over the whole range, like the console fader itself: use it for dials (1 % ≈ 0.4 dB around 0 dB).

Never go above caps a raise (for example at 0 dB); a fader already above it is left where it is.

Panel faders, rotaries and Stream Deck + dials

• Fader or rotary in value mode: action Fader: Set Position with position {{control_percent}} and position variable devicename_ch01_fader_pos.
• Rotary or dial in steps mode: action Fader: Adjust, unit %, adjust by {{control_delta}} — each step moves the fader from where the console holds it.

Integration via HTTP GET (device named "X32")

Integration via TCP/UDP Listener

Notes

• The console ignores a fader sent as an integer. Send Raw OSC Message follows the generic OSC rules (1 is an int, 1.0 or (f)1 a float): write (f) for faders.
• A name longer than 12 characters is cut, as on the console.
• Not covered yet: sends, scenes and snippets, EQ and dynamics, meters. Send Raw OSC Message reaches any of them.