M-VAVE FM-1: MIDI CC, NRPN and OSC map¶
The M-VAVE FM-1 as named OSC addresses — 3 SysEx commands — ready to use from Claude (MCP), SuperCollider, Sonic Pi, TouchDesigner or any OSC app via osc-bridge.
| Device | M-VAVE FM-1 |
|---|---|
| Vendor | M-VAVE |
| OSC prefix | /fm1 |
| Source | 📘 From the manufacturer's documentation |
| Firmware | zp12-2.5 |
| Revision | zp12 2.5 (alternative firmware by zvenson) |
| Upstream | vendor-doc |
| Driver file | devices/m-vave/fm-1.vendor.fw-zp12-2.5.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.
Other variants of this device: fm-1.vendor.fw-15, fm-1.vendor.fw-16, fm-1.vendor.fw-386dx-1.0.2, fm-1.vendor.fw-amb-1.3, fm-1.vendor.fw-beetle-1.4.25, fm-1.vendor.fw-bunker-1.0.0, fm-1.vendor.fw-bytemania-1.2.0, fm-1.vendor.fw-carnac-0.9.3, fm-1.vendor.fw-chipbox-1.2.4, fm-1.vendor.fw-choralroot-0.26.1, fm-1.vendor.fw-chord-0.3, fm-1.vendor.fw-clipper-1.1-experimental, fm-1.vendor.fw-coralflower-0.5, fm-1.vendor.fw-cs1-2026.10.22, fm-1.vendor.fw-ctl-1.0, fm-1.vendor.fw-cutador-1.2.1, fm-1.vendor.fw-dinghy-0.4, fm-1.vendor.fw-drift-0.8, fm-1.vendor.fw-dub-1.3.0, fm-1.vendor.fw-duell-1.0, fm-1.vendor.fw-emb-1.5.2, fm-1.vendor.fw-etch-1.61, fm-1.vendor.fw-fart-1.1.0, fm-1.vendor.fw-felucca-1.6.1, fm-1.vendor.fw-felucca-salt-0.9-salt14, fm-1.vendor.fw-felucca8-1.6.1-and-sequences, fm-1.vendor.fw-fimba-0.6.1, fm-1.vendor.fw-flyfish-1.0.1-4e5efb8, fm-1.vendor.fw-fm106-beta4, fm-1.vendor.fw-fm1gm-1.0.2, fm-1.vendor.fw-fmel-1.0, fm-1.vendor.fw-fmini-1.8.0, fm-1.vendor.fw-fomajam-0.1.6, fm-1.vendor.fw-fomni-0.4, fm-1.vendor.fw-frasil-1.0, fm-1.vendor.fw-frodhes-0.9.4, fm-1.vendor.fw-fumi-1.1.0, fm-1.vendor.fw-gammawave-1.0-gw, fm-1.vendor.fw-ghoulbox-2.3.2, fm-1.vendor.fw-golana-1.2, fm-1.vendor.fw-golanadz-0.1.0-beta, fm-1.vendor.fw-grimm-1.0, fm-1.vendor.fw-hera-1.1, fm-1.vendor.fw-hortator-0.23.3, fm-1.vendor.fw-hyp1-1.5.54, fm-1.vendor.fw-jangada-1.0.1, fm-1.vendor.fw-jiant-0.9.9-beta4a-813869d, fm-1.vendor.fw-kawa-0.5, fm-1.vendor.fw-ketch-0.1-beta, fm-1.vendor.fw-loom-0.7, fm-1.vendor.fw-maku-1.0, fm-1.vendor.fw-mc1-1.2.0, fm-1.vendor.fw-melodee-1.4.5, fm-1.vendor.fw-min1-0.2.1, fm-1.vendor.fw-minitone-1.0.2, fm-1.vendor.fw-modelar-0.3, fm-1.vendor.fw-monk-0.9.1, fm-1.vendor.fw-morpheus-1.0.0, fm-1.vendor.fw-mutable-1.0, fm-1.vendor.fw-mycelium-1.0-test, fm-1.vendor.fw-niagara-0.2, fm-1.vendor.fw-nmsfm-0.5, fm-1.vendor.fw-noizdemons-666, fm-1.vendor.fw-obervave-3.0.1, fm-1.vendor.fw-open-14, fm-1.vendor.fw-opn1-2.0.0, fm-1.vendor.fw-orbit-0.7.1, fm-1.vendor.fw-pigeon-0.5.0-beta.1, fm-1.vendor.fw-polly-0.5, fm-1.vendor.fw-purplemonkey-0.11, fm-1.vendor.fw-quest-38, fm-1.vendor.fw-rainbow-1.1.5-rb, fm-1.vendor.fw-shineon-3.0.1, fm-1.vendor.fw-sid-0.1, fm-1.vendor.fw-sid1-1.0.0, fm-1.vendor.fw-sidou-0.3.1, fm-1.vendor.fw-skiff-1.4, fm-1.vendor.fw-sloop-2.8.1, fm-1.vendor.fw-sloop-alg-alg05-test, fm-1.vendor.fw-sloop-banks-2.5-b28-test, fm-1.vendor.fw-sloop-floyd-2.4, fm-1.vendor.fw-sloopdx-4.0, fm-1.vendor.fw-tessera-2.0.1, fm-1.vendor.fw-tonitor-2026.10.23, fm-1.vendor.fw-tribe-0.3-beta, fm-1.vendor.fw-tuna-1.0-fbc56d3, fm-1.vendor.fw-unholy-0.2.3, fm-1.vendor.fw-vector37-0.3.2, fm-1.vendor.fw-waveloop-1.0.5.2-midi23, fm-1.vendor.fw-winampfm-0.12, fm-1.vendor.fw-x0x-1.1.0, fm-1.vendor.fw-x0xrmx-1.1.0, fm-1.vendor.fw-zen-1.2.
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/m-vave/fm-1.vendor.fw-zp12-2.5.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 fm1: ask “what can the M-VAVE FM-1 do?” and it reads this map with list_routes. See the MCP guide.
SysEx commands (3)¶
| OSC address | Arguments |
|---|---|
/fm1/program |
program: u7 |
/fm1/system/info |
|
/fm1/system/identify |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /fm1/note/on <note> <velocity>, /fm1/cc/<number> <value>, /fm1/pitchbend <0-16383>, /fm1/program_change <n>.
Limitations¶
zp12 2.5 by zvenson (GPL-3.0), a drum-machine firmware for the FM-1. no CC, no channel filter; SLOOP editor doc in web/ is a leftover, not implemented. Channels: omni: any channel, USB and TRS MIDI IN; notes 36-67 play pads A1-D8 with velocity. Pitch bend: none. Aftertouch: none. Clock: none: F8/FA/FB/FC queued by the platform but ignored; internal tempo only. MIDI out: none from the app. NRPN: none. SysEx `F0 pack7(00 59 cmd len24 body chk) F7`: M-UPGRADE vendor update protocol (installers, hub): cmd 0x11 handshake answers the package identity; F0 22 24 35 7F F7 starts the pulled update. SysEx `F0 22 24 35 7D F7`: soft key: reboot into the bootloader. SysEx `F0 pack7(7D 'Z' 'P' cmd addr:3 len:2 data sum) F7`: zp12 link v5 for the web tools: 1 HELLO ("zp12 X.Y"), 2 READ, 3 ERASE, 4 WRITE flash, 5 HOLD, 6 REBOOT, 7 RELOAD, 8 ASSIGN pad, 9 PADS. SysEx `F0 7D 46 4C`: absent: no Felucca editor protocol, no INFO reply. SysEx `F0 43`: absent: no raw DX7 SysEx parser. Identity: vendor identify FM-1_97Y for release X.Y (FM-1_97+minor, 2.5 -> FM-1_975; dev FM-1_970; tools/build.py:50,288), rescue FM-1_000; link HELLO "zp12 X.Y"; USB product "zp12 FM-1" (usb.c:255). It reads no CC.
Try it in your browser
Play a virtual FM-1 with any of its community firmwares: M-VAVE FM-1.