Hi all,
My name is Ben and I've spent about the last year building a DJ library manager called Vibes. I'm a DJ from Cologne, UX designer and developer by trade, and I use it for my own sets.
You tag your tracks by vibe, energy and mood, build sets visually on a canvas, and export that structure back into Traktor. It does Rekordbox, Serato and Engine DJ as well, on macOS and Windows.
On the Traktor side it reads your collection.nml directly, so your playlists come in intact and you can map any of them to a vibe during import. That read is strictly read-only, nothing in your collection changes. Export writes a separate NML playlist tree that you bring in yourself, with star ratings mapped to Traktor ratings and your vibe tags written into the comment field. One thing worth knowing upfront: Smartlists cannot be created from outside Traktor, so what arrives are regular playlists. The workaround I use is building Smartlist rules on top of those comments, for example comment contains Peak Time and BPM above 128.
Every track is keyed in Camelot inside Vibes, which Traktor does not display natively, so harmonic prep happens on the wheel instead of converting Open Key in your head.
I launched it two weeks ago at 1.0 and it's on 1.2.9 now. Almost every one of those updates came from someone writing in, things like analysis crashes on Apple Silicon, imports that skipped tracks, and export bugs across all four apps. It should run stable now, but if it doesn't on your setup I'd like to hear about it. That's how the last two weeks went and I don't plan on stopping.
There's a 14 day trial and you don't need an account. It's 49 dollars one time, no subscription.
Everything else is at vibesdj.io.
What I'd really like to know: what's your biggest library pain in Traktor? Is it the collection getting messy over time, prep before a gig, or getting tags to survive between apps? That's what shapes what I build next.
Happy to answer anything in here.
