A Dabbl music project · In development
Dabbl8
An open-source firmware project for the M-VAVE FM-1, working toward an eight-track instrument for making music.
Development update · 12 October 2026
From foundations to an eight-track prototype
The unchanged Felucca v1.1.5 baseline has been built and tested on a Mac. The development source now includes an eight-track prototype, with host and simulator checks for sequencing, project compatibility, shared storage and arrangement playback. Recorded full-engine software checks preserved all 92 reference audio results. A target build fits the measured memory limits, but has little spare memory; this does not establish reliable performance on an FM-1.
There is no qualified Dabbl8 firmware release offered here. Timing checks still flag work to resolve. The development source includes stopped-project saving and a first-use storage workflow, but their operation on a physical device remains unqualified. Full device timing, stack use, persistence, recovery and independent tester checks remain outstanding. Host tests and a successful build do not establish installation, playback or recovery on an FM-1.
The planned eight-track workflow
The aim is eight independently sequenced tracks, with track selection, a mixer, automation, MIDI and project editing that work together. Migration from previous firmware is not required for the first release; Dabbl8 starts with its own project format.
Eight tracks will initially share a budget of eight sounding voices. A track is a place to sequence a part; it does not get eight voices of its own. Work is progressing through small review branches. The roadmap records which parts have passed software checks and which still require integration or hardware testing.
Built on Felucca
Dabbl8 is based on Felucca, created by Leo Kuroshita (@kurogedelic) and Hügelton Instruments. Its existing synthesis, sequencing and tooling are upstream work, credited to their creators.
The firmware retains GPL-3.0-only licensing and the notices for its dependencies. See the licensing and credits for the full provenance. Dabbl8 is an independent community project.
Projects, with room to grow
The planned device workflow uses three native project slots and a shared autosave; the storage model has passed host checks. Storage is shared across the projects rather than reserving two copies for each slot. The aim is to keep all three user sample slots while making room for larger eight-track projects.
First installation is designed to reset data from previous firmware: projects, autosave, settings, user presets and user samples. Do not expect those files to survive a switch to Dabbl8. This reset is part of the development policy; the physical installation and reset procedure has not yet been verified.
Subsequent supported Dabbl8 upgrades are intended to preserve supported Dabbl8 data. Own-project backup and restore remain required, with physical verification still outstanding; existing offline conversion research does not establish a device recovery procedure. Follow the tooling work and storage work for reviewed evidence.
Planned software voice cards
We’re developing a way to choose a set of synthesis engines that fits the FM-1’s resources. Experimental Core and Breaks developer builds explore smaller engine sets and reduce their shared engine storage. They are under review and have not been qualified on a device.
The plan is to offer tested combinations, with clear limits for each sound set. A selection tool and genre-based suggestions may follow once the supported combinations are established. Every choice needs its own memory, timing, project compatibility and recovery evidence; eight tracks still share eight sounding voices.
These are development plans, with no firmware downloads offered here. Follow the software voice-card work and effects resource investigation for the current evidence and remaining checks.
Requirements and recovery
The intended hardware is the M-VAVE FM-1. Support for other devices is not established. Developer builds and tests are documented in the firmware repository.
A stock vendor firmware file has been obtained and its hash verified for future restore testing. That does not establish a working recovery procedure. Device qualification, project backups and a tested route back to stock firmware are release gates.
Verified installation requirements, limitations and recovery instructions will be linked here with a qualified release. For now, follow the roadmap and release notes for evidence as it becomes available.