Validate is the checkpoint between editing the workbook and actually writing changes back to VirtualDJ.
When to use it #
After you’ve reviewed and fixed whatever Autofix or CrossRef didn’t catch, and before you import.
What it does #
It checks that the file named in the New File Path column actually exists. That’s all — it doesn’t check whether it’s the right file, only that something’s there. If the file is there, the row becomes Validated, ready to import. If it isn’t, the row goes back to Not Found with your path kept, and validate lists it so you can fix it.
Which rows it checks #
Autofix, CrossRef and Match rows, and Not Found rows where you’ve typed a New File Path. It leaves Possible, Mismatch, Keep, Delete, Validated and Imported rows alone. A Possible row needs you to set it to Match first.
That distinction matters: if the file exists but the wrong one’s been matched, validate will happily pass it — and that’s what gets written to VirtualDJ on import. A quick visual check of the New File Path column before validating is worth the minute it takes.
Key arguments #
/repair:<target>/stage:validate
Example command #
vdjtools /repair:database /stage:validateExample output #
Virtual DJ Tools (vBeta)
Copyright© 2024-2026 Quick Apps UK. All rights reserved
Build: 1.0.38.0
repair: database
stage: validate
Validation complete: 9101 rows checked, 1721 ready to importSafety notes #
If validate lists a row, that’s the system working as intended — not a failure. Go back into the workbook, correct it, and validate again. Skipping this step, or treating it as a formality, is how a wrong Autofix guess ends up written into your library instead of caught in review.
Common scenario #
Autofix proposes a match that looks right at a glance but isn’t quite — validate won’t catch that on its own, but the habit of checking before you validate will.
