M-VAVE FM-1 (LOOM-8 0.7) MIDI CC chart, NRPN and OSC map¶
The M-VAVE FM-1 MIDI implementation: 45 CC, 3 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | M-VAVE FM-1 |
|---|---|
| Vendor | M-VAVE |
| OSC prefix | /fm1_loom |
| Source | 📘 From the manufacturer's documentation |
| Firmware | loom-0.7 |
| Revision | LOOM-8 0.7 (alternative firmware by Charles Vestal) |
| Upstream | vendor-doc |
| Driver file | devices/m-vave/fm-1.vendor.fw-loom-0.7.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 · 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-loom-0.7.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_loom: 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 (45)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/fm1_loom/lfo_amount |
1 | 0–127 | continuous | Track | |
/fm1_loom/glide |
5 | 0–127 | continuous | Track | |
/fm1_loom/level |
7 | 0–127 | continuous | Track | |
/fm1_loom/mute |
9 | 0–127 | continuous | Track | |
/fm1_loom/pan |
10 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_1 |
16 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_2 |
17 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_3 |
18 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_4 |
19 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_5 |
20 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_6 |
21 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_7 |
22 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_8 |
23 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_9 |
24 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_10 |
25 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_mute_11 |
26 | 0–127 | continuous | Track | |
/fm1_loom/resonance |
71 | 0–127 | continuous | Track | |
/fm1_loom/release |
72 | 0–127 | continuous | Track | |
/fm1_loom/attack |
73 | 0–127 | continuous | Track | |
/fm1_loom/cutoff |
74 | 0–127 | continuous | Track | |
/fm1_loom/decay |
75 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_1 |
80 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_2 |
81 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_3 |
82 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_4 |
83 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_5 |
84 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_6 |
85 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_7 |
86 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_8 |
87 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_9 |
88 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_10 |
89 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_pan_11 |
90 | 0–127 | continuous | Track | |
/fm1_loom/send_i |
91 | 0–127 | continuous | Track | |
/fm1_loom/send_ii |
93 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_1 |
102 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_2 |
103 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_3 |
104 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_4 |
105 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_5 |
106 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_6 |
107 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_7 |
108 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_8 |
109 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_9 |
110 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_10 |
111 | 0–127 | continuous | Track | |
/fm1_loom/kit_sound_1_11_level_11 |
112 | 0–127 | continuous | Track |
SysEx commands (3)¶
| OSC address | Arguments |
|---|---|
/fm1_loom/program |
program: u7 |
/fm1_loom/system/info |
|
/fm1_loom/system/identify |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /fm1_loom/note/on <note> <velocity>, /fm1_loom/cc/<number> <value>, /fm1_loom/pitchbend <0-16383>, /fm1_loom/program_change <n>.
Limitations¶
LOOM-8 0.7 by Charles Vestal (GPL-3.0), a groovebox firmware for the FM-1. CC numbers echo Felucca's (5/7/10/71-75/91/93) but routing is per channel=track, plus kit/FX/master maps; 9 engines differ from Felucca. Channels: Fixed: tracks T1-T8 = ch1-8, FX I ch9, FX II ch10, master + scenes ch11; ch12-16 play/ccs to the selected instrument track; notes on 9/10 ignored. Never sends on 12-16. Pitch bend: Per track, fixed +-2 semitones, no RPN. Aftertouch: ignored. Clock: In: F8 ext clock, FA start, FB continue, FC stop. Out: F8 24 ppqn + FA/FB/FC when Setup 'clock' send is on and not on ext clock. No SPP. MIDI out: USB: track notes on own channel (track MIDI OUT + Setup NOTES on; keys and sequencer, not echoed MIDI-in or arps they start); CC OUT (on by default): hand-turned mapped knobs as their CC; scene PCs on ch11 with SCENES OUT. NRPN: none. SysEx `F0 00 32 45 00 00 00 40 7F F7`: M-VAVE vendor update protocol kept (felucca-bsp ota.c): identify reply = 27-byte product string (fm1.toml id_prefix + 00 dev / + XXYYZZ release); update, backup and screen mirror commands in the 00 59 framing. SysEx `F0 7D 53 52`: fm1-reader screen-reader protocol (SR): HELLO, page/knob announcements as text. SysEx `F0 7D 4C 47 F7`: development log readout (LG): crash record, rails, as ASCII frames. SysEx `F0 7D 4C 43`: remote panel control (LC): buttons, keys, encoders, master; ack F0 7D 4C 43 op F7. SysEx `F0 7D 46 4C`: Felucca editor framing, LOOM subset: INFO(1) -> 'LOOM-8 \<version>', sample bank SMP_BEGIN.SMP_READ (11-17), PING 25, PROF 26, BENCH 27, SOUND 28; no patch/bank editor commands. SysEx `F0 43`: absent: no DX7 bulk parser; other SysEx dropped. SysEx `F0 7E 7F 06 01`: absent: no Universal Identity reply. Identity: vendor identify: FM-1_10000700 for release 0.7 (FM-1_1000 dev build); USB product "LOOM-8 FM-1"; editor INFO: 'LOOM-8 \<version>'; Universal Identity: none.
Frequently asked questions¶
Which MIDI CC controls the filter cutoff on the M-VAVE FM-1?
CC 74 (0–127), named /fm1_loom/cutoff in SynthHub's map.
How many parameters of the M-VAVE FM-1 can be controlled over MIDI?
SynthHub's map of the M-VAVE FM-1 lists 45 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.