M-VAVE FM-1 (No Man Sky FM 0.5) MIDI CC chart, NRPN and OSC map¶
The M-VAVE FM-1 MIDI implementation: 16 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_nmsfm |
| Source | 📘 From the manufacturer's documentation |
| Firmware | nmsfm-0.5 |
| Revision | No Man Sky FM 0.5 (alternative firmware by Hericdk) |
| Upstream | vendor-doc |
| Driver file | devices/m-vave/fm-1.vendor.fw-nmsfm-0.5.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 · 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 · 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-nmsfm-0.5.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_nmsfm: 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 (16)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/fm1_nmsfm/bank_select |
0 | 0–127 | continuous | Track | |
/fm1_nmsfm/glide |
5 | 0–127 | continuous | Track | |
/fm1_nmsfm/level |
7 | 0–127 | continuous | Track | |
/fm1_nmsfm/pan |
10 | 0–127 | continuous | Track | |
/fm1_nmsfm/expression |
11 | 0–127 | continuous | Track | |
/fm1_nmsfm/sustain |
64 | 0–127 | switch | Track | |
/fm1_nmsfm/resonance |
71 | 0–127 | continuous | Track | |
/fm1_nmsfm/release |
72 | 0–127 | continuous | Track | |
/fm1_nmsfm/attack |
73 | 0–127 | continuous | Track | |
/fm1_nmsfm/engine_cutoff_else_track_filter |
74 | 0–127 | continuous | Track | |
/fm1_nmsfm/decay |
75 | 0–127 | continuous | Track | |
/fm1_nmsfm/reverb_send |
91 | 0–127 | continuous | Track | |
/fm1_nmsfm/chorus_send |
93 | 0–127 | continuous | Track | |
/fm1_nmsfm/delay_send |
94 | 0–127 | continuous | Track | |
/fm1_nmsfm/remote_panel_button_1_102_115_14_buttons |
102 | 0–127 | continuous | Track | |
/fm1_nmsfm/reset_all_controllers |
121 | 0–127 | trigger | Track |
SysEx commands (3)¶
| OSC address | Arguments |
|---|---|
/fm1_nmsfm/program |
program: u7 |
/fm1_nmsfm/system/info |
|
/fm1_nmsfm/system/identify |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /fm1_nmsfm/note/on <note> <velocity>, /fm1_nmsfm/cc/<number> <value>, /fm1_nmsfm/pitchbend <0-16383>, /fm1_nmsfm/program_change <n>.
Limitations¶
No Man Sky FM 0.5 by Hericdk (GPL-3.0), a groovebox firmware for the FM-1. Keeps SLOOP's MIDI map except: matches SLOOP 2.7, not 2.8.1: no CC11 expression and no CC121 reset (seq.c:2738-2786); no Bank Select CC0: Program Change has no bank (that came in SLOOP 2.7.2); everything else as in SLOOP 2.8.1: CC74 engine cutoff (cc74_slot), sustain, MIDI learn (16), REMOTE CC102-115, FX channel, DR MAP, IN = CH n, OTHER, clock out; the game on HOME is screen and knobs only; it adds no MIDI. Channels: GLO > MIDI: CH1/CH2/CH3 (default 1, 2, 3) and CH4 = drums (default 10), each OFF or 1-16; OTHER: SEL or OFF; IN: NOTES, CLOCK, or CH 1-16 (one channel on the selected track); FX CH plays the punch-in effects (notes 53-79); REMOTE channel. Pitch bend: 14-bit; range GLO > MIDI 2 > BEND 1-12 semitones (default 2, params.c:205); not on drums; no RPN. Aftertouch: ignored. Clock: in from USB or TRS (SYNC): F8/FA/FB/FC; out on USB when GLO > MIDI 3 > CLOCK = OUT (F8, FA, FC; seq.c:2884-2891). MIDI out: USB: keys, or with OUT = SEQ also the sequencer, arp and rolls, on each track's channel. NRPN: none. SysEx `F0 7D 46 4C`: SLOOP editor protocol v12 (FM6 68-71, SYN kits 72-76, LIVE 77). 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 (DX7 import in the web editor only, as in SLOOP). Identity: vendor identify FM-1_900 (read from release/nmsfm-0.5.fwsc); editor INFO "FELUCCA NMS FM 0.5"; USB product "Felucca".
Frequently asked questions¶
Which MIDI CC controls the filter cutoff on the M-VAVE FM-1?
CC 74 (0–127), named /fm1_nmsfm/engine_cutoff_else_track_filter 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 16 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.