Local DJ library companion. Select the directory that contains _Serato_ to reuse Serato's on-disk crate layout, then play tracks from your local music library on disk.

cd dj
npm install
npm run browser   # web (Vite)
npm run desktop   # Tauri desktop shell

When you choose Open library, select the folder that contains your _Serato_ folder (for example Music or a drive root), not the _Serato_ folder itself.

Your audio files must live somewhere under that same folder, because the app resolves each track using Serato's stored path and, if that fails, by searching for the filename under the folder you granted.

Keep one copy of each track filename inside that tree. If there are multiple files with the same name, the filename lookup can't reliably decide which one to play.

Hot cues are read only from MP3 ID3 GEOB frames (Serato Markers2, Serato Markers_). Serato's library and crate files only tell this app which file to open; they do not supply hot-cue positions here. You get no cue strip when those GEOB payloads are missing on that file, which is common after moves or duplicates: the stored path may not exist under the folder you granted, a same-name fallback may open an untagged copy, or Serato may still show cues that were never written into the MP3 you are actually streaming.

This app reads the on-disk library database and crate track lists that live next to your library. Implementing that without guesswork leaned heavily on Jan Holthuis (@Holzhaus): serato-tags documents those binary layouts and related file metadata. In the browser (and anywhere else that uses packages/core), database V2 and Subcrates/*.crate are parsed in TypeScript, following the same structures as triseratops. The Tauri desktop build also calls the triseratops Rust crate directly for filesystem scans and embedded MP3 cue decoding (apps/desktop/src-tauri).