M-VAVE FM-1: MIDI CC, NRPN and OSC map¶

The M-VAVE FM-1 as named OSC addresses — 2 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	sloop-alg-alg05-test
Revision	SLOOP ALG ALG05-TEST (alternative firmware by shaw-core)
Upstream	vendor-doc
Driver file	`devices/m-vave/fm-1.vendor.fw-sloop-alg-alg05-test.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-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, fm-1.vendor.fw-zp12-2.5.

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-sloop-alg-alg05-test.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /fm1/system/info

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 (2)¶

OSC address	Arguments
`/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¶

SLOOP ALG ALG05-TEST by shaw-core (none stated (a SLOOP fork)), a groovebox firmware for the FM-1. SLOOP 2.2 MIDI: only notes over USB; CCs, Program Change and bend are dropped (seq.c:1547); no MIDI clock in: usb.c queues only CIN 8-E, so F8/FA/FB/FC are dropped (usb.c:459-463); SYNC is a placeholder; TRS MIDI IN is off by default (felucca.c:40 FELUCCA_UART 0); the README says it uses USB MIDI only; the fork's own editor commands 34 XPATCH (read or replace the selected DX7 voice as 128 bytes) and 35 BIND (map a user slot onto a factory entry); these numbers clash with SLOOP 2.3+ backup commands 34-36; INFO protocol byte = 7 (the fork's own meaning, not SLOOP's v7); adds the engines PLUCK, ADDIT, DX7, VA, KSDRUM, KSWIRE, KSCOMB. Channels: drum channel (default 10) -> drum track; ch1-3 -> synth tracks 1-3; ch4-16 -> the selected track (USB only). Pitch bend: ignored. Aftertouch: ignored. Clock: none in, none out. MIDI out: USB: panel keys as notes on the track channel. NRPN: none. SysEx `F0 7D 46 4C`: SLOOP 2.2 editor protocol (cmds 1-33) plus the fork's 34 ED_XPATCH (128-byte DX7 voice) and 35 ED_BIND; user presets carry a 128-byte xpatch. SysEx `F0 00 32 45`: M-VAVE vendor update protocol / identify. SysEx `F0 22 24 35`: 7D = mask-ROM reboot, 7F = OTA request. SysEx `F0 43`: not parsed by the firmware; the web editor splits .syx 32-voice banks and sends voices with XPATCH or UP_PUT. Identity: vendor identify FM-1_985 (tools/build.py:50; read from firmware/sloop-ALG05-TEST.fwsc); editor INFO "FELUCCA SLOOP ALG05 TEST" (build.py:51); USB product "Felucca". It reads no CC.

Try it in your browser

Play a virtual FM-1 with any of its community firmwares: M-VAVE FM-1.