Polyend Tracker family now open-source and community update with major new features

SYNTH ANATOMY uses affiliation & partner programs (big red buttons) to finance a part of the activity. If you use these, you support the website. Thanks!    Reading Time: 3 minutes

Polyend has announced that its entire Tracker family (OG, + and Mini) is going open source, and they released a community update 1.0 with major new features.

AI has turned the music-tech market upside down, making once-unimaginable possibilities real. The most prominent topic is custom firmware updates for hardware. Behringer has decided to make its products open-source. A day later, Akai—practically forced to do so after Behringer announced an open MPC clone—followed suit.

Next up is another well-known company. The Polish developers at Polyend have made their Tracker family open-source and also released a major community update.

Polyend Tracker Open Source

Polyend Tracker Open-Source

The headline makes it clear: Polyend has made its Tracker open-source—not just the original Tracker, but also the Tracker+ and the Mini. They have published the firmware source code for all three devices on GitHub.

This means you can now add new features to the firmware or even build entirely new instruments from it. However, many are still afraid to flash these custom operating systems because they might brick the bootloader.

The Polyend developers have thought ahead and implemented a recovery system that helps prevent a faulty build from permanently disabling the instrument. This is an addition many of the new companies going open-source should also incorporate. 

“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,” said Piotr Raczyński, CEO of Polyend.

“Maybe you want to build an entirely new instrument on the Tracker hardware. Or maybe there’s just one thing you wish your Tracker did differently. Either way, you can now try it on the unit you already own. I bet some of you already have ideas for the original Tracker that never crossed our minds.”

Polyend Tracker open-source

Tracker Community Edition 1.0

Alongside the official open-source firmwares, you can also find the new Polyend Tracker Community Edition 1.0 firmware on GitHub. This all-new official update brings new features to all three standalone sampling workstations.

All three models can now stream long stems, loops, and field recordings from a microSD card, keeping only the start of each streamed sample in sample memory.

New dedicated micro-move and volume fields capture the timing and velocity of each hit while leaving both step FX slots free. New chance conditions can bring in a snare fill every fourth pass.

It also introduces six new sample editor plugins, from an analog-style kick generator to a stereo delay. Better: a new development kit lets users build, share and sell their own effects and generators.

Tracker+ and Tracker Mini also gain two synth engines, CHIP and DIRT, and a separate development kit for creating new engines

Other additions across the range include wavetable envelopes and LFOs, faster project loading and saving, tighter MIDI clock timing, and a browser editor for custom themes and fonts

First Impression

A very welcome move that shows the music tech market is currently undergoing a major shift. I’m curious to see which other companies will follow suit.

Polyend Tracker family is now open-source, and you can find the code on GitHub.

More information here: Polyend

Hardware Sampler News

Hardware Groovebox News

13 Comments

  1. The recovery system is a very nice addition. I don’t know if I’ll do this to my Mini because I’m not obsessed with this whole customer firmware thing, but a recovery system makes it more appealing because everything is reversible.

  2. thanks for releasing the source code! I gave it to ChatGPT and explained the one feature I’ve wanted for ages – a temp audition loop. In Sample Playback, pressing Preview once now loops the sample between its Start and End points. No need to hold preview down: adjust the points while listening, and press it again to stop. I like to work with big loops so i’m going to add Preview end next: play from shortly before the End point, then loop back to Start.

    • Please, I’m more of a Puredata guy than a coder, and all of these custom firmware are very intriguing but very mysterious to figure out HOW to actually create one, and make it functional without being a coder… Event Chat GPT didn’t really manage to explain the process…

      Can you elaborate on the steps needed to generate custom firmware, please?

      I bet I’m not the only one to get stuck at this step without being a beginner in DSP music though… Thank you very much!

      • if you have a chatgpt subscription, you need to switch it to codex (it’s a dropdown at the top where it says chatgpt). tell the regular chat what you want and it will give you prompts for codex. it’s a multistep process of trial and error, pasting error codes and summary files from codex back to chatgpt, and then pasting further prompts from chatgpt to codex. it helps to have a software emulator that emulates the processor and computing power of the hardware unit so you can test your firmware versions without bricking your machine. and get ready for your weekly codex usage to dwindle after a day or 2.

        • Thanks!
          That’s already a bit clearer!
          But it’s still a bit vague—for instance, do you need a paid subscription to ChatGPT/Claude, or can you get by with a free version, even if it takes longer?
          What tools should be used to create these specific virtual machines?
          How do you debug software if it’s running on a virtual machine rather than on the actual hardware with real-world controls?
          How long does the process actually take?
          I’m used to programming and debugging DSP effects over the course of weeks, but I have no idea what the real-time requirements might be here…
          It would be incredibly helpful to see a full, end-to-end walkthrough—from the initial firmware concept and the base prompt to code testing, debugging, and finally the completed firmware being transferred—presented as a video that includes the time taken, so I can truly grasp the entire process, the duration, and the tools involved.
          This is precisely what’s currently missing to make these alternative firmwares more “mainstream usefull” and to break out of the classic “developer’s codes > to users” loop—a cycle that has yielded the same results for 30 years: plenty of cool new features added over the years, yet an interface and ergonomy that remains far too disconnected from the realities of a musician’s needs.

      • i downloaded the zip file from Github and dropped it into Chatgpt. it then tested we could make a firmware file from the stuff we downloaded by compiling it in a free program called MSYS2 UCRT64. its like a command terminal but GPT will give u the instructions to put in. when the compile was successful that proved everything would work. final step was to give GPT my improvement and it produced a new file for the compiler. i made a new folder on my SD card called firmware and dropped the new firmware in there. it worked first time. ChatGpt can guide u every step of the way its very easy. if it did crash your tracker u can do a hard reset apparently to get old settings back.

  3. Akai didn’t say MPC Sample is open source. They said they are embracing the vibe coding community, that’s not the same thing. the code can still be closed source and you need to be invited to join the developer community. I see so many articles and social media commentators misrepresentating the information.

  4. UPDATE: Just a heads-up for anyone who might be in the same situation as me:
    I just asked ChatGPT again to explain the process and how to put it into practice. Previously, I had been accessing ChatGPT through DuckDuckGo’s AI, but this time I asked directly on the ChatGPT website—and the response was completely different! It was able to explain everything with perfect clarity and guide me through the process. In contrast, the version accessed via DuckDuckGo’s AI basically kept telling me that it required coding, that it was difficult, and that it would take a long time—in short, it was clearly trying to discourage the user from carrying out the project…

    Anyway, be wary of the AI ​​platform you use; the exact same model can behave in completely different ways depending on the interface you use to communicate with it!

  5. Why not use AI to create some of your pure data code as a starting point? Then you could see what it was doing and also not have to jump through hardware hoops at first.

    • This is the core of my project: I currently have a functional setup with a tracker connected—via a USB audio—to Pure Data on a PC, where I apply various DSP processes to specific tracks.
      My idea is to convert all my Pure Data DSP processes into C++ with the help of an LLM, and then integrate them into the tracker. Since I’m not a developer, it was very difficult for me to figure out how to go about this; but now that I’m using the actual ChatGPT—rather than the stripped-down version offered by DuckDuckGo—I’ve finally gotten all the answers I needed!

    • Indeed, “open-source firmware” does not mean “entirely open-source software”; in general, there is some confusion regarding this.

Leave a Reply

Your email address will not be published.


*