MIDI Mapping & Automation
The MIDI & Automation panel lets you map hardware MIDI controls, keyboard keys, and DAW automation to live performance actions and effect parameters.
This is where you configure setlist switching, preset triggers, input/output trim control, and custom mappings to effect parameters.
Opening MIDI mapping
- Click the MIDI button in the footer bar.
- The MIDI & Automation modal opens.
The modal has three tabs:
| Tab | What it does |
|---|---|
| Mappings | Configure MIDI control mappings and target parameters |
| Keyboard | Map computer keyboard keys to slots |
| MIDI Log | View incoming MIDI events for troubleshooting |
Default slots
Default slots are always available and cannot be deleted. You can still change their MIDI mapping and keyboard mapping.
| Slot | Target | Typical use |
|---|---|---|
| Setlist Preset 1-8 | setlist.preset1 ... setlist.preset8 | Trigger specific slots in the active setlist |
| Bank Up | setlist.bankUp | Move to the next setlist |
| Bank Down | setlist.bankDown | Move to the previous setlist |
| Select Bank | setlist.bankSelect | Jump directly to a setlist by bank number |
| Input Level | global.inputTrim | Control global input trim |
| Output Level | global.outputTrim | Control global output trim |
Bank behavior
- A bank is a setlist.
- Bank Up/Bank Down changes the active setlist and resets the setlist cursor to the first slot.
- Select Bank expects a bank number value (0-127), typically from MIDI CC.
- Bank changes do not automatically load a preset. Use Setlist Preset 1-8 to trigger the preset slot you want in that bank.
Custom slots
Custom slots let you map almost any target parameter.
- In Mappings, click + Add Custom Slot.
- Click Target on the new row.
- Set a Label.
- Choose a Target parameter.
- Click Apply.
Target choices include:
- Global controls (for example
global.inputTrim) - Setlist controls (for example
setlist.bankSelect) - Effect parameters (for example
node.amp_nam.inputGain,node.reverb_room.mix)
Up to 16 custom slots are supported.
MIDI Learn workflow
Use Learn to capture the next incoming MIDI control message.
- Click Learn on a slot.
- Move a control on your MIDI device (knob, switch, pad, pedal, etc.).
- The slot stores that MIDI event mapping.
If a row shows Test, you can fire that trigger action immediately from the UI.
MIDI Log
Use MIDI Log to verify that your device is sending events.
- Open the MIDI Log tab.
- Enable MIDI logging.
- Move your MIDI control and confirm event entries appear.
This is the fastest way to diagnose channel/controller mismatches before remapping.
Tips
- Start by mapping only a few critical live actions: Bank Up, Bank Down, and one or two Setlist Preset slots.
- For smooth mixer rides, map expression pedals to continuous targets (for example
Input Levelor custom effect mix parameters). - If a mapping does not react, confirm incoming events in MIDI Log, then remap with Learn.