The FM-1 Firmware Hub · open source only

Make Firmware,
Not War.

Every open-source firmware for the M-VAVE FM-1 in one place: Felucca, SLOOP, X0X, FoMni, Jangada, ChoralRoot, Melodee, Hortator, FiMba-1, zp12, sloopDX and more. No need to pick a side. Connect your FM-1 by USB, choose one, press Install: about a minute, and it is a different instrument. Try them all, keep the one you love, switch back tomorrow. Chrome or Edge.

Not ours, not checked by us. Except zp12 and sloopDX, these firmwares are their authors' work: this page takes each one unchanged from its GitHub release and checks only that it is an FM-1 package. We do not test, support or answer for them: questions and bugs go to each project. Back to stock any time: the official V15 installs from this page too. Back up first. The firmwares keep their projects, presets and samples in the same flash and in different ways: after a switch the new one may not read the old one's data, or start empty. Save what you made with the backup of the firmware you are on (each project's page says how) before you switch. Stuck? Hold OCT− while switching the FM-1 on (USB rescue), then install again.

Twelve open-source firmwares, one FM-1

Loading the catalogue…

+

Your firmware

Made an open-source firmware for the FM-1? Free, with its source (GPL-3.0), released as a .fwsc on GitHub: join in. It goes here with your name and your links, and follows every release you make.

The hub is free and stays free. If it saved you an evening: ☕ buy me a coffee.

Mail [email protected]
M-VAVE
V15

Official firmware

Back to M-VAVE's own: download FM-1 V15 from m-vave.com/download (PC Firmware → FM-1) and choose the file here: only that exact file is accepted.

Looking for Baud Girl or Groove OS? They are not open source, so they cannot be mirrored here: get them from their makers, baudgirl.com and groove-os.com.

Questions

Which custom firmwares are there for the M-VAVE FM-1?

All free and open source (GPL-3.0): Felucca, the custom firmware the others build on, and Felucca [Salt], its fork with a browser Studio; SLOOP, a live groovebox, and sloopDX, SLOOP with a DX7 inside; zp12, a 12-bit sampling drum machine; X0X, 909/808 drums and two 303s; FoMni, a chord harp; ChoralRoot, a chord instrument; Jangada, dark drones and ten engines; Melodee, a multi-engine synth; Hortator, an eight-track drum machine; FiMba-1, a kalimba. Make firmware, not war: you do not have to choose one for good.

How do I install a firmware on the FM-1?

In Chrome or Edge (they speak Web MIDI): connect the FM-1 by USB, press Connect the FM-1, then Install on the firmware you want. About a minute, the FM-1 restarts as a different instrument. No app, no driver, no file to download.

Why only open-source firmwares?

The hub lists firmwares that are free software, released with their source (GPL-3.0): so every package can be mirrored unchanged, checked and kept available, and anyone can see what it does. Closed or paid firmwares are not listed.

Where is Baud Girl? Where is Groove OS?

Both are fine firmwares for the FM-1, but neither is open source: there is no published source and no license that allows passing the package on, so this page may not mirror them, and it only lists firmware it can take unchanged from a public release. Install them from their makers: Baud Girl (free, tips on Ko-fi) and Groove OS. If either becomes open source with a release on GitHub, it goes on here the next day.

Is it always the newest version?

Yes. Every night the hub looks at each project's repository and offers its newest release, after checking that the package is an FM-1 firmware with the update loader. Betas are marked.

How do I go back to the official firmware?

Download FM-1 V15 from m-vave.com and install it with the box above. If the FM-1 is stuck, hold OCT− while switching it on (USB rescue) and install again.

What happens when you press Install

The page talks to the FM-1 over USB MIDI with the same update protocol as M-VAVE's own updater (first the running firmware stages the new package's update loader, then the loader writes the firmware). The package is checked first (its SHA-256 against the catalogue). Nothing goes to a server: the packages come from this page, mirrored unchanged from each project's GitHub release.