Use case · X32

Kill the vocal FX while you talk.

Between songs your vocal is drowning in reverb tail and the room can’t make out a word. One stomp dries you out, another gives the wash back for the next tune.

Console: Behringer X32 family
Gesture: Hold, or tap to latch
Template: vocal_talk_mode

The moment this fixes

Reverb and delay that sound huge on a chorus turn speech into mush.
Reaching for a phone between songs is slow, visible from the floor, and puts your hands on the wrong device.
Asking the engineer over the wedge for “less verb, just for a sec” never lands in time.

What happens when you step on it

You press
The pedal captures the current FX send state, mutes the FX bus and lifts your mic slightly so speech carries.
The console confirms
The change is read back from the desk. Only then does the LED go green — it is showing the console’s state, not the pedal’s intention.
You release
Everything returns to exactly the values captured at press time, including any trim the engineer made in between.

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",
  "actions": [
    { "op": "mix.delta", "target": "/ch/01/mix/fader", "delta": 0.08, "capture": true },
    { "op": "mix.set",   "target": "/fx/1/mix/on",     "value": 0 },
    { "op": "mix.set",   "target": "/fx/2/mix/on",     "value": 0 }
  ],
  "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

If the Wi-Fi drops while you are holding, the pedal cannot confirm the restore. It retries, then flutters red rather than pretending the mix is back. The console keeps whatever it last acknowledged, so you are never left with a silently half-applied state — and you know to reach for the desk.

Questions

Does this mute the whole FX bus for everyone?

It mutes whatever you point it at. Muting the FX bus affects everything feeding it, so most bands target the FX sends on their own vocal channel instead. The config above is a starting point, not a fixed behaviour.

What if the engineer changes something while I am holding?

The pedal stands down. An inbound value that differs from what it asked for is treated as a human decision and the pending write is cancelled rather than fought.

Do I need the app for this?

No. This is a Core mapping, set up from the pedal’s own web page over your local network, with no account and no cloud.

Build one this weekend.

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

Build yours How it works