Compatibility

What it talks to, and what it doesn’t.

Two consoles are genuinely supported. Everything else on this page is listed so you can rule it out quickly rather than discovering it after you have bought a board.

Console	How it connects	Status	What works
Behringer X32 familyBehringer	OSC over UDP, port 10023	Supported	Channel faders and mutes, bus and FX sends, and any parameter you can address by OSC path. Live state is read back and cached, so the pedal knows what the console is actually doing. Subscribes with /xremote and refreshes every 9 seconds; the console must be reachable on the same network. OSC path details are community-documented rather than vendor-guaranteed, so they are verified per firmware version.
Midas M32 familyMidas	OSC over UDP, port 10023	Expected to work, untested	The M32 shares the X32 control protocol, so the same driver applies. We have not tested one, so we will not claim it as supported until we have. No M32 has been through our test matrix yet. Tell us if you run one.
Soundcraft Ui12 / Ui16 / Ui24RSoundcraft	HTTP snapshot then socket.io WebSocket, port 80	Supported	Channel 1-16 faders, channel 1-16 mutes and FX 1-4 mutes. Initial state comes from the console snapshot, then updates stream over the WebSocket. The address map covers the channels and FX mutes listed above, not the full console surface. Soundcraft does not publish a stable public API for this, so it is an integration we maintain rather than a supported vendor interface.
Behringer X Air (XR12/16/18) and Midas MR18Behringer / Midas	OSC over UDP	Being investigated	— No driver exists yet. These consoles are the most requested next target and the protocol is close to the X32, but nothing has been written or tested.
Behringer WING, Allen & Heath Qu / SQ, YamahaVarious	—	Not supported	— No driver, and none currently planned.

Tested versions

Things the protocol layer can’t promise

The X32 OSC surface is community-documented. Behringer describes remote control, but the parameter paths people rely on are largely community knowledge. That means a console firmware update can move something without warning, which is exactly why the version matrix matters.
Soundcraft does not publish a stable public API. The Ui integration talks to the same interface the browser UI uses. It works, it is maintained, and it is not a vendor-supported contract.
Two consoles at once, three addresses each. The pedal holds two active console connections, each with up to three candidate addresses that can be tied to a specific Wi-Fi network — so a rig that moves between a rehearsal room and a venue can find the right desk on its own.

What an action can do

Mappings are built from these operations. Two of them are declared in the schema but not yet implemented, and they are marked as such rather than quietly listed alongside the rest.

mix.set
Write a value to a console parameter.
Works
mix.delta
Offset a value from its captured baseline.
Works
mix.restore
Write back the value captured at press time.
Works
mix.toggle
Flip a parameter, with optional capture and learned offset.
Works
led.*
Drive the LED directly — on, off, toggle, blink.
Works
delay
Wait between actions inside one binding.
Works
midi.cc / midi.note
Not implemented. The action exists in the schema but does nothing yet.
Not implemented
ws.send
Not implemented. Raw message sending is a stub.
Not implemented

Not in the product

Things people reasonably expect from a mixer footswitch that CueStomp does not do today:

Scene and snapshot recall. No template, no tested path. A guarded recall is the obvious next thing to build, but it does not exist yet.
Tap tempo. Not implemented.
MIDI output. The pedal is a network device; it does not send MIDI.
More than six footswitch inputs. Six is the hard ceiling on every board profile.

Running an X Air or MR18?

It is the most requested next console and the protocol is close to the X32 — but nothing is written yet. With one person building this, knowing who is waiting is genuinely what decides the order.

Add your console