Collection CSV export does not match Collection count (missing and extra tracks)

Hello Engine DJ team:

I’m trying to audit my music library using Engine DJ Desktop (latest version) and I’m encountering serious inconsistencies between the Collection view and the CSV export.

What I see:

  • Collection (visible in Engine DJ): 6863 tracks
  • Export Collection → CSV: ~10,000 tracks
  • The CSV includes many tracks with paths like C:… and other drives that no longer exist.
  • All my actual music files are physically located on drive L:.

To clean up the data, I did the following:

  • I exported the Collection to CSV.
  • I removed all rows that were NOT from L:.
  • After filtering, the CSV contains 6421 tracks.

The problem:

  • The collection shows 6863 tracks.
  • The CSV filtered to the actual drive shows 6421 tracks.
  • This means that approximately 442 visible tracks in the Collection are missing from the CSV export.

I also ran Collection → Run Cleanup, but this did not resolve the issue.

Why are some visible tracks in the Collection not exporting correctly (or not exporting at all) to CSV?

Is there a supported way to obtain a reliable, 1:1 snapshot of the visible Collection?

Currently, the CSV export does not seem reliable for auditing or verification purposes.

Thank you for your time.

Sincerely.

Simply use Lexicon for this. The database synchronization feature doesn’t require a subscription. With Lexicon, you can reassign the data if the files have been moved to a different location. There are also tutorials available for this. However, I’m currently unsure whether this feature is free. It’s better to pay a small fee upfront than to end up with an incomplete collection later.

Moving & Renaming FIles - DJ Library Management

Thank you so much, I’ve already tried it. And Lexicon doesn’t allow exporting, so it’s useless to me…

Anyway, I did another test and I’m amazed at how badly it works.

In the CSV I exported from a playlist, it tells me that a song, for example, is on drive F: I look for it, and it’s actually on drive L:

And it’s not duplicated or anything, I don’t know why, but this information changed when I exported to CSV… I’m baffled.