Use case · Soundcraft Ui

The Ui already has a footswitch input. This is what it can’t do.

The Ui24R takes a footswitch, and for simple jobs that is the right answer. This is for when you want several things to happen at once, held rather than latched, with the console’s real state on an LED.

Console: Soundcraft Ui12 / Ui16 / Ui24R
Gesture: Hold
Template: vocal_talk_mode

The moment this fixes

The console’s own footswitch input covers a fixed set of functions, one at a time.
Nothing tells you whether the action landed — there is no feedback on a contact-closure switch.
You are stood on a stage and the tablet running the console is by the drummer.

What happens when you step on it

You press
The pedal captures current values and applies every action in the mapping — for example lifting your channel and muting two FX at once.
The console confirms
State comes from the Ui’s own WebSocket stream, so the LED reflects the desk rather than the pedal’s hopes.
You release
Every captured value is written back.

The mapping

This is the shipped vocal_talk_mode template — Hold = Talk Mode (boost + FX mute, restore). Templates are expanded into concrete actions when you save them, so what runs on the pedal is plain actions, not a hidden abstraction.

json

{
  "template": "vocal_talk_mode",
  "input": 1,
  "event": "hold",
  "mixer": "ui",
  "actions": [
    { "op": "mix.delta", "target": "ch.5.fader", "delta": 0.08, "capture": true },
    { "op": "mix.set",   "target": "fx.1.mute",  "value": 1 }
  ],
  "onRelease": "restore"
}

Paste into the pedal’s web page, or build it with the template picker.

What the LED tells you

Confirmed
The console reported the new value back. The change is really in the mix.
Pending
Sent, not yet acknowledged. Retrying up to three times.
Failed
No acknowledgement after the retries. A fast red flutter, so you know within a second.
Dark
No connection to the console, so the pedal makes no claim about state at all.

When the network misbehaves

The Ui connection is an HTTP snapshot followed by a WebSocket. If the socket drops, feedback LEDs go dark rather than showing a value the pedal can no longer verify, and the pedal reconnects on its own.

Questions

Which Ui parameters are supported?

Channel 1–16 faders, channel 1–16 mutes, and FX 1–4 mutes. That is the current address map — it is not the full console surface, and we would rather say so than imply otherwise.

Should I just use the Ui24R’s own footswitch input?

For a single latching function, yes — it is free and it is built in. Use this when you want multi-action mappings, hold-and-restore behaviour, or an LED that tells you the console really did it.

Is this an official Soundcraft integration?

No. Soundcraft does not publish a stable public API for this, so it is an integration we maintain and test rather than a vendor-supported interface.

Build one this weekend.

A dev board, a footswitch, and about an hour.

Build yours How it works