FN ACID
This fork is FN ACID, an FM-1 firmware where every track is a function y(s, φ) drawn on one pair of axes and played as it is drawn, after AA (@measureplan) "trying to turn math into acid".
- Custom firmware
- Alpha
- Medium brick risk
- Reversible
Source codeWebsite: fn-acid.netlify.app
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?
- EasyCopy a file or use a web page. No extra software.
- What you need
- A USB or MIDI cable
- 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 FN ACID 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 ("5. Onto the FM-1"):
./build.sh # -> build/dinghy.fwsc (fails on what would brick the FM-1) python3 tools/fm1install.py build/dinghy.fwsc # over USB; asks before it writes, restarts into your build python3 tools/fm1install.py --info # what runs on the connected FM-1
That is the whole loop: change, hear it on the host, build, install. Back to another firmware, or to the official one, with the FM-1 Firmware Hub in Chrome or Edge: Dinghy (and every copy of it) answers the hub's updater like every firmware there. Installing firmware is at your own risk.
Risk and recovery
- Brick risk
- Medium
- Reversible
- Yes
- Requires opening the device
- No
From the project's README ("6. When it goes wrong"):
- It crashes: the screen shows where (the PC), then the FM-1 restarts. Twice at boot and it goes to the USB rescue by itself.
- It won't start at all: hold OCT- while switching on: the USB rescue, no sound, only the updater. Install a working build (or another firmware from the hub) from there.
- The build refuses: it checks for a 64-bit division, a call into the chip ROM, too much RAM, a register touched outside hal/. docs/RULES.md says why each one matters; read it before your first crash.
Credits, license and support
- License
- GPL-3.0