A 2012 budget guitar pedal is now a full amp modeler. A $70 Temu synth has dozens of alternate firmwares. And Elektron, the darling of the synth world, is banning links to community firmware files. Inside the vibe-coded firmware rebellion over who decides what your hardware can do.
Something strange is happening to music gear. A developer got tired of waiting — and started building vibe-coded firmware.
His handle is 18nelli. He owned an Elektron Model:Cycles — a beloved little groovebox, the entry point into Elektron’s premium universe — and he was frustrated. The machine had received no official firmware update since May 2021. Five years of silence from the manufacturer while the hardware sat there, perfectly capable, frozen in time. His read on the stasis: the device felt “designed just to push us to buy their more expensive gear.” That is his stated interpretation, and no one should mistake it for a confirmed fact — no manufacturer has addressed the motive. But the frustration was real, and it did what frustration has always done: it made someone build.
The vibe-coded firmware hack that grew legs
18nelli’s project, Modded Cycles, began with a single goal: six-track audio over USB. Built with the help of Claude, it grew through community contributions into something far stranger — a custom firmware layer that pushes the little groovebox well past what its official software allows.
That DIY instinct is now the pattern of an entire underground: owners of synths, samplers and grooveboxes who decided that once they’ve bought the hardware, the software ceiling is negotiable.
When adding one feature used to take a season
To understand how fast this moved, you need the before picture. In the pre-LLM era, custom firmware for synths was exceedingly rare, the province of deep experts willing to spend weeks or months. Adding a simple feature — say, velocity sensitivity to a Korg Volca — could consume a season of evenings. Now, as The Verge reported, hobbyists turn cheap synths into full grooveboxes in days.
The receipts are everywhere. The M-Vave FM-1 is a roughly $70 Yamaha DX-7 clone sold on Temu. It now hosts dozens of custom firmwares — Felucca, SLOOP, X0X — several of which list Claude as a contributor on GitHub, adding synth engines, multi-track sequencing and alternate user interfaces.
And then there’s the 2012 Zoom MS-70CDR, a budget multi-effects pedal. Roman Rusinov, a Redditor who releases as Farlow, used AI-assisted development and built on the ZDL reverse-engineering project to load NAM A2 Lite amp captures and custom impulse responses onto the pedal — a full-fledged amp modeler where a chorus pedal used to be. “If you own the hardware, you should be able to do whatever you want with it,” he told The Verge.
Two manufacturers, two religions
Here is where the affair begins — because the manufacturers noticed, and they split.
Elektron, for its part, has banned links to community firmware files.
M-Vave took the opposite path: the company backs the community effort. Where Elektron polices distribution, the budget maker lets the ecosystem bloom.
This is the conflict at the heart of the story: the fight is over who controls the firmware of the thing you own — between the manufacturers who set the software ceiling and the hobbyists rewriting it.
The case for the ban, steelmanned
It would be dishonest to tell this story as heroes versus villains, so let’s give the ban its strongest case. Custom firmware can brick devices. It can void warranties, and the support costs it generates may land on the manufacturer, not the hobbyist who shipped the code — the company that sold the hardware remains the brand blamed when a vibe-coded flash fails mid-gig. Policing distribution is defensible stewardship, not necessarily control.
There’s a second, quieter defense. Nobody is entitled to perpetual updates: the argument runs that the Model:Cycles worked as sold, and tiering features across price points is ordinary product strategy, not sabotage. The community firmware boom may simply prove that AI lets a few skilled hobbyists do free R&D that manufacturers rationally declined to fund for a niche audience. And the downside of AI-accelerated development is documented in the scene itself: frequent updates can leave bugs and unfinished code behind, and the risk of bricking a unit is real.
All of that can be true at once. And still: the machine on your desk was capable of this all along.
Who maintains the fork in two years?
There is a harder question hiding behind the excitement: what happens to a vibe-coded firmware fork two years on? The reporting gathered here does not say — nothing in it describes how these forks are maintained, who takes over if the original builder moves on, or what happens when the novelty fades. Those are open questions, not settled facts, and the honest answers run in both directions. A fork could find a successor and thrive, the way community projects sometimes do; or it could stall, with bugs left unpatched and a working machine slowly becoming one fewer people understand. Either future is conceivable. Neither is established. That is not an argument for the ban. It is the uncertainty the whole rebellion is built on: the hardware was never the limit, but the evidence does not yet show whether the community is a durable replacement for the manufacturer.
Withheld, or never built?
Which brings us to the one question the evidence can’t answer — were these features deliberately withheld, or simply never built?
18nelli has his interpretation: the static firmware felt engineered to push buyers up the product line. It’s a serious charge from a serious builder, and it’s exactly one data point. No manufacturer has confirmed or denied any of it. The honest version of this story keeps the question open, the way the best detective stories do: the evidence proves the hardware was never the limit. It does not prove why the limit was there.
But here’s what the evidence does prove, and it’s the takeaway worth carrying out of the synth world into everything else you own: on these devices, the bottleneck was the firmware rather than the hardware. Cheap and aging machines proved capable of far more than their official software allowed, the moment hobbyists could rewrite that software with AI help. One manufacturer banned the links; another backed the builders. The rest is up to whoever holds the flasher.
