devices/m-vave/fm-1.vendor.fw-chipbox-1.2.4.json, updated 2026-10-24Edit on GitHubJSONCSVMIDNAMOSCQueryM-VAVE FM-1 running Chipbox 1.2.4
The M-VAVE FM-1 MIDI implementation: 7 CC, 1 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- firmwarechipbox-1.2.4
- Maker
- M-VAVE
- Firmware
- Chipbox 1.2.4 (alternative firmware by Pasquale Barilla)
- Source
- maker's documentation
From the README of pbarilla/chipbox at 7792b46, licence GPL-3.0.
Chipbox
Chiptune 'grovebox' thing with NES, GB, and SMS stuff
What is it
A simple (to me) workflow for making music. Theres 3 main views you'll spend all your time in:
RACK - this is the current page (16 steps). Use this to add channels
CHIPs - this is where you can config each channel. You pick a channel from the hardware first (NES, GB, SMS), and then what channel (like PU1, WAV, etc). If you want appregio, make a channel and change the shape to an appregio shape.
SONG - this is where you stitch together the pages into a song
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
Share and load its sounds
Plug the M-VAVE FM-1 into your computer, open shared presets in Chrome, Edge or Opera and press Connect my synth: SynthHub finds it, takes the sound it plays and names it. Sounds others shared for it load from their page the same way.
https://github.com/pbarilla/chipbox
MIDI controls
8 controls, from the source at Chipbox 1.2.4 (alternative firmware by Pasquale Barilla)
Track
| Control | CC | Range | Name to send |
|---|---|---|---|
| Play stop | 102 | 0–127 | /fm1_chipbox/play_stop |
| Tempo | 103 | 0–127 | /fm1_chipbox/tempo |
| Save project | 104 | 0–127 | /fm1_chipbox/save_project |
| Open project | 105 | 0–127 | /fm1_chipbox/open_project |
| Add channel test | 106 | 0–127 | /fm1_chipbox/add_channel_test |
| Remove last channel test | 107 | 0–127 | /fm1_chipbox/remove_last_channel_test |
| Fx pad test | 108 | 0–127 | /fm1_chipbox/fx_pad_test |
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| Program | program: u7 | /fm1_chipbox/program |
Performance MIDI
Notes, pitch bend and any CC are also available: /fm1_chipbox/note/on <note> <velocity>, /fm1_chipbox/cc/<number> <value>, /fm1_chipbox/pitchbend <0-16383>, /fm1_chipbox/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-chipbox-1.2.4 --out-port <N> --in-port <M>
Then send OSC to 127.0.0.1:7777, for example:
osc-bridge osc-send /fm1_chipbox/play_stop 63
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as fm1_chipbox: ask “what can the M-VAVE FM-1 do?” and it reads this map with list_routes. See the MCP guide.
Limitations
Chipbox 1.2.4 by Pasquale Barilla (GPL-3.0), a groovebox firmware for the FM-1. CC 105-108 are marked 'test' in source; undocumented in README; TRS MIDI IN not built (FELUCCA_UART 0): USB only; fixed identity FM-1_337, outside the FM-1_9NN range (installers cannot resume an interrupted install). Channels: MIDI channel n plays chip channel n (up to 16 channels, as many as the project has); any channel for CCs/PC. Pitch bend: ignored. Aftertouch: ignored. Clock: none: internal sequencer clock only (24 ppq internal), MIDI clock ignored and not sent. MIDI out: USB: panel keys as notes (velocity 100) on the selected channel's number; every 500 ms CC100 = CPU load, CC101 = project slot | dirty/loaded flags, on channel 1. 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. Identity: vendor identify FM-1_337 (fixed); rescue FM-1_000; 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 7 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.