Home›Articles›MONO2K: a Monomachine-style firmware for the FM-1, meas…
Articles

MONO2K: a Monomachine-style firmware for the FM-1, measured against the original

MONO2K firmware turns the M-VAVE FM-1 into a six-track, Monomachine-style synth with p-locks and a lofi bus. Features, install notes and limits.

Bernardo de Azevedo
Bernardo de Azevedo
· Updated
MONO2K firmware: M-VAVE FM-1 pocket synthesizer beside the Elektron Monomachine SFX-6

MONO2K is a custom firmware for the M-VAVE FM-1 that borrows the working method of Elektron’s Monomachine: six tracks, one synthesis machine per track, a sequencer with parameter locks and a deliberately dirty output stage. It is published by a developer who works under the name Sequencist and whose GitHub account is InigoHernandez. The MONO2K firmware raises a pointed question, namely how closely a pocket synth can follow a 2004 design when, by the author’s account, every machine is written from scratch and checked against the original with measurements.

Table of Contents

What the MONO2K firmware is

The project describes itself as a Monomachine-style firmware with a 1-bit, 240 by 240 screen, dithered type and machine icons. The Elektron Monomachine was produced from 2004 to 2016, offered six tracks and stored a snapshot of track parameters on each sequencer step. MONO2K reproduces that workflow on the FM-1 rather than the DX7-style voice the device ships with, which is covered in the M-VAVE FM-1 profile.

The MONO2K firmware code is GPL-3.0-only according to the README, which says it is built on open FM-1 work including Felucca and carries that project’s update loader. The project’s pages state that it is not affiliated with Elektron or M-VAVE.

The interface follows from that borrowed logic. Each knob value is drawn as a small picture (dials, sliders, curves, wave shapes) in the manner of Elektron’s parameter pages, and machine icons move in time with the pattern. The screen can be set to a light or dark scheme. It is an unusual choice of identity for a firmware that could have settled for text lists, and it will not suit everyone.

The same core also runs in a browser through WebAssembly, so the project page doubles as an emulator, with a patch editor and a manual beside it. That is a practical way to judge the interface of the MONO2K firmware before owning the hardware.

Six tracks, nineteen machines

The tagline mentions six mono machines, which is slightly misleading. According to the manual, each of the six tracks hosts one machine, and the player chooses from nineteen. They are grouped in families: sine and noise tones, three SuperWave-style variants (saw, pulse, ensemble), a digital wave machine, a formant voice, a SID-6581 chip voice, three FM machines, four drum voices and three effect machines.

The effect machines make no sound of their own. They process the track before them, so a source on track 3 can be followed by a chorus, ring modulator or dynamics stage on track 4. The drum voices are described as modelled on the voices of Erica Synths’ LXR, with the page stating that none of that instrument’s code or samples are used.

Each track also has its own chain. The amplifier section covers attack, hold, decay, release, distortion and portamento. The filter combines high-pass and low-pass in one band described by a base and a width. Further pages add EQ, sample-rate reduction, an 8-bit mu-law delay, bit crushing, wavefolding and an XOR mangler, plus three LFOs per track and an arpeggiator.

Sequencer and lofi bus

The sequencer has 64 steps per track and supports parameter locks, according to the project page and README. Each step can trigger the amplifier, the filter envelope and the LFOs independently, giving eight trig states from ALL to NONE. The README describes a trigless lock among them, which is the kind of detail that Monomachine owners will recognise.

Conditions include chance steps, A:B loops, first and previous-step tests and fill logic, and a step can ratchet one to four times. Tracks can run their own length and speed, so polymeter is built in. A drum pattern generator ported from Mutable Instruments’ Grids is also included under the same licence.

The signature of the firmware is the bus. A feedback-delay reverb with a tail from 0.3 to 24 seconds, a 4-bit ADPCM crunch and a drive into a soft clip sit on the master. A PERFORM mode, reached by holding FX, then turns the black keys into bus effects such as repeats, reverse, stutter, freeze, scatter and shimmer. Read in sequence, the manual suggests an instrument meant to be played and broken live rather than programmed and left alone.

The factory content points the same way. According to the README, bank A of the demo project holds four parts named CIRCUIT, TIDE, SUSPEND and LANTERN, and the README adds that their sounds were drawn at random and picked by ear. The manual says the sound library has 128 slots, of which 96 are factory sounds, twelve in each of eight categories.

Calibrating against the original

The most distinctive part of MONO2K is its documented testing. The project page says the machines were measured against a Monomachine running in a community emulator, by playing identical notes and knob settings on both and recording levels, spectra, times and stereo behaviour. It reports 944 cases, grouped by topic, and 2,605 measured numbers kept, and it calls the reference “measurements only, no code or data”, the same line the README applies to the emulator.

The README adds that the owner’s own Monomachine OS image is read from a local path and never copied into the project, so no ROM or recordings are in the repository. It also keeps a candid list of known gaps, each held to its measured size by a regression script. One example is FM feedback above roughly 44, where the original’s carrier drifts off the note and MONO2K’s stays harmonic until it aliases.

These figures and the description of the method are the author’s own, and they have not been independently reproduced. The project page describes the machines as written from scratch and the README calls them “clean-room designs”, but both are the author’s own characterisation of the work, not a legal finding or an endorsement by this site about its relationship to Elektron’s software. No independent review of the sound had been published at the time of writing. The method is nevertheless documented in enough detail to be checked by someone who owns both instruments.

The author and the neighbouring firmwares

The author links Bandcamp, SoundCloud, YouTube and Instagram pages under the Sequencist name, and the Firmware Hub credits the work to Iñigo Hernandez. His GitHub profile lists MONO2K as a pinned repository with 16 stars at the time of writing. The first page of the release list shows ten tagged releases between 25 and 30 October, ending with version 1.6, so the project is changing fast. The list continues on a second page, so earlier versions may exist.

Compared with Felucca, which the author’s own README credits as one of its foundations, MONO2K is narrower. Felucca’s page lists thirteen engines, four tracks and a modulation matrix for a general-purpose instrument. MONO2K gives up that breadth for a single design language borrowed from one machine. Against a looper-led groovebox such as SLOOP, the emphasis is also different: pattern programming and sound design on the track, rather than live layering.

A companion firmware by the same author, Demake, shares the platform but follows a different idea and is treated separately.

What the community makes of the MONO2K firmware is harder to say. The Synthtopia overview of alternative FM-1 firmware was posted on 4 October, before the first MONO2K release, so its silence says nothing either way. No press coverage or user comments had been located at the time of writing, so there is no outside opinion to report here.

Installing, backing up and leaving

There are two routes, both documented by the author. The installer page works in Chrome or Edge over a data USB cable with MIDI SysEx permission, and the firmware is also distributed through The Firmware Hub. Anyone flashing it should read the project’s own warnings first and the site’s safe install and recovery guide.

Several points from the author’s pages deserve attention before installing the MONO2K firmware. MONO2K stores its single 64-pattern project and sound library in the last 128 KiB of the FM-1’s data area, and the README warns that its first save overwrites whatever another firmware kept there. Patterns live in flash and do not survive a return to M-VAVE’s official V15 firmware. The patch editor can read the store over USB and save it as a file, which is the recommended backup. Holding OCT− at power-on starts a rescue loader.

Limits and open questions

The FM-1 build keeps one project of 64 patterns, with the factory demos in bank A, which the manual says leaves room for roughly 20 to 30 patterns of the user’s own. The emulator keeps four projects, so work moving to hardware needs pruning. A CPU meter on the global page shows load, and near 100% the sound drops out and the header reads CPU FULL.

MIDI is partly constrained in the MONO2K firmware. Channels 1 to 6 address the six tracks, but velocity is ignored and notes always trigger everything, while parameters unique to MONO2K, such as the destroy effects and the arpeggiator, have no controller numbers. The CC map for the shared parameters follows the Monomachine’s.

Load is a related unknown. The README, which may lag the releases, lists an on-device CPU reading of two of the heavier demo patterns as pending, while the release notes for version 1.4.2 say the two processors now share the tracks evenly and that the heaviest patterns need about 10% less processing time. In practice the CPU meter is the thing to watch on dense patterns.

Documentation is inconsistent, which is natural at this release rate. The status section of the project page reads 1.1, the manual 1.0, the README’s status line 1.0, and the release list 1.6. Treat any version number here as a snapshot. The README also lists further machines and a power-cut-safe store as future work.

Final perspective

The MONO2K firmware is best read as a study in fidelity rather than a general FM-1 upgrade. Its choice to measure, document and publish gaps gives it a documentation trail that a feature list alone would not, though the results remain the author’s own, and the depth of the sequencer is the obvious draw. The cost is that it demands attention: pages of knobs, trig logic and a bus that is meant to degrade the sound.

Owners who never touched a Monomachine may find the learning curve steep, and those who want to keep other firmware’s data on the device should heed the flash warnings. For readers curious about Elektron-style programming on a very small budget, the browser emulator makes a low-risk first step, and the MONO2K firmware can then be judged on hardware only if the flash warnings above are acceptable.

Sources

  1. MONO2K, Six mono machines for the M-VAVE FM-1, Sequencist
  2. MONO2K manual, Sequencist
  3. MONO2K installer, Sequencist
  4. InigoHernandez/mono2k, GitHub
  5. MONO2K releases, GitHub
  6. InigoHernandez profile, GitHub
  7. Felucca, GitHub (Hügelton Instruments)
  8. The Firmware Hub, The Firmware Hub
  9. Elektron Monomachine, Wikipedia
  10. Alt Firmware Options For The M-Wave FM-1 Pocket Synthesizer, Synthtopia
Bernardo de Azevedo
Written by
Bernardo de AzevedoFounder & Editor

His connection with music began at age 6, in the 1980s, when his father introduced him to Jean-Michel Jarre's Rendez-Vous on vinyl. He works professionally in the legal field, while synthesizers became his space for abstraction and creative exploration. Founder of The Synth Source.