Home›Articles›OberVave and Dinghy: an analog-style polysynth and the …
Articles

OberVave and Dinghy: an analog-style polysynth and the minimal base firmware beneath it

OberVave firmware turns the M-VAVE FM-1 into an analog-style polysynth, built on Dinghy, a minimal base. See what each does and why a small base matters.

Bernardo de Azevedo
Bernardo de Azevedo
· Updated
OberVave firmware: M-VAVE FM-1 pocket synthesizer beside a Nord Lead 4

The OberVave firmware turns the M-VAVE FM-1 into a single-purpose, analog-style polysynth, and Dinghy is the minimal base firmware it is built on. Both are published as open source under the GitHub name zvenson, the account that also hosts the sloopDX firmware, whose README credits Sven Trogus.

OberVave also appears as one of the modules in the FM-1 Dock multi-synth firmware by Joakim Eriksson. This article describes each project, then turns to a broader question: why a deliberately small base firmware matters for a community that has produced a growing number of firmwares for a roughly $70 instrument since its launch.

What the OberVave firmware is

According to its README, OberVave is an 8-voice polysynth firmware inspired by the American eight-voice poly synths of 1979 to 1984. It is one synth design rather than a set of different engines: four tracks, each with its own sound, arpeggiator and sequence, share the eight voices and feed a mixer, effects and a master section. The voices run in poly, dual, unison or mono mode, with glide.

Each voice has two oscillators with hard sync, cross-modulation, pulse-width modulation and noise. The filter is a state-variable design with low-pass, high-pass, band-pass and notch outputs, a cascaded 24 dB low-pass and SEM-style morph modes. Two envelopes, an LFO and a per-voice offset and drift control, which the README calls Vintage, supply the modulation.

On the effects side there are chorus, a tempo-synced ping-pong delay, a plate reverb and drive as send effects, followed by a master section with a DJ filter, compressor and soft limiter. The OberVave firmware also has an arpeggiator, a step sequencer, 99 program slots with 70 factory sounds, USB MIDI in and out and the FM-1’s TRS MIDI input. Because the chip has no floating-point unit, the code uses fixed-point integer maths throughout.

The README credits Andrew Simper for the trapezoidal state-variable filter design and Jon Dattorro for the 1997 plate reverb design. It also states that the OberVave firmware is not made by or affiliated with the owners of the Oberheim names it alludes to, and it notes that M-VAVE and FM-1 belong to their owners.

Four tracks, and which version is current

The track count depends on the version. The README says that the OberVave firmware has played four tracks since version 3.0, each with a sequence of up to 256 steps, and that tracks start and stop on the bar like clips.

Its change notes place a second sound on track B in 1.4 and the full-screen sequencer in 1.3. The FM-1 Dock page and the coverage of Dock describe OberVave as a four-track analog poly, which is consistent with the current README. Older descriptions that mention fewer tracks presumably refer to earlier releases, although the sources do not say so.

The version number is less settled. The README names 3.0.1 as the released version, with its package in the repository’s firmware folder and a listing on the Firmware Hub. The repository’s GitHub releases page, by contrast, shows v1.5.1 as the latest release, dated 18 October with the year not displayed. The two pages do not agree, so readers should check the README and the Hub before installing.

Dinghy: the smallest firmware to build on

Dinghy describes itself as the smallest firmware for the FM-1 to build your own on. Out of the box it plays a four-voice sine wave from the keys, and everything around that sound is already in place. That includes the update path over USB, a USB rescue mode, class-compliant USB MIDI on the USB port and the TRS jack, USB audio input, the panel controls, the 240 by 240 screen, settings saved to flash and a crash screen. The same app can also be built for the M-VAVE SMK-37 keyboard.

The place where a developer writes code is a single file, dinghy.c, which the README gives as about 300 lines in its file overview and about 200 lines in its first tutorial step. A separate platform file handles booting, USB, updates, the audio interrupt and settings.

A host mode runs the app on a computer and writes the screen as images and the sound as audio files, so work can be tested without hardware. The repository lists four tagged releases, from v0.1 to v0.4. The first three are dated 9 October and v0.4 is dated 23 October, with the year not shown on the page.

Dinghy is licensed GPL-3.0-only. Its README credits the platform to Leo Kuroshita of Hügelton Instruments, the author of Felucca, with changes made by isod89 for SLOOP.

The README’s status note says that version 0.3 was tested on an FM-1: the install, MIDI input with exact pitch and four voices, USB audio at both sample rates, the keys, the screen, octave storage in flash and a return to another firmware through the Firmware Hub.

Version 0.4 brings over the TRS MIDI input, MIDI clock, extra storage areas, the update loader’s screen and SMK-37 support from OberVave. According to the README, that code already runs on a device inside OberVave, but Dinghy 0.4 itself had been tested only on a computer. Its documentation set includes an API reference, a rules file and a guide to making the firmware one’s own.

Why a minimal base matters

The argument for a base like Dinghy is practical. The risky parts of an FM-1 firmware are the ones every project needs and few authors want to rewrite: flashing, recovery, USB and the timing-critical audio interrupt. A broken build can stop a unit from starting, which the Dinghy rules acknowledge by pointing to the FM-1-transporter tool for that case, and the site’s piece on why the device is hackable explains the background. Sharing a tested platform lets a new author start from working plumbing.

Dinghy’s documentation is notable because it states the constraints. Its rules file explains that the chip has no floating-point unit, that 64-bit division fails at link time, and that the audio callback has a budget of 5.8 milliseconds per 256 frames. It also says a flash erase halts everything, sound included, for tens of milliseconds. A build script rejects code that breaks several of these rules.

Recovery is part of the design. A fault shows a crash screen with the location of the fault, and two crashes during boot send the device into USB rescue mode. Holding OCT- at power-on forces the same mode.

The “make it yours” guide covers the organisational side. It tells authors to give each firmware a package identity of the form FM-1_9 plus two digits, so that installers can tell projects apart, and it notes that there is no registry, so authors must check the hub or ask.

It lists identities already used, including SLOOP, Felucca, sloopDX, zp12, a Doom port and Dinghy. To be listed on the FM-1 Firmware Hub, the guide requires public GPL-3.0 source, GitHub releases with the firmware file attached and a screenshot of the firmware’s screen, and it tells authors to ask through a card on the Hub.

For first projects, the guide suggests modest steps: a detuned second oscillator, per-key envelopes on the four knobs, a one-pole low-pass filter or a step sequencer on the white keys. It also points to zp12 and sloopDX as larger examples on the same platform. That ladder from a small starting file to a full groovebox illustrates the range the base is meant to support.

There are costs. A base inherits the assumptions of Felucca and SLOOP, and the GPL asks derivative authors to keep copyright lines and provide source. The identity scheme depends on convention, since the guide itself notes that no registry exists yet. These are reasonable trade-offs for a platform of this size, although they do tie derivative firmwares to the same licence.

FM-1 Dock: how OberVave reaches players

FM-1 Dock by Joakim Eriksson is one project built on Dinghy. Its README says it is based on Dinghy, and its project page explains that users install Dock once, then hold HOME to choose a synth module without reflashing. The package includes CS-1, Scintilla, OberVave and a sine module, with FM-1 SID, AMB-1 and FoMni available as one-click additions.

The Dock page describes the OberVave firmware as a module of 149 KB with 8 voices, with its pages, presets and patterns kept in Dock’s banks. The built-in sine is Dinghy’s own four-voice sine, which Dock keeps as a fallback if a module fails and as the smallest module to copy. MatrixSynth and Synthtopia both covered Dock on 26 October 2026, and Synthtopia lists OberVave among the engines in the preview video.

Other targets and version confusion

The OberVave README and licensing file record several further details. The README links a browser simulator that compiles the firmware’s own C sources to WebAssembly, and the licensing file credits it to zvenson. The README also lists support for the M-VAVE SMK-37 keyboard, where the board layer is credited to M. Geisler and comes from the smk37 branch of his SLOOP fork.

The Firmware Hub shows a card titled “VIBE Native VST”, subtitled “Made for VIBE FM, in your DAW” with the label OberVave 3. The README says that version 3.0 brought OberVave’s VIBE edition back to the FM-1, which suggests a shared lineage, although neither page spells out how the plug-in and the firmware relate.

The Hub’s disclaimer lists OberVave and Dinghy, together with zp12, sloopDX and Shine On, as the only projects it calls its own. Shine On is not described on the Hub’s page or in the projects’ READMEs.

Installing and trying them

The OberVave firmware can be installed from the FM-1 Firmware Hub or with the project’s Python installer, and Dinghy offers the same two routes. This article does not give steps. The READMEs carry the project’s own instructions and warnings, and the site’s install and recovery guide explains the general precautions.

One warning in the OberVave firmware README deserves repeating. It tells users not to install version 1.1, because its USB MIDI output is broken, and says that version 1.2 fixed this. Building Dinghy from source requires JieLi’s toolchain and three files from its AC79 SDK, which makes the source route a developer task.

Reception and limits

Direct commentary on the OberVave firmware is thin. On the Elektronauts FM-1 thread, a user named GHRS said in post 418 that OberVave appealed as a synth rather than a bunch of different engines, and added in post 526 that its interface looked nice but that they had not tried it. Function1 wrote in post 463 that Oberwave, as the name is spelled there, and Melodee sounded better than some much more expensive synths, while noting that they had not tried many of the firmwares.

These are individual forum remarks, not tests. The README does not state a hardware test list for the OberVave firmware, and the Firmware Hub’s page text does not describe either project. Independent reviews would be needed to judge sound quality and stability.

Final perspective

The OberVave firmware shows what a focused instrument can look like on a small device, while Dinghy supplies the less glamorous groundwork that lets such projects exist. The base matters more than its size suggests, because its recovery behaviour and written rules reduce the chance that a new author bricks a unit.

The unresolved point is the version numbering, since the README and the releases page do not agree. For now, OberVave and Dinghy are best treated as active projects whose details should be confirmed on their own pages.

Sources

  1. OberVave README, zvenson/obervave, GitHub
  2. OberVave licensing notes, GitHub
  3. OberVave releases, GitHub
  4. Dinghy README, zvenson/dinghy, GitHub
  5. Dinghy 0.1 release, GitHub
  6. Dinghy rules, GitHub
  7. Dinghy make-it-yours guide, GitHub
  8. fm1-dock README, GitHub
  9. fm1-dock project page, Joakim Eriksson
  10. FM1 Dock: One FM-1 firmware, many synths, MatrixSynth
  11. Latest FM-1 Firmware Lets You Load 4 Synth Engines & Swap Them On The Fly, Synthtopia
  12. The FM-1 Firmware Hub, thefirmwarehub.com
  13. M-vave fm-1, posts 418, 463 and 526, Elektronauts
  14. Dinghy releases, GitHub
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.