Why You Should Scan Your Music Files Before Every Gig
You’ve spent hours curating the perfect setlist. The transitions are mapped out, the energy arc is dialled in, and you’re feeling confident about Saturday night. Then, mid-set, a track drops — and it sounds flat. Muffled highs, no presence, zero punch on the system. The crowd doesn’t know why the vibe shifted, but you do: that “320 kbps” file was lying to you.
It happens more often than you’d think.
The 320 kbps lie
Most DJs assume that if a file says 320 kbps in its metadata, it is 320 kbps. But metadata is just text — anyone (or any tool) can write whatever they want in there. Here are the most common ways you end up with fake 320s in your library:
- Transcoded files. Someone takes a 128 kbps MP3 and re-encodes it at 320 kbps. The file size goes up, the metadata says 320, but the actual audio content never exceeds 128 kbps worth of data. You can’t un-scramble an egg.
- Streaming rips. Tracks grabbed from streaming services are typically 128–256 kbps AAC or OGG. When converted to MP3 at 320 kbps, the result is a bloated file with no more detail than the source stream.
- Mislabelled downloads. Blogs, forums, and file-sharing sites are full of MP3s tagged as 320 that were never encoded at that bitrate. Sometimes it’s intentional; sometimes it’s just sloppy.
- Corrupt or partial downloads. A download that didn’t finish cleanly can produce a file that plays but has sections of degraded or missing audio data.
On laptop speakers or earbuds, you might not notice. On a club system with proper monitoring? It’s obvious.
Why metadata isn’t enough
DJ software reads ID3 tags and file headers. If the header says 320 kbps CBR, your software will report exactly that. It has no reason to question it — it’s just reading what it’s told.
The only way to know the actual encoding quality is to inspect the audio stream itself. That’s what FFprobe does. It analyses the bitstream frame by frame and reports the real bitrate based on the actual encoded data, not what some tag claims.
How DJ Scan works
DJ Scan wraps FFprobe in a simple desktop interface. Point it at a folder — your USB stick, your download folder, your entire library — and it recursively finds every MP3. Each file gets analysed against the audio stream, not the metadata.
A file passes only if the detected bitrate falls within 318–322 kbps. Anything outside that window gets flagged with the exact bitrate and reason. No guesswork, no waveform analysis — just what the encoder actually produced.
Make it part of your prep
The best time to scan is right after you download new tracks and before you load them onto your performance drive. Think of it like checking your headphones or testing your cables — basic due diligence that takes seconds and saves you from a bad surprise on a big system.
A quick workflow:
- Download new tracks to a staging folder.
- Run DJ Scan on that folder.
- Replace or re-source anything that gets flagged.
- Move clean files to your main library.
It takes less than a minute for most folders and gives you confidence that every file on your drive is what it claims to be.
Don’t let a fake 320 ruin your set
Your track selection and mixing are only as good as the source files you’re working with. A mislabelled transcode on a festival system isn’t just embarrassing — it breaks the energy you’ve worked to build.
DJ Scan is free, open source, and built specifically for this. Download it, scan your library, and play every gig knowing your files are legit.