Playcount restores the play counts your tracks lose when a file’s path changes — keeping your VirtualDJ search results reflecting how you actually use your library, not just which files happen to have an intact path.

Why it matters #

VirtualDJ ranks search results partly by play count. When a file moves, gets renamed, or changes drive, a database repair reconnects it — but the play history tied to the old path doesn’t automatically carry over to the new one. Left alone, your most-played tracks can quietly slip down your search results, even though nothing about the track itself has changed.

When to use it #

After a database repair, once paths are reconnected and validated. It’s a good habit to run whenever you’ve been through a repair session involving moved or renamed files.

What it does #

It reconciles play counts across old and new paths for the same track, so the count reflects your real listening/playing history rather than resetting to zero just because the file reference changed.

Safety notes #

As with any change, a backup beforehand means you can always step back to the previous state if something doesn’t look right.

Common scenario #

You’ve just finished a database repair after a drive change. The library looks healthy again, but a track you play at every gig has dropped out of your top results — because its play count reset when the path changed. Playcount reconciles that back.

Related pages #

• Database Repair
• CrossRef