Use case · X32
Take the solo. Give the fader back.
Eight bars where you need to be louder, and nobody at front of house who can read your mind. Hold the pedal for the solo, release, and your channel goes back to exactly where it was.
- Console
- Behringer X32 family
- Gesture
- Hold
- Template
solo_hold_boost
The moment this fixes
- Solos get buried because nobody knew they were coming.
- A fixed boost you set at soundcheck is wrong the moment the engineer re-balances.
- Turning yourself up and forgetting to turn back down is worse than being quiet.
What happens when you step on it
You press
The pedal reads your channel’s current fader position, stores it, and adds your boost on top.
The console confirms
Green means the fader really moved. Amber means it is still asking.
You release
It writes back the captured value — not a preset number. If the engineer trimmed you 2 dB during the solo, that trim survives.
It learns
That 2 dB correction is remembered as an offset, so your next press lands where the mix actually wants you.
The mapping
This is the shipped solo_hold_boost template — Hold = Solo Boost (fader + offset, restore). Templates are expanded into concrete actions when you save them, so what runs on the pedal is plain actions, not a hidden abstraction.
{
"template": "solo_hold_boost",
"input": 1,
"event": "hold",
"actions": [
{
"op": "mix.delta",
"target": "/ch/03/mix/fader",
"delta": 0.10,
"capture": true,
"learnOffset": true
}
],
"onRelease": "restore",
"feedback": {
"kind": "boost",
"target": "/ch/03/mix/fader"
}
}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
Restore is the safety-critical half. If the release write is not acknowledged, the pedal retries and then reports failure rather than assuming your fader came back down. It also refuses to restore a stale value: if the engineer moved the fader during your hold, that becomes the new baseline instead of being overwritten.
Questions
How much boost should I use?
Start small — around 3 to 4 dB of travel. The learned offset will drag it toward whatever the mix actually wants after a few songs.
Does this fight the engineer?
Deliberately not. Front of house always wins: any value they set cancels a pending write and becomes the baseline the pedal restores to.
Can I boost more than one channel?
Yes, a single binding can carry up to four actions — for example your vocal and your instrument together.
Build one this weekend.
A dev board, a footswitch, and about an hour.