devices/m-vave/fm-1.vendor.fw-orbit-0.7.1.json, updated 2026-10-24Edit on GitHubJSONCSVMIDNAMOSCQueryM-VAVE FM-1 running ORBIT 0.7.1
The M-VAVE FM-1 MIDI implementation: 16 CC, 3 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- firmwareorbit-0.7.1
- Maker
- M-VAVE
- Firmware
- ORBIT 0.7.1 (alternative firmware by dspaudio)
- Source
- maker's documentation
From the README of dspaudio/orbit at c07bd1d, licence GPL-3.0.
ORBIT
Make a beat, shape three synths, then rearrange their events on Tape.
ORBIT is a four-track groovebox firmware for the M-VAVE FM-1: three synth parts and a drum machine, played through a color-coded Synth / Drum / Event Tape / Mixer workflow. Record a loop, turn it into a song, and keep your favorite sound controls together with user macros. Based on SLOOP/Felucca, with original ORBIT engines and graphics inspired by the original OP-1's four encoder roles.
Install · Get started · User guide · MIDI controllers · 0.7.1 release notes · Try the native preview
0.7.1: a clearer drum matrix, precise slow ENV/LFO turns, step-recorded sound controls, safer Tape/pattern edits and a smaller firmware image.
Actual firmware UI rendered by the native host harness. These are earlier ORBIT screens, not hardware photographs or captures of the current release.
Make a loop, then move its events
- Select track 4 with ALGORITHM and choose a drum kit with PRESETS. Press REC and play; on an empty project in free mode, press REC on the next downbeat to close the loop.
- Select track 1, choose a sound, and record a bass line. Add chords or a melody on tracks 2 and 3.
- Press HOME for Event Tape. Set the region with KNOB 2/3, choose COPY or LIFT with KNOB 4, and hold SEL while pressing OCT- to capture it. Set the destination with KNOB 1 and use SEL + OCT+ to drop it.
- Press GLO for Mixer to balance the four tracks. Save variations into sections A-D and play or chain them with the SAVE layer.
Tape edits sequencer events, including notes, drum hits, timing, fills and parameter locks. It is not audio recording, PCM overdubbing or tape-speed playback. Drop overwrites destination events, so save a section before experimenting. See the Tape controls.
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
19 controls, from the source at ORBIT 0.7.1 (alternative firmware by dspaudio)
Track
| Control | CC | Range | Name to send |
|---|---|---|---|
| Bank select | 0 | 0–127 | /fm1_orbit/bank_select |
| Glide | 5 | 0–127 | /fm1_orbit/glide |
| Level | 7 | 0–127 | /fm1_orbit/level |
| Pan | 10 | 0–127 | /fm1_orbit/pan |
| Expression | 11 | 0–127 | /fm1_orbit/expression |
| Sustain | 64 | switch | /fm1_orbit/sustain |
| Engine res or q | 71 | 0–127 | /fm1_orbit/engine_res_or_q |
| Release | 72 | 0–127 | /fm1_orbit/release |
| Attack | 73 | 0–127 | /fm1_orbit/attack |
| Filter bipolar lp hp 64 off | 74 | 0–127 | /fm1_orbit/track_filter_bipolar_lp_hp_64_off |
| Decay | 75 | 0–127 | /fm1_orbit/decay |
| Reverb send | 91 | 0–127 | /fm1_orbit/reverb_send |
| Chorus send | 93 | 0–127 | /fm1_orbit/chorus_send |
| Delay send | 94 | 0–127 | /fm1_orbit/delay_send |
| Remote panel button 1 102 115 14 buttons | 102 | 0–127 | /fm1_orbit/remote_panel_button_1_102_115_14_buttons |
| Reset controllers | 121 | trigger | /fm1_orbit/reset_controllers |
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| Program | program: u7 | /fm1_orbit/program |
| System info | /fm1_orbit/system/info |
|
| System identify | /fm1_orbit/system/identify |
Performance MIDI
Notes, pitch bend and any CC are also available: /fm1_orbit/note/on <note> <velocity>, /fm1_orbit/cc/<number> <value>, /fm1_orbit/pitchbend <0-16383>, /fm1_orbit/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-orbit-0.7.1 --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_orbit: ask “what can the M-VAVE FM-1 do?” and it reads this map with list_routes. See the MCP guide.
Limitations
ORBIT 0.7.1 by dspaudio (GPL-3.0), a groovebox firmware for the FM-1. Keeps SLOOP's MIDI map except: matches SLOOP 2.6, not 2.8.1; CC74 = track FILTER only (bipolar LP/HP), drums too; no per-engine cutoff (seq.c:2196-2199); no CC11 or CC121; no Bank Select (Program Change has no bank); no REMOTE CC102-115, no FX channel, no DR MAP, no MIDI clock out; different engine list (adds SWARM, ORBIT_PULSE, FM4, CLUSTER, CLOUD), so CC71 RES/Q targets differ by engine; editor protocol v12 is ORBIT's own: 77 = ED_WIDE (3-byte values), 78-81 = macro commands. It is not SLOOP's v12, where 77 = LIVE; MIDI notes on the STEP screen enter notes or chords at the cursor (docs/MIDI-CONTROL.md). Channels: GLO > MIDI: CH1-3 (default 1, 2, 3) and the drum channel (default 10), each OFF or 1-16, kept unique; GLO > MIDI 2: IN = NOTES, CLOCK or CH 1-16 (selected track), OTHER = SEL or OFF (params.c:167-189; docs/MIDI-CONTROL.md). Pitch bend: 14-bit; range GLO > MIDI 2 > BEND 1-12 semitones (default 2, params.c:197); not on drums. Aftertouch: ignored. Clock: in from USB or TRS (SYNC): F8/FA/FB/FC; no clock out. MIDI out: USB: keys, or with OUT = SEQ also the sequencer, arp and rolls; incoming notes are not echoed. NRPN: none. SysEx `F0 7D 46 4C`: ORBIT editor protocol v12: SLOOP v10 commands (1-42, FM6 68-71, SYN kits 72-76) plus 77 ED_WIDE and 78-81 macros (MACRO, UP_GET_MAP, UP_PUT_MAP, MACRO_DESC). 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; DX7 SysEx is imported in the web editor (README). Identity: vendor identify FM-1_900 (docs/releases/0.7.1.md: releases use the default build, never --release); editor INFO "FELUCCA ORBIT 0.7.1"; USB product "Felucca".
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
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.