Polyend open-sources Tracker firmware, releases Community Edition 1.0
Music hardware maker releases source code for three Tracker models, inviting users to modify and build on the platform.
What to know
- Polyend open-sourced firmware for three Tracker models and released Community Edition 1.0, enabling users to modify hardware and share custom builds.
- The move includes a safety recovery system preventing bricked devices and new features like wavetable envelopes, faster performance, and custom theming.
- Community response emphasizes this as industry-leading openness in music hardware, with questions about whether it signals end-of-life or a model to drive future demand.
The dispute Whether open-sourcing the Tracker firmware signals end-of-life for the hardware line or a strategy to sustain long-term demand and community engagement. · positions read across 24 posts and comments
This is exemplary open-source hardware practice that other manufacturers should emulate.
-
“if this is the EOL treatment for the Tracker, this is what other companies should strive for too.”
jussi · Lobsters ↗
Open-sourcing may stimulate new demand and community development rather than signal product end-of-life.
-
“Conversely, perhaps the updated firmware, engines, and the open-sourcing stimulates new / more demand.”
jussi · Lobsters ↗
Modular firmware installation would improve usability for community customization.
-
“I'm now thinking about how people will choose features from the different firmwares the community builds.”
jussi · Lobsters ↗
Piotr Raczyński CEO of PolyendPolyend Music hardware manufacturer
How it unfolded 1 development · click the chart to see its coverage articlesposts
-
1
Tracker Community Edition 1.0 includes wavetable envelopes, faster performance, custom theming
The new Community Edition adds wavetable envelopes and LFOs, faster project loading and saving, tighter MIDI clock timing, and browser-based custom theme and font design capabilities.
“We've seen it firsthand in the unofficial Tracker mods you've built, and we're sharing the firmware source code to support that work.”
— Piotr Raczyński, CEO of Polyend · source -
Oh wow, I had a feeling they may do this. There has been a lot of vibe-reverse-engineering done for this firmware over the past few weeks. I think this is the right call for a device that has fallen to the bottom of the Polyend catalogue. I love my Tracker but it definitely felt like Polyend was not going to support it for much longer (especially…
2 more of the top 3 · 24 posts in this stretch
-
Two days ago I (that is, AI) started to mod my modal electronics Cobalt8 after trying the model:cycles mods.Half a day of setup and i had my first curtis-style filter on the synth. 2 days of low intensity prompting and I have- 3 Filters: Curtis, 303, Steiner Parker- An additional noise source- The oscillators from braids- Prophet08-ish oscillators…
-
note that the firmware release also applies to the plus and the mini (which i suppose they couldn't have really "protected" if they did release only the og tracker firmware, given you can compare the binaries in a decompilation tool) the real question is if the play/play+ firmware comes out and if not how easy it might be to reverse that…
-
-
background
Polyend releases Tracker firmware source code and Community Edition 1.0 — Polyend published the firmware source code for the original Tracker, Tracker+, and Tracker Mini on GitHub, along with Tracker Community Edition 1.0. The release enables users to modify firmware, build custom versions, and share modifications with a safety recovery system to prevent bricking.
What people are saying 21 voices from 2 sites · best of 24 · verbatim
- Nov 3
-
Responding to myself with a correction:I made an apparently common mistake:My mistake: MWAVE or M-WAVEReal name: M-VAVE FM-1The latter will get you more stock listings on Ali and elsewhere. There cannot be a better stocking stuffer for anyone who is synth-curious.
-
As you mention, the FM-1 blew up thanks to the plethora of different firmware options that suddenly appeared, and it’s interesting that Behringer just announced new units (Kick and Ignite) with open firmware too.This new paradigm makes me happy.
-
Oh yeah I noticed the firmware applied to all three models - its just over the past year+ the OG Tracker wasn't getting much love. I understand its an underpowered machine (and not the one Polyend _wanted_ to make in the first place) but it still has a permanent home on my desk next to my synths. They have a handful of great hardware now that…
-
It looks like we are in the knee of the curve for open source firmware for music gear.
-
For a good list of firmware open and less so, see https://github.com/Lapin/awesome-music-gear-firmware - came across it earlier today when looking for something unrelated.
-
Widespread LLM reverse engineering basically forcing the hand of many hardware instrument makers.
-
It's more likely because LLM usage and particularly REA (Reverse Engineer Anything) is opening up those firmwares whether the vendor likes it or not.The best strategy for a HW-vendor at this point is to get ahead of it and open-source the firmware under your own License Agreement, so you can possibly also integrate community work back into your…
- Nov 2
-
Modwiggler is filling with reverse engineering mods, I think it is super smart to get out in front of that. Modding is nothing new and open source music firmware à la Mutable Instruments is a great example to learn from. Good move Polyend!
-
Very smart move. Open-source your project. Get more nerds invested in your gear and its legacy, and crowd-source feature development.Well done, Polyend! Godspeed, and looking forward to seeing how this develops.
-
Yes. Custom firmware for audio gear has been A Thing for a long time, as far back as the 1990s. I worked on a company that offered a general DSP platform back in 2003, but it didn't take off because it was too difficult for most people to program. JJOS became very popular among users of Akai's MPC line (of whom there are very many) in the…
-
That, plus the fact people were already poking into the closed firmware binary, plus the existence of an alternative firmware. By doing this, Polyend also kind of passes the responsibility of maintaining the Tracker devices to the community.It's also worth mentioning that the release is not just a source code release, they added a lot of great…
-
That’s cool. After M-vave's FM1 and TE's OP-1 revolution, going this path is almost mandatory for anyone with good hardware but a crappy interface. I'd love to love Polyend's software, but M8 is so far ahead in terms of power and intuitiveness.
-
This has to be related to MWAVE's FM-1 viral popularity, largely due to open firmware right?https://arstechnica.com/gadgets/2026/10/from-impulse-purchas...https://github.com/aroum/fm1-custom-fwsee also:> Reverse Engineering of the M-VAVE FM-1 Pocket Synthesizer Firmwarehttps://news.ycombinator.com/item?id=49994065 (75 points - 50 comments)
-
Looks like my Tracker is getting promoted from drawer jockey to the main jamspot in my music setup, and I've got a weekend project to take on.I love to see this new trend in the electrical musical implement industrial complex.
-
Relatedly, Erika Synths released the source code of the LXR-02 very recently as well: https://www.ericasynths.lv/news/post/lxropen(I/AI had fun porting it to wasm/web! I don't want to seem too self-link'y, so if anyone asks, happy to share the link)I also have a Polyend Tracker for sale if anyone's in the market..! It's a great device, I'm just…
-
For people afraid of bricking their units, I can't stress enough how groundbreaking it is that they're acknowledging that risk and still offering to repair your unit. You pay of course, because this is a risk you took, but at least they will have a look at it: "Out-of-Warranty Repairs Available: In the unlikely event that something ever goes wrong…
-
The avalanche of reverse engineered/custom firmwares is definitely changing the synth landscape. I'm wondering how many other companies will start open sourcing. It isn't always trivial since sometimes there's proprietary software components or toolchains that can't be open sourced. But it's hard to imagine it won't be more common. There's a lot…
-
Oh nice, I didn't realize the LXR-02 firmware was open-sourced as well. [It looks like there is a lot of new, open music tools coming right now](https://cdm.link/sndstation-linux-distro-for-game-handhelds/). I really like it but I have a suspicion we are going to be inundated with devices and software over the next year. The true test, of course…
-
Erica Synths also released the LXR-02 firmware (https://www.ericasynths.lv/news/post/lxropenmod/) quoting explicitly the vibe-RE/hacking ongoing. I would bu curious if there would be some sort of community led movement like for Deluge. Or we may more see some firmware à la carte like https://modwerk.app. It is an interesting time.
-
[They do provide the API for these blobs](https://github.com/polyend/tracker-ce/tree/main/synth/include/PolySynth). Is that what you're asking about? I would assume with something like this we can take a synth engine from something like [Surge](https://surge-synthesizer.github.io/) and then wrap it up with these APIs to have it run inside Tracker…
-
Really interesting to see this happening across the music tech landscape. Wonder what [this](https://github.com/polyend/tracker-ce/blob/main/synth/lib/) means for what you can do with the synth engine, and which parts they're not opening? "Binary blobs for `libPolySynth.a` and `libPolyDSP.a` with a `LICENSE-PROPRIETARY.txt`. Maybe they provide…