Mappings, templates and actions

A mapping binds an event on a footswitch to up to four actions.

Events

Event	When it fires
press	The switch closes.
release	The switch opens.
tap	A press and release shorter than 250 ms.
doubleTap	Two taps within 320 ms.
holdStart	The switch has been down for 450 ms.
holdEnd	Released after a hold.

Contacts are debounced for 25 ms in firmware, so you do not need any hardware debounce circuitry.

Templates

Templates are the user-facing layer. Rather than asking you to write OSC paths, they ask what you want to happen and expand into concrete actions when you save.

Three ship today:

• solo_hold_boost — hold to lift a fader, release to restore it
• vocal_talk_mode — hold to boost a mic and mute FX, release to restore
• toggle_mute — tap to toggle a mute

Expansion happens in the browser when you save, so what runs on the pedal is plain actions. There is no hidden interpretation layer on the device, and you can always see exactly what a template turned into.

Actions

Action	What it does
mix.set	Write a value to a console parameter.
mix.delta	Offset a value relative to a captured baseline.
mix.restore	Write back the value captured at press time.
mix.toggle	Flip a parameter.
led.on / led.off / led.toggle	Drive the LED directly.
led.blinkStart / led.blinkStop / led.blinkToggle	Blink patterns.
delay	Wait, so a sequence can be staged.

midi.cc, midi.note and ws.send appear in the schema but are not implemented — they currently do nothing.

The three modifiers that make holds safe

capture reads the current value before changing it, and that captured value is what release restores. Without it, release would write a number chosen when you configured the mapping, undoing anything the engineer changed since.

learnOffset watches what happens during the hold. If the engineer moves the same control, the pedal records the difference and applies it next time, so you stop making them repeat the same correction.

invert flips the sense of a toggle, for consoles where “on” means the opposite of what you would expect.

Limits

A Core pedal holds three mappings and three feedback rules across six inputs, with one console connected. These are fixed array sizes in the firmware rather than licence checks — there is no fourth slot to unlock at runtime.