Project ideas from Hacker News discussions.

Fasttracker II clone in C using SDL 2

📝 Discussion Summary (Click to expand)

1️⃣ Tracker revival & nostalgia
The community is buzzing about bringing back classic trackers.

“The world could use more trackers. I’m really hoping the upcoming Ableton Live extension API will allow for direct access to the piano roll.” – Anonymous
“Renoise Redux is already shipping a feature‑complete tracker you can easily run in Ableton or Bitwig.” – Teknomadix
“Schism Tracker as well: https://github.com/schismtracker/schismtracker/” – rzzzt

2️⃣ SDL2 vs. SDL3 discussion
Many wonder why the project still uses SDL2.

“SDL3 has been around for 1.5 years. I can’t help but wonder about the choice of SDL2 over it. … If you value running on those deprecated platforms and/or you don’t need any of the features introduced since SDL3, it’s quite reasonable to stick with SDL2.” – RodgerTheGreat
“I don’t have an extremely high opinion of sdl2‑compat specifically because my SDL2‑based projects have had several bizarre bug reports which originated in downstream packages presuming they could use this ‘compatibility layer’ instead of the actual dependency I develop and test against.” – RodgerTheGreat

3️⃣ Historical sound‑hardware & tracker origins
The conversation drifts into the hardware constraints that shaped early trackers.

“Um, no. Let’s set the record straight… Ensoniq was just the volume tier of Creative’s own lineup.” – Teknomadix
“As someone who was in the demoscene: FastTracker II was more of a successor to ProTracker on the Amiga than it was a successor to ScreamTracker 3.” – Benanov
“Tell us about the great Sound Blaster shortage! I thought they threw one after you each time you left a PC parts shop.” – rzzzt

These three themes capture the resurgence of classic trackers, the technical rationale for staying on SDL2, and the retro‑hardware context that inspired the original tools.


🚀 Project Ideas

TrackerHub — A Unified Web Platform for Legacy Tracker Modules

Summary

  • A searchable, community‑driven repository that hosts, previews, and converts classic tracker files (XM, MOD, IT, MO3, etc.) with modern metadata.
  • Preserves original instrument/sample data while offering lossless re‑export to contemporary formats (WAV, FLAC, MIDI).

Details

Key Value
Target Audience Retro‑scene musicians, chiptune producers, indie game devs, music historians
Core Feature Module library with drag‑and‑drop import, batch conversion, and direct VST/AU export
Tech Stack React front‑end, Node.js API, SQLite/IndexedDB storage, FFmpeg for audio conversion, Docker deployment
Difficulty Medium
Monetization Revenue-ready: Subscription tier ($5/mo) for premium storage & analytics

Notes

  • HN commenters repeatedly expressed nostalgia for FT2/Schism Tracker modules and asked for ways to share and archive them; a central hub would satisfy that need.
  • Integrating a VST export feature directly answers toaster comments about “FT2 clone as a VST plugin” and the desire to use trackers inside modern DAWs.
  • Open‑source core with optional paid plans encourages community contribution while providing sustainable funding.

SDL3 Tracker Engine — Modern Open‑Source Tracker with VST Export

Summary

  • A cross‑platform tracker built on SDL3 that faithfully replicates the ProTracker/FT2 workflow while exposing a plugin API for VST/AU instruments.
  • Allows users to edit modules on any OS and drop exported instrument plugins directly into Ableton, Bitwig, or FL Studio.

Details

Key Value
Target Audience Tracker enthusiasts, chip‑tune artists, game audio developers
Core Feature Real‑time pattern editor, SDL3‑backed audio mixing, one‑click VST/AU instrument generation
Tech Stack Rust core, SDL3, Rust‑FFI bindings, JUCE for VST plugin generation, CI/CD with GitHub Actions
Difficulty Medium
Monetization Revenue-ready: Commercial license for enterprise use + optional $15 “Pro” tier

Notes

  • Commenters asked “Would you be working on a port of rtmidi in pure C?” and about SDL‑3 compatibility; this project directly answers both.
  • The nostalgia factor (“This rocks. Such nostalgia.”) translates into strong early adoption if the UI mirrors classic trackers.
  • VST export satisfies toaster’s observation that “Someone also released an extension … as a VST plugin” but provides an open, community‑maintained alternative.

Tracker Shortcut Bridge — Browser Extension & Desktop App to Map Legacy Tracker Keys

Summary

  • A lightweight desktop application (Electron) and browser extension that translates ProTracker/FT2 keyboard shortcuts into native hotkeys of popular modern music software (Ableton Live, Bitwig Studio, Reaper, etc.).
  • Enables users who learned tracking in the 90s to retain muscle memory while working in contemporary DAWs.

Details

Key Value
Target Audience Former tracker users, retro‑music educators, hobbyist musicians transitioning to modern DAWs
Core Feature Real‑time mapping layer that intercepts key presses and forwards them as MIDI CC or DAW shortcuts
Tech Stack Electron (Node.js + Chromium), Electron‑Bridge API, Configuration UI, Cross‑platform installer (Windows/macOS/Linux)
Difficulty Low
Monetization Revenue-ready: One‑time purchase ($12) for premium mapping packs

Notes

  • Numerous comments lamented lost “muscle memory for ProTracker (or FastTracker 2) keyboard shortcuts” and wanted direct integration with modern tools.
  • Providing a simple solution to bridge that gap directly addresses the sentiment “Such nostalgia.” and the desire for a “ProTracker clone for Ableton”.
  • Low development effort combined with high perceived value makes this a quick win for community goodwill and potential viral adoption on Hacker News.

Read Later