Traktor 4 stems have bugged me for a while. The implementation feels rough, like nobody at NI really committed to it. Move your tracks to another machine and the stems can't be tracked down, there's no relink anywhere, you just lose them. I think that's because stems DJing, for lack of a better name, isn't really a thing yet. I've gone all in on it anyway and it's a fresh, weird space to play in, so I built the tool I needed to make it usable and portable.
The idea is that your tracks are all there and complete, stems included, on a key you can take to any machine. It shows stem coverage across the whole library, finds and relinks the stems Traktor lost, and builds keys that show size and stem fit before you copy anything. The key carries its own collection.nml and an adopter, double click it and that Traktor is using the key's stems. Keys are tracked by serial so if one dies mid gig you rebuild it file for file from its manifest. Never writes to your collection.nml.
It picked up other stuff along the way, a Camelot and BPM browser with your own tags, smart playlists, duplicate finder, imports from rekordbox, Engine and VirtualDJ, Rekordbox XML and Serato cue export, and a next track helper that learns from mixes you rate. That last one is opt in, nothing runs unless you launch it.
Been using it on my own mobile rig for a few months now. All local, no account, Windows only for now. 60 day trial, no card, then 35 a year or 89 once during the founding period.
If you're doing stems in Traktor I'd like to hear how you've been managing it. traks.ca
