> For the complete documentation index, see [llms.txt](https://manual.minimal.audio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.minimal.audio/current-manual/additional-settings/midi-learn.md).

# MIDI Learn

### Overview

This plugin supports native **MIDI Learn**, letting you map the knobs and sliders on your MIDI controller directly to plugin parameters with no DAW configuration required.

Mappings are saved with the plugin instance, so they recall with your project and persist across preset changes. You can also save them to a file for reuse, and set a default map that loads automatically with every new instance.

### Learning a Control

1. Right-click the knob or slider you want to control and select **Learn MIDI**.
2. Move a control on your MIDI controller. The parameter is now mapped and follows your hardware.
3. Repeat for any other parameters you want to map.

Closing the plugin window cancels a pending **Learn MIDI**.

### Editing a Mapping

Right-click a mapped control to change or clear its mapping:

* **Unlearn MIDI CC.** Removes the mapping. The menu shows which CC is assigned, for example **Unlearn MIDI CC 74**.
* **Relearn MIDI.** Reassigns the control to the next knob or fader you move.

### How Mappings Behave

* MIDI CCs respond on all channels (omni).
* Each parameter responds to a single CC. Learning a new CC on a parameter replaces its previous assignment.
* A single CC can drive several parameters at once. Learning the same CC on another parameter keeps both mappings.

### Saving and Loading MIDI Maps

Open the **Global Settings** menu and select **MIDI Map**:

* **Save MIDI Map.** Saves all current mappings to a `.ma_midimap` file.
* **Load MIDI Map.** Restores mappings from a previously saved file.
* **Restore default map.** Replaces the current mappings with your saved default map. Available once a default map has been set.
* **Clear MIDI Map.** Removes all mappings, showing a confirmation of how many will be removed.

MIDI maps are specific to each plugin, so a map saved with one Minimal Audio product can't be loaded into another.

### Using a Default MIDI Map

Open the **Global Settings** menu and select **MIDI Map → Set Default Map**. This makes the currently loaded map the default for every new plugin instance, so your controller always maps to the plugin the same way.

To remove the default, select **Clear MIDI Map**, then **Set Default Map** again to save an empty map as the default.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://manual.minimal.audio/current-manual/additional-settings/midi-learn.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
