M-VAVE FM-1 (OPN-1 2.0.0) MIDI CC chart, NRPN and OSC map¶
The M-VAVE FM-1 MIDI implementation: 21 CC, 2 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | M-VAVE FM-1 |
|---|---|
| Vendor | M-VAVE |
| OSC prefix | /fm1_opn1 |
| Source | 📘 From the manufacturer's documentation |
| Firmware | opn1-2.0.0 |
| Revision | OPN-1 2.0.0 (alternative firmware by putchdev) |
| Upstream | vendor-doc |
| Driver file | devices/m-vave/fm-1.vendor.fw-opn1-2.0.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 · MC-1 1.2.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 · 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-opn1-2.0.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_opn1: 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_opn1/lfo_speed_chip_wide |
1 | 0–127 | continuous | Track | |
/fm1_opn1/psg_volume |
7 | 0–127 | continuous | Track | |
/fm1_opn1/instrument_library_slot |
9 | 0–127 | continuous | Track | |
/fm1_opn1/algorithm |
14 | 0–127 | continuous | Track | |
/fm1_opn1/feedback |
15 | 0–127 | continuous | Track | |
/fm1_opn1/total_level_o1_16_19_o1_o4 |
16 | 0–127 | continuous | Track | |
/fm1_opn1/multiple_o1_20_23_o1_o4 |
20 | 0–127 | continuous | Track | |
/fm1_opn1/detune_o1_24_27_o1_o4 |
24 | 0–127 | continuous | Track | |
/fm1_opn1/rate_scaling_o1_39_42 |
39 | 0–127 | continuous | Track | |
/fm1_opn1/attack_rate_o1_43_46 |
43 | 0–127 | continuous | Track | |
/fm1_opn1/decay_1_rate_o1_47_50 |
47 | 0–127 | continuous | Track | |
/fm1_opn1/decay_2_rate_o1_51_54 |
51 | 0–127 | continuous | Track | |
/fm1_opn1/sustain_level_o1_55_58 |
55 | 0–127 | continuous | Track | |
/fm1_opn1/release_rate_o1_59_62 |
59 | 0–127 | continuous | Track | |
/fm1_opn1/am_on_o1_70_73 |
70 | 0–127 | continuous | Track | |
/fm1_opn1/lfo_on_chip_wide |
74 | 0–127 | continuous | Track | |
/fm1_opn1/fm_depth_pms |
75 | 0–127 | continuous | Track | |
/fm1_opn1/am_depth_ams |
76 | 0–127 | continuous | Track | |
/fm1_opn1/stereo |
77 | 0–127 | continuous | Track | |
/fm1_opn1/bend_range |
81 | 0–127 | continuous | Track | |
/fm1_opn1/ssg_eg_o1_90_93 |
90 | 0–127 | continuous | Track |
SysEx commands (2)¶
| OSC address | Arguments |
|---|---|
/fm1_opn1/program |
program: u7 |
/fm1_opn1/system/identify |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /fm1_opn1/note/on <note> <velocity>, /fm1_opn1/cc/<number> <value>, /fm1_opn1/pitchbend <0-16383>, /fm1_opn1/program_change <n>.
Limitations¶
OPN-1 2.0.0 by putchdev (GPL-3.0), a instrument firmware for the FM-1. version 2.0.0 not in source: APP_VER from --release (default DEV); GenMDM-compatible CC layout (YM2612 registers per operator); docs/MIDI.md is the author's full spec; channel 16 (and 15 for data) reserved for its web-app protocol: ch16 CC 0x1F-0x7F = version query, part setup 0x20-0x27, patch frames 0x50-0x5E, chunks 0x6A-0x6F, song stream 0x60-0x7F (opn1.c:1088-1260, docs/MIDI.md 2-3). Channels: 6 FM parts, each with channel 1-16, off or All (= ch 1-6 and 12-15). Modes (CC 26 on ch16 / GLO page): Normal (default 'Single': part 1 on All), GENMDM (part n = FM ch n on MIDI ch n, mono), PANEL (any ch but 10 plays the selected part). Ch 7-9 PSG tones, 10 drum kit (or PSG noise), 11 PSG noise, 15-16 transfers. USB+TRS merged. Pitch bend: 14-bit on FM parts and PSG tones; range 2 st default, CC 81 sets 0-17 st; on ch 15/16 bend and poly AT carry transfer data. Aftertouch: ignored for sound (poly AT on ch 15/16 = transfer data). Clock: none (no F8 handling, no clock out). MIDI out: USB, ch16 CC replies to the web app only; CC 28+p on ch16 when part p's slot changes; panel keys not sent. NRPN: none (no CC 64, no RPN; bend range by CC 81). SysEx `-`: no SysEx used by the app (docs/MIDI.md: 'SysEx is not used'); transfers are CCs on ch16. SysEx `F0 00 32 45 / F0 22 24 35`: M-VAVE vendor update protocol kept (identify F0 00 32 45 00 00 00 40 7F F7 -> 27-byte product string; F0 22 24 35 7F F7 upgrade; F0 22 24 35 7D F7 reboots to mask-ROM UBOOT: never send). SysEx `F0 43`: no raw DX7 parser: absent. Identity: vendor identify FM-1_950 (dev), release FM-1_95Y (2.0.0 -> FM-1_950); rescue FM-1_000; USB product 'OPN-1 FM-1' ('Felucca Update' in rescue). Version query: ch16 CC 0x1F 0 -> CC 1C major, 1D minor, 1E patch (2.0+).
Frequently asked questions¶
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.