Use case · X32

Open the talkback without letting go of anything.

Whether it is a talkback mic to the band, a listen mic to the booth, or a channel you only want live for ten seconds — hold it open with your foot and let it close itself.

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

The moment this fixes

A permanently open talkback mic bleeds the whole stage into wherever it goes.
A latching switch you have to remember to turn off is how a private conversation ends up in the mains.
Mixing from the stage means your hands are already busy.

What happens when you step on it

You press
The pedal unmutes the channel you assigned and holds it open.
The console confirms
The LED tracks the console’s actual mute state. If the desk never applied the change, the light does not claim it did.
You release
The channel mutes again. Because release restores rather than toggles, a lost packet cannot leave the mic open in the “on” position.

The mapping

This is the shipped toggle_mute template — Tap = Toggle Mute. 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": "toggle_mute",
  "input": 2,
  "event": "hold",
  "actions": [
    { "op": "mix.set", "target": "/ch/12/mix/on", "value": 1, "capture": true }
  ],
  "onRelease": "restore",
  "feedback": {
    "kind": "toggle",
    "target": "/ch/12/mix/on",
    "requireConfirmed": true
  }
}

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

What the LED tells you

Confirmed
The console reports the mic is open. It really is live.
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

This is the mapping where fail-safe matters most. Release writes an explicit mute rather than toggling, and retries it — so a dropped packet cannot silently leave the mic open. If the retries fail, the LED flutters red instead of going dark, because “I could not close this” is something you need to know immediately.

Questions

Can I make it latch instead of hold?

Yes — bind it to tap instead of hold. Hold is recommended for anything you would regret leaving open.

Will the LED show the state if someone mutes the channel at the desk?

Yes. Feedback is driven by state read back from the console, so the light follows the desk regardless of who changed it.

Does the X32 have a dedicated talkback I should use instead?

It does, and if its routing suits you, use it. This is for when you want a specific channel, a specific destination, or a footswitch the console’s own talkback does not give you.

Build one this weekend.

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

Build yours How it works