Hey everyone,
I’ve been building a tool to automate the annoying admin work between downloading tracks and importing them into Rekordbox.
I got tired of:
- fixing filenames
- correcting inconsistent/missing ID3 tags
- manually looking up metadata
- adding artwork/BPM/genre/release dates
- sorting files into folders
- discovering “320kbps” files that were clearly transcoded/upscaled
Especially for tracks coming from pools, promos, edits, Bandcamp downloads and other less-standardised sources.
The workflow for many DJs seems to be something like:
download → rename → Mp3tag → metadata lookup → copy/paste tags → move files → import into RB
So what my tool does:
- monitors an inbox folder
- identifies tracks via Beatport
- writes proper metadata automatically
- renames/organises files based on your preferences
- detects likely fake-320/transcoded files using spectral analysis
- more checks/features to come
Depending on your feedback I’ll probably add more sources for the metadata, audio quality checks and other features too
Tech stack is mainly Python + Beatport v4 API + FFT-based audio analysis.
Before pushing this further, I’m trying to better understand how other DJs handle library management and metadata cleanup today.
So I made a short survey (~5 min):
(Beta invites are at the end of the survey.)
But also genuinely curious about the workflows here:
- Do you clean/fix ID3 tags? If yes: manually, Mp3tag, OneTagger, custom scripts, something else?
- Do you standardise filenames/folder structure?
- Do you verify audio quality? Spectral check, Spek/Fakin’ The Funk, critical listening, something else?
- What’s the most annoying/friction-heavy part between download and Rekordbox import?