Export scans a repair target for anything that isn’t where it should be, and lists every broken row in the workbook, ready to fix.
When to use it #
Always the first stage of any repair — nothing gets fixed until it’s been exported first.
What it does #
It reads through the target’s data, checks whether each file path still resolves, and writes anything broken into its own row in the workbook with a status of Not Found.
Run it again later on the same repair and it replaces whatever’s currently in that worksheet — so don’t re-export over rows you’ve fixed but haven’t validated and imported yet. If CrossRef hasn’t yet copied your imported database fixes into folders, playlists or history, VDJTools warns you before it replaces the Database worksheet.
Key arguments #
/repair:<target>/stage:export
Example command #
vdjtools /repair:database /stage:exportExample output #
Virtual DJ Tools (vBeta)
Copyright© 2024-2026 Quick Apps UK. All rights reserved
Build: 1.0.38.0
repair: database
stage: export
Database loaded: 11 songs from C:UsersDJOneDriveVirtualDJdatabase.xml
Database loaded: 1 songs from D:VirtualDJdatabase.xml
Database loaded: 33755 songs from E:VirtualDJdatabase.xml
Database loaded: 3133 songs from F:VirtualDJdatabase.xml
Database loaded: 0 songs from H:VirtualDJdatabase.xml
--- Database Scan ---
[Scan] Database: databases=5, scanned=36900, issues=0
Items scanned: 36900 | Missing: 1257 | Sources: databases=5
Database scan completed
Exporting databases to Excel...
Export complete: 1257 songs exported, 17490 skipped (no play history or cue points)Safety notes #
Export is read-only — it doesn’t change anything in VirtualDJ. The only thing to watch is re-running it: it replaces the whole worksheet for that repair, so any unvalidated fixes sitting in there get overwritten.
Common scenario #
A drive change leaves hundreds of tracks unresolved. Export gathers every one of them into a single worksheet, rather than you tracking each one down by hand.
