MD-One
MD-One replaces its firmware with four Braids oscillators, tuned combs and a modulation system, delivering into a DAW over USB audio.
- Custom firmware
- Beta
- Medium brick risk
- Reversible
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Before you start
- How hard is it?
- EasyWith Slipway.
- What you need
- Comfort with the command line
- A computer
- Can it break my device?
- Small chance of trouble, with a way to recover.
- Can I undo it?
- Yes. You can go back to the official software.
Did it work for you?
Did MD-One work on your M-VAVE FM-1?
No reports yet.
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 ("Quick start"):
references + toolchain (once) .\scripts\clone-references.ps1 .\scripts\fix-line-endings.ps1 -Force wsl -d archlinux -- bash scripts/setup-wsl-toolchain.sh wsl -d archlinux -- bash scripts/verify-toolchain.sh
emulator cd references\fm1-emu; cargo build --release -p fm1-emu -p fm1-live; cd ....
build everything and RUN it -- the gate before any commit wsl -d archlinux -- bash scripts/check-all.sh
check-all.sh builds the DSP tests, the chip-rule check, the host renderers, the three target probes and the firmware, then loads the firmware into the emulator and asserts it boots and makes a sound. Compiling is not verifying: three consumers of the parameter table sat broken for days because nothing built them together.
Exact commands and their real output: docs/BUILDANDTEST.md.
Risk and recovery
- Brick risk
- Medium
- Reversible
- Yes
- Requires opening the device
- No
From the project's README ("Two decisions already forced"):
- Licence. Dinghy is GPL-3.0-only, so our firmware will be too, and everyone we hand a build to is entitled to the complete source. If the engine must ever be proprietary, that has to be decided now — the alternative is writing the USB stack, update path, rescue mode and HAL from scratch. docs/LICENSEREGISTER.md.
dsp/ is kept MIT and free of GPL code so the synthesis engine stays reusable.
- Flashing, and how to come back. Single flash bank, no recovery button, no test pads, no debug header, and updates authenticated by CRC-16 with no signature. One SysEx byte separates "upgrade" from "mask-ROM download mode".
This section used to say "No flashing" and list the gate that had to be satisfied first. That gate has been satisfied and the device has been flashed many times since. What replaced it is a rescue reachable from a running firmware — OCT− and OCT+ held for five seconds — walked end to end on the device: running → rescue → flash → running. A build that boots but misbehaves is provably recoverable; a build that does not boot at all rests on a path nobody here has exercised. docs/FIRMWARESAFETY.md has both.
Credits, license and support
- License
- GPL-3.0