Motu MTP AV (WIP) MIDI CC chart, NRPN and OSC map¶
The Motu MTP AV (WIP) MIDI implementation: 2 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | Motu MTP AV (WIP) |
|---|---|
| Vendor | MOTU |
| OSC prefix | /motu_mtp_av_wip |
| Source | 🎛️ Derived from an Electra One community preset |
| Revision | per Electra preset |
| Upstream | electra-preset |
| Driver file | devices/motu/motu_mtp_av_wip.json |
Not tested on the device yet
This driver comes from documentation or community data and has not been checked on real hardware. If you own one, a quick test and a pull request promoting it helps everyone — see CONTRIBUTING.
How do you control it?¶
Find the MIDI ports, then start the bridge with this driver:
osc-bridge detect # prints the ready-to-run line for what is plugged in
osc-bridge run --device devices/motu/motu_mtp_av_wip.json --out-port <N> --in-port <M>
Then send OSC to 127.0.0.1:7777, for example:
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as motu_mtp_av_wip: ask “what can the Motu MTP AV (WIP) do?” and it reads this map with list_routes. See the MCP guide.
SysEx commands (2)¶
| OSC address | Arguments |
|---|---|
/motu_mtp_av_wip/remap |
val: u7 |
/motu_mtp_av_wip/mute |
val: u7 |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /motu_mtp_av_wip/note/on <note> <velocity>, /motu_mtp_av_wip/cc/<number> <value>, /motu_mtp_av_wip/pitchbend <0-16383>, /motu_mtp_av_wip/program_change <n>.
Limitations¶
Imported from an Electra One community preset. The mapping reflects the preset author's editorial choices: parameter naming, ranges, and which params are exposed. Untested on hardware in this repo.
Frequently asked questions¶
Can an AI agent like Claude control the Motu MTP AV (WIP)?
Yes: SynthHub's hosted MCP server knows the Motu MTP AV (WIP)'s MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.