The code is GPL-3.0-only, with the Dexed core under Apache-2.0, the Terminus font under the SIL Open Font License and the icons under MIT. The README also notes that DX7 is a Yamaha trademark.
Installing the sloopDX firmware and going back
The README lists three routes: a browser installer used from Chrome or Edge, a Python script that takes a firmware package, and building from source. The browser route needs a data cable connected directly to the FM-1 without a hub. This article does not repeat the steps, because the project documents them and because the details change between versions.
Readers should read the author’s warnings before flashing. The project page says that an interrupted update can leave the device unable to start, and the README states that custom firmware is installed at the user’s own risk. The README is somewhat more specific about recovery: a cut-off install leaves the FM-1 in update mode, where pressing Install again finishes it, and holding OCT- at power-on starts a USB rescue mode.
For a unit that no longer starts at all, it points to the separate FM-1-transporter tool. The README also explains how to return to SLOOP or to M-VAVE’s official V15 firmware, and advises backing up first because sloopDX projects may refer to sounds that SLOOP lacks. The site’s safe install and recovery guide covers the general precautions.
Strengths and limits
For the sloopDX firmware, the clearest strength is the candour of the documentation. The README separates what was tested on a unit from what was not, which is more than many hobby firmwares offer. Open code, a stated licence, a backup and restore function in the editor, and a documented route back to stock all lower the risk of trying it.
The limits are mostly about maturity. The README says version 3.5 was installed and played on a real FM-1, covering the boot screen, the DX7 voice list, the flash voice bank, drum kits and levels. It also says version 4.0 has not yet been run on a device, so the second core, the MIDI features inherited from SLOOP 2.6 and 2.7, the web editor end to end, processor load with three synth tracks and drums, USB audio and the MIDI input jack are all unconfirmed.
Two further cautions apply. Projects saved in 4.0 do not open in 3.x, and two arpeggiator settings must be reset before downgrading. The documentation also says that its screens are host renders of the firmware’s drawing code, with the sound rendered by the engine, so they illustrate the software rather than a captured device.
One discrepancy remains open. The repository’s releases page lists only v2.6, v2.4, v2.3 and v2.1 at the time of writing, while the README and project page describe version 4.0 as the newest and 3.5 as the last version played on a device. The README says the installer page carries the current package and refers to a 3.5 package file in the repository, so the browser installer is the documented route to the current build, and the numbering of the tagged releases does not match it.
How sloopDX compares with related projects
Against SLOOP, the sloopDX firmware narrows the focus to DX7-style FM. SLOOP’s own description in Synthtopia’s roundup of alternative FM-1 firmware centres on three synth layers and a drum machine built from Felucca’s engines. sloopDX keeps the structure and gives users a DX7-compatible patch library, which makes sense for anyone who already owns bank files.
Baud Girl’s FM-1+VA is a close relative in spirit, since the sloopDX README credits it for the idea behind the on-device voice list. The Lunar Modulator project, which will be covered separately, lists an FM6 engine built on the same msfa code, so at least two community projects draw on that code.
On reception, the Firmware Hub’s disclaimer lists sloopDX among the five projects it calls its own. No dedicated review or forum comment on sloopDX was available at the time of writing, so this article does not report user reactions.
Final perspective
The sloopDX firmware is a considered extension of SLOOP aimed at users who want DX7-style programming and FM drums inside a groovebox workflow. Its documentation is frank about gaps, and its reliance on Dexed gives it a verifiable reference point. The main weakness is that the 4.0 features, which carry much of the appeal, were untested on hardware at the time of writing.
A cautious approach suits the sloopDX firmware: back up, read the README, and check the project pages for newer test notes before relying on version 4.0 in a performance. Those details are likely to change quickly.
Sources
- sloopDX README, zvenson/dxsloop, GitHub
- sloopDX installer and editor page, zvenson / designburgapps.com
- dxsloop releases, GitHub
- zvenson profile, GitHub
- The FM-1 Firmware Hub, thefirmwarehub.com
- Alt Firmware Options For The M-Wave FM-1 Pocket Synthesizer, Synthtopia