MIDI Implementation
Deepfield accepts controller MIDI for parameter control and host-integrated program recall. MIDI output is not required for the standard effects workflow.
Controller binding types
The Automation Manager supports these MIDI binding types:
| Type | Description |
|---|---|
| Off | No MIDI controller assignment. |
| CC | Standard 7-bit MIDI Continuous Controller. |
| High Res CC | 14-bit paired CC using CC 0–31 as MSB and CC+32 as LSB. |
| Pitch Bend | Channel Pitch Bend message. |
| Channel Pressure | Channel pressure/aftertouch message. |
Bindings can be Omni or restricted to a specific MIDI channel.
MIDI Learn
Arm Learn for one automation/control row and move the desired controller. The next supported CC, Pitch Bend or Channel Pressure message is captured. The selected channel policy is preserved.
Mod wheel
Mod wheel is standard CC 1. Select CC and controller 1; no special Mod Wheel binding type is needed.
Program Change / Variants
Deepfield does not parse MIDI Program Change in the normal per-block MIDI controller path. Instead it exposes 128 native plugin programs to the host:
| Host program | Deepfield meaning |
|---|---|
| 0 | Default / Base |
| 1–127 | Saved Variants in stored order |
A DAW/controller setup that maps MIDI Program Change to the plugin's native program selection can therefore recall Variants without adding MIDI scanning work to the normal graph processing path.
Storage
MIDI controller assignments are stored with the DAW/plugin instance state, not in portable .p00tch files. This prevents a shared patch from replacing the receiving user's personal hardware mapping. MIDI Learn being armed is temporary runtime state and is not restored.
Variant definitions, their order and the optional startup Variant are .p00tch content; the currently selected Variant/native host program is DAW-instance state. Program Change messages themselves are transient events.
See Automation and MIDI for the full Automation Manager workflow and its persistence rules.