devices/m-vave/fm-1.vendor.fw-dinghy-0.4.json, updated 2026-10-24Edit on GitHubJSONMIDNAMOSCQueryM-VAVE FM-1 running Dinghy 0.4
The M-VAVE FM-1 MIDI implementation: 2 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- firmwaredinghy-0.4
- Maker
- M-VAVE
- Firmware
- Dinghy 0.4 (alternative firmware by zvenson)
- Source
- maker's documentation
From the README of zvenson/dinghy at 22acb91, licence GPL-3.0.
Dinghy
The smallest firmware for the M-VAVE FM-1 to build your own on.
Dinghy plays a sine wave on the keys, and that is all it does. Under it is everything an FM-1 firmware needs before it can be any fun: the update path, the USB rescue, MIDI over USB and the TRS jack (with clock), USB audio, the keys, knobs and LEDs, the screen, flash storage, and the same again for the M-Vave SMK-37. It all works, so you start with the part you actually want to write.
firmware/src/dinghy.c **Status: 0.4.** 0.3 was tested on the FM-1: the install, MIDI in (pitch exact, 4 voices), USB audio at
> 44.1 / 48 kHz, the keys, the screen, the octave kept in flash, and back to another firmware through the hub.
> 0.4 brings OberVave's platform over: the TRS MIDI IN, the clock, blobs and slots, the loader's screen, the SMK-37.
> That code runs on the device in OberVave (FM-1 and SMK-37); Dinghy 0.4 itself is tested on the host only so far.
[Read the whole README on GitHub](https://github.com/zvenson/dinghy/blob/22acb9165ebc8baa712af3aff8c507e230c1e028/README.md)
Try it in your browser
Play a virtual FM-1 with any of its community firmwares: M-VAVE FM-1.
Communities
Where M-VAVE FM-1 owners meet, share and help each other:
- M-VAVE forum, forum
MIDI controls
2 controls, from the source at Dinghy 0.4 (alternative firmware by zvenson)
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| System info | /fm1_dinghy/system/info |
|
| System identify | /fm1_dinghy/system/identify |
Performance MIDI
Notes, pitch bend and any CC are also available: /fm1_dinghy/note/on <note> <velocity>, /fm1_dinghy/cc/<number> <value>, /fm1_dinghy/pitchbend <0-16383>, /fm1_dinghy/program_change <n>.
Use 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 m-vave/fm-1.vendor.fw-dinghy-0.4 --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_dinghy: ask “what can the M-VAVE FM-1 do?” and it reads this map with list_routes. See the MCP guide.
Limitations
Dinghy 0.4 by zvenson (GPL-3.0), a instrument firmware for the FM-1. firmware template: no CC, no Program Change, no pitch bend handling at all; version 0.4 not in source: APP_VER comes from tools/build.py --release (default 0.0). Channels: One receive channel setting (saved): 0 = omni (default), else 1-16; only notes are acted on. USB and TRS MIDI IN merged in one queue (midi_get returns 1 USB, 2 TRS). Pitch bend: ignored. Aftertouch: ignored. Clock: in (USB and TRS): F8 counted to show BPM on screen, FA/FB/FC run state; no sync of sound, no SPP, no clock out from the app (midi_send can send F8 FA FB FC). MIDI out: USB only: panel keys as note on/off (velocity from the keys) on the receive channel (channel 1 when omni). NRPN: none. 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. SysEx `F0 7D 46 4C`: no Felucca editor protocol, no INFO, no Universal Identity reply. Identity: vendor identify: FM-1_990 (dev build), release FM-1_99Y (tools/build.py --release X.Y; 0.4 -> FM-1_994); rescue FM-1_000; update loader ota-FM-1_015; SMK-37 builds 'SMK-37 Pro_99Y'. USB product 'Felucca' ('Felucca Update' in the loader). No editor INFO. It reads no CC.
Firmwares
The M-VAVE FM-1 runs 94 firmwares SynthHub maps, each with its own MIDI or another's it shares. All the devices with several: firmwares.
94 firmwares
Frequently asked questions
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.