TheReFmB1rth
Experimental replacement firmware for the M-VAVE FM-1: a compact four-machine acid groovebox inspired by the classic two-bassline/two-drum-machine workflow.
- Custom firmware
- Beta
- Low brick risk
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
TheReFmB1rth v0.1.0-beta.18 — corrective FM-1 beta
This prerelease contains the corrective hardware architecture produced after the first physical FM-1 test exposed disconnected Felucca/ReFm control paths, plus the browser/readback and runtime-diagnostic work added since beta.1.
Built from commit 5e2cc6fa89cb34241e40241054abc3433d4743e0 only after that exact commit passed host DSP/integration tests, the browser/WASM build, JieLi FM-1 target compile/link, target memory budgets, package manifest/checksum verification and the target sample link-size experiment.
Physical workflow
- dedicated 240×240 ReFm pages: HOME / ACID / STEP / DRUM / MIXER / FX / SONG / PROJECT
- physical keyboard routed directly to the selected ACID A / ACID B engine
- physical PLAY starts/stops the ReFm sequencer instead of Felucca's old audible sequencer
- fresh Pattern A contains an audible factory demonstration for immediate PLAY testing
- 16-step ACID editing with NOTE / REST / TIE, Accent, Slide and probability
- 808/909 lane editing with OFF / HIT / ACCENT
- mixer level/pan/delay/reverb plus mute/solo and master FX editing
- four project save/load slots using Felucca's CRC-checked storage
- held-note panic on editor-page/machine transitions
- target-only idle ACID fast path to reduce wasted DSP work
Browser/editor additions
- device-to-browser live state synchronization
- START / CONTINUE / STOP through the firmware MIDI realtime path
- full A–H ReFm project backup and restore using the versioned project codec, project CRC and chunked SysEx transport
- restore changes live RAM only; persistence still requires the normal FM-1 project SAVE action
- one-click read-only runtime diagnostic capture for CPU, DMA lateness and user/supervisor stack headroom
- downloadable runtime JSON compatible with
tools/target_runtime_report.py
Physical beta gates shown in the browser
- zero DMA deadline misses
- sustained audio CPU <= 75%
- peak render <= 82% of one DMA-half deadline
- user-stack free headroom >= 4096 bytes
- supervisor/ISR-stack free headroom >= 1024 bytes
Install asset
TheReFmB1rth-experimental.fwsc
Verification assets
SHA256SUMSmanifest.jsontarget-memory.jsonrefm-overlay.txtrefm-ui-overlay.txt
Status
This remains software-gated beta firmware, not hardware-proven stable firmware. The next required step is the second physical FM-1 pass covering LCD/control behavior, live keys, Pattern A, sustained stress diagnostics, USB/TRS MIDI, USB audio, project persistence and rollback/recovery.
Keep the verified official V15/recovery path available while testing. No custom firmware has a zero-brick guarantee.
Before you start
- How hard is it?
- EasyCopy a file or use a web page. No extra software.
- What you need
- Nothing beyond the device, as far as the project says.
- Can it break my device?
- Very unlikely to break anything.
- Can I undo it?
- The project doesn't say. Assume you can't.
Did it work for you?
Did TheReFmB1rth v0.1.0-beta.18 work on your M-VAVE FM-1?
No reports yet for v0.1.0-beta.18.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: M-VAVE FM-1.
No compatibility information yet.
Getting started
From the project's README ("Browser installer"):
The browser release loader reads the CORS-safe firmware-channel/latest.json, then verifies that exact tag through GitHub's releases/tags/ endpoint, verifies the exact .fwsc asset name and SHA-256, and only then enables the package. It does not depend on GitHub's release-list ordering.
Risk and recovery
- Brick risk
- Low
- Requires opening the device
- No
Releases
| Version | Name | Released |
|---|---|---|
| v0.1.0-beta.18 | TheReFmB1rth v0.1.0-beta.18Pre-release | 16 October 2026 |
| v0.1.0-beta.17 | TheReFmB1rth v0.1.0-beta.17Pre-release | 15 October 2026 |
| v0.1.0-beta.16 | TheReFmB1rth v0.1.0-beta.16Pre-release | 15 October 2026 |
| v0.1.0-beta.15 | TheReFmB1rth v0.1.0-beta.15Pre-release | 15 October 2026 |
| v0.1.0-beta.14 | TheReFmB1rth v0.1.0-beta.14Pre-release | 15 October 2026 |
| v0.1.0-beta.13 | TheReFmB1rth v0.1.0-beta.13Pre-release | 15 October 2026 |
| v0.1.0-beta.12 | TheReFmB1rth v0.1.0-beta.12Pre-release | 15 October 2026 |
| v0.1.0-beta.11 | TheReFmB1rth v0.1.0-beta.11Pre-release | 15 October 2026 |
| v0.1.0-beta.10 | TheReFmB1rth v0.1.0-beta.10Pre-release | 15 October 2026 |
| v0.1.0-beta.9 | TheReFmB1rth v0.1.0-beta.9Pre-release | 15 October 2026 |
| v0.1.0-beta.8 | TheReFmB1rth v0.1.0-beta.8Pre-release | 15 October 2026 |
| v0.1.0-beta.7 | TheReFmB1rth v0.1.0-beta.7Pre-release | 14 October 2026 |
| v0.1.0-beta.6 | TheReFmB1rth v0.1.0-beta.6Pre-release | 14 October 2026 |
| v0.1.0-beta.5 | TheReFmB1rth v0.1.0-beta.5Pre-release | 14 October 2026 |
| v0.1.0-beta.4 | TheReFmB1rth v0.1.0-beta.4Pre-release | 13 October 2026 |
| v0.1.0-beta.3 | TheReFmB1rth v0.1.0-beta.3Pre-release | 13 October 2026 |
| v0.1.0-beta.2 | TheReFmB1rth v0.1.0-beta.2Pre-release | 12 October 2026 |
| v0.1.0-beta.1 | TheReFmB1rth v0.1.0-beta.1Pre-release | 12 October 2026 |
| hardware-test-0.1.3 | TheReFmB1rth hardware-test-0.1.3Pre-release | 12 October 2026 |
| hardware-test-0.1.2 | TheReFmB1rth hardware-test-0.1.2Pre-release | 12 October 2026 |