Why I'm building Metamix

Every DJ I know who plays more than a few hundred tracks has the same quiet problem: the library outgrew the workflow. Finding the track you know you have means scrolling, guessing, or begging the search bar. Preparing an import means hours of manual analysis, tagging, and cue placement that all evaporate the moment you forget which tracks you already did.

Metamix started as a tool for exactly that problem. The idea is simple: your archive should work like a streaming service — searchable, browsable by vibe, instantly connected to your performance library — and the tedious parts (analysis, tags, cue points) should be automated carefully, not done by hand.

Two principles shape everything I'm building:

• Local-first. Your music never leaves your Mac. Analysis runs on Apple's native frameworks, tagging runs on local models, and there is no cloud, no account, and no phone-home. The app works offline, full stop.
• Rekordbox is sacred. Metamix never guesses about timing — it builds on the beatgrid Rekordbox already trusts. It never overwrites edits you made by hand. Every write is planned as a diff, audited, and reversible.

If that sounds like the version of your library you always wanted, join the waitlist. I'm sharing the build openly as it happens — what works, what doesn't, and why.