devices/m-vave/fm-1.vendor.fw-tribe-0.3-beta.json, updated 2026-10-26Edit on GitHubJSONMIDNAMOSCQueryM-VAVE FM-1 running TRIBE 0.3-beta
The M-VAVE FM-1 MIDI implementation: 2 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- firmwaretribe-0.3-beta
- Maker
- M-VAVE
- Firmware
- TRIBE 0.3-beta (alternative firmware by apiel)
- Source
- maker's documentation
From the README of apiel/fm1-tribe at 29664b2, licence GPL-3.0.
TRIBE
Custom firmware for the M-VAVE FM-1: a ten-track groovebox where any engine plays on any track. Kicks, the 909 and 808 voices and ACID, sixty-four clips per track, scatter effects, two master effects every track sends to, and four master knobs you assign to the volume, a DJ filter, the effects or the tempo.
Try it, install it
| Emulator | TRIBE in the browser, with sound: the same code the FM-1 runs. No FM-1 needed. |
| Web installer | Flash your FM-1 from Chrome or Edge over USB. Nothing to install on the computer. Can put the stock firmware back. |
| Manual | Getting started, every page and every parameter. |
| What's new | The release notes. |
| Discord | Questions, bugs, music: the fm1-tribe channel. |
| Site | All of the above on one page. |
Installing firmware is at your own risk; TRIBE is a beta.
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
- fm1-tribe, Discord, for the TRIBE 0.3-beta firmware
MIDI controls
2 controls, from the source at TRIBE 0.3-beta (alternative firmware by apiel)
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| System info | /fm1_tribe/system/info |
|
| System identify | /fm1_tribe/system/identify |
Performance MIDI
Notes, pitch bend and any CC are also available: /fm1_tribe/note/on <note> <velocity>, /fm1_tribe/cc/<number> <value>, /fm1_tribe/pitchbend <0-16383>, /fm1_tribe/program_change <n>.
The same MIDI as fm-1.vendor.fw-dinghy-0.4, which this firmware shares.
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-tribe-0.3-beta --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_tribe: ask “what can the M-VAVE FM-1 do?” and it reads this map with list_routes. See the MCP guide.
Limitations
TRIBE 0.3-beta by apiel (GPL-3.0), a groovebox firmware for the FM-1. No musical MIDI at all: the built unit (x0x.c includes tribe/*.c, not app/engine.c or app/editor.c) never reads the MIDI input queue; app/engine.c and app/editor.c are dead X0X copies; docs/SPEC.md: 'MIDI deferred'; NOTE.md: 'TODO midi'; No editor protocol in the build, so no INFO. Channels: none (MIDI input queued by USB/TRS drivers but never consumed). Pitch bend: ignored. Aftertouch: ignored. Clock: none (no clock in or out in the built code). MIDI out: none (plat_midi_out never called from tribe/). NRPN: none. SysEx `F0 00 32 45`: M-VAVE update protocol only (SysEx frames go to ota_service). SysEx `F0 22 24 35 7D F7`: UBOOT soft key: reboots to mask ROM. SysEx `F0 7D 46 4C`: absent in the build (app/editor.c not compiled). SysEx `F0 43`: absent. Identity: Vendor identify: dev FM-1_900; release FM-1_9XXYYZZ, so 0.3-beta -> FM-1_9000300 (tools/build.py:55,355-368). No editor INFO. No Universal Identity. USB manufacturer 'X0X', product 'X0X FM-1' (unchanged from X0X, firmware/src/usb.c:211-217). 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.