M-VAVE FM-1 (BEETLE 1.4.25) MIDI CC chart, NRPN and OSC map¶
The M-VAVE FM-1 MIDI implementation: 4 CC, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | M-VAVE FM-1 |
|---|---|
| Vendor | M-VAVE |
| OSC prefix | /fm1_beetle |
| Source | 📘 From the manufacturer's documentation |
| Firmware | beetle-1.4.25 |
| Revision | BEETLE 1.4.25 (alternative firmware by Joppe Sikken (SikkenWorks)) |
| Upstream | vendor-doc |
| Driver file | devices/m-vave/fm-1.vendor.fw-beetle-1.4.25.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 · 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 · 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-beetle-1.4.25.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_beetle: 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 (4)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/fm1_beetle/sustain |
64 | 0–127 | switch | Track | |
/fm1_beetle/all_sound_off |
120 | 0–127 | trigger | Track | |
/fm1_beetle/reset_controllers |
121 | 0–127 | trigger | Track | |
/fm1_beetle/all_notes_off |
123 | 0–127 | trigger | Track |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /fm1_beetle/note/on <note> <velocity>, /fm1_beetle/cc/<number> <value>, /fm1_beetle/pitchbend <0-16383>, /fm1_beetle/program_change <n>.
Limitations¶
BEETLE 1.4.25 by Joppe Sikken (SikkenWorks) (GPL-3.0), a groovebox firmware for the FM-1. Source version BEETLE-V1.4.27 (build.py) vs 1.4.25 listed; Incoming MIDI is fed to ETCH's synth state (etch_native_midi), but with TRACK_FIRMWARE the audio is rendered by the tracker (track_fm1_audio_process -> track_chip_render), which never reads it: external notes/bend/sustain have no audible effect as far as the source shows; Tracker transport does not follow MIDI clock (clock_bpm/clock_running unused by track_*). Channels: Omni in ETCH engine state (per-channel note ids, sustain, bend); tracker channels not MIDI-addressable. USB only (no TRS uart driver in tree). Pitch bend: 14-bit, fixed +-2 semitones table, per channel (ETCH engine state; not rendered by tracker). Aftertouch: ignored (this tree has no 0xD0 branch, unlike ETCH). Clock: F8 measured into ETCH clock_bpm, FA/FB/FC set clock_running (audio_core.c:190-205); tracker transport ignores them. Out: ETCH perf-MIDI clock code compiled in but driven by ETCH seq_run, not the tracker. MIDI out: USB: panel keys as notes ch1, note 53+key+12*octave, velocity 127 (native_panel_midi.c); ETCH perf MIDI (voice notes, FA/F8/FC 24 ppqn) compiled in, tied to ETCH sequencer state. NRPN: none. SysEx `F0 00 59 (pack7)`: BEETLE project transfer V5 in the vendor packed-7 envelope: 0x50 HELLO . 0x58 ABORT, 0x59 DELETE, 0x5A RECOVER, 0x5B/0x5C marker audit/repair, 0x5D/0x5E V2 migration. SysEx `F0 00 59 (pack7)`: M-UPGRADE vendor update protocol (F0 pack7(00 59 cmd .) F7; cmd 0x11 handshake answers package identity; F0 22 24 35 7F F7 upgrade; F0 22 24 35 7D F7 UBOOT) (when built with OTA). SysEx `F0 43`: no raw DX7 F0 43 parser; no F0 7D 46 4C editor. Identity: vendor identify FM-1_2123 (bringup.c:176; older RC tools FM-1_2110); USB manufacturer 'SikkenWorks', product 'BEETLE Audio' (usb.c:392-397).
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 4 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.