Repository navigation
Start Here - Welcome to Polyend Tracker Community Edition (CE) #1
sandroidmusic
announced in
Announcements
Replies: 3 comments
|
Shout out to the team! Been looking forward to this!! |
0 replies
|
This is amazing, thank you Polyend! Already have some ideas |
0 replies
|
This is very awesome! Thank you! Polyend rulez! <3 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Welcome to the official GitHub Discussions space for Polyend Tracker Community Edition (CE)!
By opening up the codebase for the OG Tracker, Tracker+, and Tracker Mini, our goal is to give musicians, sound designers, and embedded developers the keys to explore, improve, and extend the Tracker platform together.
Whether you're here to grab the latest Community Edition release, share custom
.ptfxSample Editor plugins and themes, propose workflow improvements, or dive into C++ and DSP code, we're glad to have you here.A quick overview
Here is how this repository and community are organized:
Releases (Ready-to-Flash Firmware & Plugins)
.ptffirmware files (PolyendTracker_CE_*.ptf,TrackerPlus_CE_*.ptf,TrackerMini_CE_*.ptf) andPolyendTracker_CE_Effects.zipdirectly from the Releases page.CHANGELOG.mdto see everything included in the latest releases.Documentation & SDK Guides (
docs/).ptfxSample Editor Plugin SDK (editor-fx-sdk/, MIT-licensed) and the Open Synth Engine SDK (synth/include/PolySynth/sdk/) for Tracker+ and Mini.Where to Post What
.ptfxeffect, or a synth engine? Start a discussion here first so we can bounce ideas around and align before writing code..ptfxplugins, color schemes, custom fonts, synth engines, or music made with Tracker CE!MK66vsIMX), or writing DSP code.Guiding Philosophy
For the main
polyend/tracker-cerepository, we want to prioritize workflow continuity and muscle memory. Add thoughtful features, DSP additions, optimizations, and bug fixes that feel right at home on the Tracker across all three devices.Governance, Maintainers & Our Community Pledge
Right now at launch, I'm the only maintainer with permissions to review/merge Pull Requests and publish official releases. However, the goal of Tracker CE is never for this project to be controlled by a single person.
What makes its way into the Community Edition should be driven by the community, through open discussion, consensus, and real-world musical utility.
That is why GitHub Discussions is so important: it gives everyone a voice in shaping the roadmap and weighing in on proposed features.
As the community grows, I would love to bring additional maintainers on board based on active contributions, code quality, hardware testing, and alignment with the project's philosophy.
Quick Note on Hardware Safety
Experimenting with Tracker CE is very safe: the hardware bootloader on all three devices is isolated from the
.ptfapplication firmware. Even if you flash a custom build that crashes immediately on boot, pressing the hardware pinhole recovery button lets you re-flash any working.ptffrom your microSD card in seconds.(Just one golden rule if you're experimenting with low-level code: never modify the flash origin addresses in the linker scripts or the MK66
.flashconfigbytes—seeCONTRIBUTING.mdfor details.)Say Hello!
Drop a reply below to introduce yourself! Let us know which Tracker model(s) you're using, what music you make, or what you're excited to build or tweak in Tracker CE!
Cheers and i hope to talk to y'all soon,
Sandro(id)
All reactions