M-VAVE FM-1 (MC-1 1.2.0) MIDI CC chart, NRPN and OSC map¶
The M-VAVE FM-1 MIDI implementation: 21 CC, 3 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | M-VAVE FM-1 |
|---|---|
| Vendor | M-VAVE |
| OSC prefix | /fm1_mc1 |
| Source | 📘 From the manufacturer's documentation |
| Firmware | mc1-1.2.0 |
| Revision | MC-1 1.2.0 (alternative firmware by dspaudio) |
| Upstream | vendor-doc |
| Driver file | devices/m-vave/fm-1.vendor.fw-mc1-1.2.0.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 versions of the M-VAVE FM-1 (93)
stock firmware V15 · stock firmware V16 · 386DX 1.0.2 · AMB-1 1.3 · BEETLE 1.4.25 · Bunker Evolved 1.0.0 · Bytemania 1.2.0 · Carnac OS 0.9.3 · Chipbox 1.2.4 · ChoralRoot 0.26.1 · fm1-chord 0.3 · Clipper 1.1-experimental · CoralFlower 0.5 · CS-1 2026.10.22 · CTL-1 1.0 · Cut-A-Dor 1.2.1 · Dinghy 0.4 · DRIFT 0.8 · DUB-1 1.3.0 · DUELL 1.0 · Evander's Music Box 1.5.2 · ETCH 1.61 · Fart Machine One 1.1.0 · Felucca 1.6.1 · Felucca [Salt] 0.9-salt14 · Felucca 8 Patterns 1.6.1_and_sequences · FiMba-1 0.6.1 · Flyfish 1.0.1-4e5efb8 · FM-106 Beta4 · FM1-GM 1.0.2 · FMEL-1 1.0 · FMini-1 1.8.0 · FOMAJAM 0.1.6 · FoMni 0.4 · FRASIL 1.0 · Frodhes 0.9.4 · FuMi-1 1.1.0 · Pocket GammaWave 1.0-GW · GHOULBOX 2.3.2 · Golana 1.2 · Golana DZ Edition 0.1.0-beta · GR!MM 1.0 · HERA 1.1 · Hortator 0.23.3 · HYP-1 1.5.54 · Jangada 1.0.1 · JIANT FM 0.9.9-beta4a-813869d · KAWA 0.5 · Ketch 0.1-beta · LOOM-8 0.7 · MAKU 1.0 · Melodee 1.4.5 · MIN-1 0.2.1 · Mini-Tone 1.0.2 · MODELAR 0.3 · MONK-1 0.9.1 · MORPHEUS 1.0.0 · Mutable Dreams 1.0 · MYCELIUM 1.0-test · Niagara Drift 0.2 · No Man Sky FM 0.5 · NOIZ DEMONS 666 · OberVave 3.0.1 · FM1 Open V14 · OPN-1 2.0.0 · ORBIT 0.7.1 · PIGEON 0.5.0-beta.1 · Polly 0.5 · PurpleMonkey 0.11 · FM1 Quest 38 · Rainbow Mode 1.1.5-rb · Shine On 3.0.1 · FM-1 SID 0.1 · SID-1 1.0.0 · SIDOU 0.3.1 · Skiff 1.4 · SLOOP 2.8.1 · SLOOP ALG ALG05-TEST · SLOOP DX7 Banks 2.5-b28-test · SLOOP Floyd FM 2.4 · sloopDX 4.0 · Tessera 2.0.1 · Tonitor 2026.10.23 · TRIBE 0.3-beta · Tuna 1.0-fbc56d3 · Unholy Union 0.2.3 · Vector37 0.3.2 · WaveLoop FM-1 1.0.5.2-midi23 · winampFM Synth 0.12 · X0X 1.1.0 · X0X-RMX 1.1.0 · ZEN-1 1.2 · zp12 2.5
Try it in your browser
Play a virtual FM-1 with any of its community firmwares: M-VAVE FM-1.
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-mc1-1.2.0.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_mc1: ask “what can the M-VAVE FM-1 do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (21)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/fm1_mc1/glide |
5 | 0–127 | continuous | Track | |
/fm1_mc1/part_level |
7 | 0–127 | continuous | Track | |
/fm1_mc1/part_pan |
10 | 0–127 | continuous | Track | |
/fm1_mc1/r_d1_bus_type |
20 | 0–7 | continuous | Track | |
/fm1_mc1/r_d2_bus_type |
21 | 0–7 | continuous | Track | |
/fm1_mc1/c_f1_bus_type |
23 | 0–7 | continuous | Track | |
/fm1_mc1/c_f2_bus_type |
24 | 0–7 | continuous | Track | |
/fm1_mc1/sustain_pedal |
64 | 0–127 | switch | Track | |
/fm1_mc1/sustain |
70 | 0–127 | continuous | Track | |
/fm1_mc1/resonance |
71 | 0–127 | continuous | Track | |
/fm1_mc1/release |
72 | 0–127 | continuous | Track | |
/fm1_mc1/attack |
73 | 0–127 | continuous | Track | |
/fm1_mc1/cutoff |
74 | 0–127 | continuous | Track | |
/fm1_mc1/decay |
75 | 0–127 | continuous | Track | |
/fm1_mc1/r_d1_send |
91 | 0–127 | continuous | Track | |
/fm1_mc1/r_d2_send |
92 | 0–127 | continuous | Track | |
/fm1_mc1/c_f1_send |
93 | 0–127 | continuous | Track | |
/fm1_mc1/r_d1_send_alias |
94 | 0–127 | continuous | Track | |
/fm1_mc1/c_f2_send |
95 | 0–127 | continuous | Track | |
/fm1_mc1/all_sound_off |
120 | 0–127 | trigger | Track | |
/fm1_mc1/all_notes_off |
123 | 0–127 | trigger | Track |
SysEx commands (3)¶
| OSC address | Arguments |
|---|---|
/fm1_mc1/program |
program: u7 |
/fm1_mc1/system/info |
|
/fm1_mc1/system/identify |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /fm1_mc1/note/on <note> <velocity>, /fm1_mc1/cc/<number> <value>, /fm1_mc1/pitchbend <0-16383>, /fm1_mc1/program_change <n>.
Limitations¶
MC-1 1.2.0 by dspaudio (GPL-3.0), a groovebox firmware for the FM-1. Own 4-part map (3 melodic + drums); not Felucca's routing block, no RPN, no MIDI learn; Version 1.2.0 in VERSION and FIRMWARE.json matches. Channels: One channel per part, defaults 1, 2, 3 (melodic) and 10 (drums) (src/engine.c:99); each set 1-16 on GLO > MIDI page, saved with the project; no omni/SEL mode. Pitch bend: 14-bit, fixed ~+/-2 semitones, no RPN (src/midi.c:112; docs/MIDI.md). Aftertouch: Channel and poly pressure ignored (no dispatch case; docs/MIDI.md). Clock: Source INTERNAL/USB/TRS (BLE listed as unavailable); selected source F8 (BPM derived), FA/FB/FC; no SPP. Internal clock sends F8 and FA/FB/FC out (src/midi.c:141-174). MIDI out: USB only: sequencer/arp/panel notes on part channels, knob edits as CCs (5,7,10,70-75, sends 91/93/92/95 per part, bus types 20/23/21/24 on part 1's channel), PC on demo change, clock+transport when internal; panic CC123/120/64; incoming not echoed. No TRS out. NRPN: none. SysEx `F0 00 32 45`: M-VAVE update protocol kept (identify 0x11 -> 27-byte product string); M-UPGRADE F0 22 24 35 7F F7 starts update. SysEx `F0 22 24 35 7D F7`: UBOOT soft key: ignored in the app (MC_USB_APP), honoured only by the update loader. SysEx `F0 7D 46 4C`: absent: no Felucca editor protocol, no INFO. SysEx `F0 43`: absent: no DX7 parser (no FM engine); musical parser skips all SysEx. Identity: Vendor identify: FM-1_900 (OTA_IDENTITY, firmware/app.c:41; FIRMWARE.json). No editor INFO. No Universal Identity reply. USB manufacturer 'M-VAVE', product 'MC-1 / M-VAVE FM-1' (firmware/update/usb.c:267-268).
Frequently asked questions¶
Which MIDI CC controls the filter cutoff on the M-VAVE FM-1?
CC 74 (0–127), named /fm1_mc1/cutoff in SynthHub's map.
How many parameters of the M-VAVE FM-1 can be controlled over MIDI?
SynthHub's map of the M-VAVE FM-1 lists 21 MIDI CC parameters, each with its number, range and a readable name; the full chart is on this page.
Can an AI agent like Claude control the M-VAVE FM-1?
Yes: SynthHub's hosted MCP server knows the M-VAVE FM-1's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.