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.