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, it sounds like 320 kbps. But 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 gets bigger and says 320, but the detail the 128 threw away is gone for good. You can’t un-scramble an egg.
• Streaming rips. Tracks grabbed from streaming services are typically 128–256 kbps AAC or OGG. 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 “320s” that started life as something much smaller. 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 fine for minutes, then glitches or stops dead.

On laptop speakers or earbuds, you might not notice. On a club system with proper monitoring? It’s obvious.

Why the bitrate can’t tell you

Here’s the catch: a transcode really is a 320 kbps file. The encoder spends 320 kilobits on every second of audio. It just spends them describing a sound that has already lost its highs. Your DJ software reads the bitrate and the tags, both say 320, and it has no reason to question them.

What gives a fake away is the sound itself. A low-bitrate encoder saves space by cutting off the high frequencies. A genuine 320 kbps MP3 carries sound up to about 20 kHz. A file that started life as a 128 stops at around 16 to 17 kHz, and no amount of re-encoding brings those highs back.

How DJ Scan catches it

DJ Scan decodes every track from start to finish and measures where the high frequencies actually stop. When a file says 320 but stops at 17 kHz, DJ Scan flags it as a fake 320 and tells you what it really sounds like.

While it’s listening, it checks the things that stop a track loading at all: formats your decks can’t play, damaged and cut-off downloads, long silent intros and gaps, and file names a FAT32 stick can’t store. Then it checks the stick itself, because a deck that can’t read your stick won’t play any of it.

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 saves you from a bad surprise on a big system.

A quick workflow:

1. Download new tracks to a staging folder.
2. Run DJ Scan on that folder.
3. Replace or re-source anything that gets flagged.
4. Move clean files to your main library.

It takes less than a minute for a folder of new downloads, 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 a Mac app that checks every track and stick against the decks you’re about to play. Scan your library tonight, and play Saturday knowing your files are legit.