M-VAVE FM-1 Workbench: GPLv3 app, FM1-only binary engine
M-VAVE has published the FM-1 Workbench on open.m-vave.com, a workbench for its FM-1 synth device. The text available for this retelling is the copyright and licence notice with the third-party notices file (THIRD_PARTY.md), so it covers licensing and provenance, not what the workbench does.
The headline terms: the APP is licensed under GPLv3 with an FM1 SDK linking exception, with no warranty. The notice links to the source as the FM1-Open-V14-Development-Kit zip. SDK and firmware resources have separate redistribution terms. The FM-1 V15 recovery firmware is downloaded from m-vave.com/download (PC Firmware / FM-1 V15) and is distributed by M-VAVE under Apache-2.0.
The proprietary part is the engine in sdk/lib/libfm1_engine.a. For the components M-VAVE owns or has authority to license, it grants each recipient a non-exclusive, royalty-free permission to do three things: download, retain and copy them for developing and using firmware on M-VAVE FM1 devices; link them with the APP or a modified APP, then build, install and run the resulting firmware on FM1 devices; and redistribute them in binary form, either as separate SDK components or as part of firmware and firmware-inclusive workbenches for FM1 devices, for commercial or non-commercial purposes. Redistributions must keep the copyright and licence notices and include the file. No proprietary SDK source is supplied. The FM1-only condition applies to this engine grant; the APP, third-party components and separately licensed resources keep their own rights and terms. Complete packages must comply with each component's licence, including any corresponding-source requirements. M-VAVE supplies the proprietary components as-is, without warranty, and says it is not liable, to the extent the law permits, for losses from their use, including data loss or device malfunction.
The boot and update files in sdk/tools/pack (uboot.boot, ota.bin, cfg_tool.bin, boot-config.bin) and the recovery image sdk/firmware/FM-1_015.fwsc are distributed by M-VAVE under Apache-2.0. Redistribution, including binary redistribution for commercial or non-commercial purposes, is allowed subject to that licence: include the licence, mark modified files, and keep copyright, attribution and NOTICE material. These permissions do not change the APP's GPLv3 licence or the engine's separate terms. A Chinese-language version of the grant is included alongside the English text.
The third-party table shows what the firmware and web builds borrow. Open303 (MIT) is adapted in C for the 303 voice, with FM1 drive and MIDI handling. DaisySP (MIT) supplies selected Plaits drum and String models for the 808 and Pluck voices. stmlib (MIT) supplies a fixed-rate filter adaptation for the SVF. The FM model derives from Google's MSFA and Dexed's msfa (Apache-2.0), as a C adaptation of algorithms, envelopes, LFO and note scaling with FM1 arithmetic and controls. The PSG uses emu2149 (MIT), with a memory and table adaptation and an ultrasonic output fix. The SEA codec (MIT) provides a fixed-format encoder, decoder and tables, and the packager adapts jl-misctools (MIT) with FM1 validation and layout. The SDK libraries include Newlib-derived C runtime routines, compiler-rt routines under legacy MIT and University of Illinois-NCSA notices, identified micro-ecc routines (BSD-2-Clause) inside libfm1_engine.a, and identified material from the JieLi AC79 SDK, which keeps its upstream terms. The notices also reproduce FreeRTOS (MIT, Amazon.com 2017), micro-ecc (BSD-2-Clause, Kenneth MacKay 2014) and the MIT licence text for the other components.
Two provenance details stand out. The APP and open web engine tuning incorporate contributions by Vikram Rojo (PR #2 in the m-vave/fm1_open repository), with FM1 integration changes dated 2026-10-17. And the original 128-voice DX7 bank in app/fm_factory.inc was extracted, without parameter or ordering changes, from the bundled M-VAVE V15 recovery image (Apache-2.0) and losslessly encoded for Flash in 2026. It can be reproduced with node tools/Generate-Factory-DX7.mjs, which pins the source package and decoded VMEM SHA-256 hashes; demo project recipes remain separate. Company-authored FM1 modifications, FX, arrangements and synthesized demo samples are Copyright (c) 2026 M-VAVE. Product names identify compatible formats, and no upstream endorsement is implied.
Key facts
- The FM-1 Workbench APP is licensed GPLv3 with an FM1 SDK linking exception, with no warranty; source is linked as the FM1-Open-V14-Development-Kit zip.
- The proprietary engine in libfm1_engine.a is binary-only: M-VAVE grants a royalty-free, non-exclusive permission to use, link and redistribute it for M-VAVE FM1 devices, and supplies no source.
- The FM-1 V15 recovery firmware and the boot/update files are distributed by M-VAVE under Apache-2.0.
- The firmware builds on open code including Open303, DaisySP/Plaits, stmlib, MSFA/Dexed, emu2149, the SEA codec and jl-misctools, mostly MIT, with the FM model under Apache-2.0.
- The factory sound bank is the original 128-voice DX7 bank, extracted from the V15 recovery image, and the APP incorporates a contribution from Vikram Rojo (PR #2) dated 2026-10-17.
Why it matters
Hardware makers often ship a device with closed firmware and little documentation. Here M-VAVE spells out a mixed model for the FM-1: the app under GPLv3, the recovery firmware under Apache-2.0, and one proprietary binary engine with a clear grant. The notice also shows which open synth code the device builds on, including Open303, Plaits models from DaisySP and the Dexed/MSFA FM engine.
Who it affects
Owners of the M-VAVE FM-1 who want to modify the app or build firmware, and developers who might redistribute firmware or workbenches for the device. Anyone reusing the code needs to follow the licence of each component, since the notices say the APP, third-party parts and separately licensed resources each keep their own terms.
How to use it
The notice points to the FM1-Open-V14-Development-Kit zip for the APP source and to m-vave.com/download (PC Firmware / FM-1 V15) for the recovery firmware. Per the grant, you may link the proprietary engine with the APP or a modified APP and run the result on M-VAVE FM1 devices. Redistribution must keep the copyright and licence notices and include the notices file. The DX7 bank can be reproduced with node tools/Generate-Factory-DX7.mjs.
How solid is it
The licence statements come straight from M-VAVE's own page, so they are first-party. The verified source text is only the licence and third-party-notices section; it does not describe the workbench's features, UI, supported operations or how it connects to the device. No release or publication date of the workbench is given; the only date is 2026-10-17, attached to the Vikram Rojo contribution. The licence text is cut off in the source, so the SDK notices and the full licence texts are not fully visible.
Risks and caveats
The proprietary engine is usable only on M-VAVE FM1 devices, so it cannot be moved to other hardware, and no source for it is supplied. It comes as-is, without warranty, and M-VAVE disclaims liability for losses such as data loss or device malfunction, to the extent the law permits. GPLv3 on the app and the corresponding-source requirements of components mean complete packages need careful compliance. Product names identify compatible formats only; no upstream endorsement is implied.