Create MIDI controller map
create_midi_mapBuild a MIDI controller preset for a supported device: create a MIDI input node and a bind table, optionally auto-bind faders/knobs to a target COMP's custom parameters.
Instructions
HARDWARE-GATED SCAFFOLD. Build a MIDI controller preset for a supported device (apc_mini / launchpad / midi_mix / nanokontrol / generic): creates a midiinCHOP + a labeled bind Table DAT, and optionally auto-binds faders/knobs to a target COMP's numeric custom parameters. Explicit bindings can override or supplement the preset. CC/note numbers are best-effort from published MIDI charts and MUST be validated with real hardware — actual assignments depend on device firmware. This tool is HELD FROM RELEASE until hardware validation is complete. For one-at-a-time MIDI learn of a single control, use learn_control instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| parent_path | No | COMP to create the MIDI map inside. | /project1 |
| name | No | Name for the MIDI In CHOP node created under parent_path. | midi_map |
| device | No | Controller preset. Each preset embeds a best-effort CC/note map for that device (UNVERIFIED — real numbers depend on firmware; validate with hardware). 'generic' builds a bare MIDI In + a template bind table with no preset. | nanokontrol |
| target | No | COMP whose custom numeric params/cues the preset auto-binds faders/knobs onto. Faders bind to the first N float/int custom pars; pads look for matching cues. Auto-binding is best-effort and hardware-gated. | |
| bindings | No | Explicit control→param/cue overrides. Applied after the preset auto-map. Omit to rely entirely on the device preset's default map. |