VirtualDJ

For VirtualDJ, select database.xml. Keep the adjacent Playlists folder next to it, since playlist hierarchy is read from there.

Import steps

1. Close VirtualDJ so the database is saved and consistent.
2. In briDJe, click Import or press Cmd+I / Ctrl+I.
3. Choose VirtualDJ and click Browse. Select database.xml.
4. Choose the scope. The default is all tracks and playlists. You can instead select playlists; ancestor folders are included.
5. Click Preview import.
6. Review new, changed and absent tracks and playlists, plus local edits, conflicts and uncertain matches.
7. Accept and apply.

Import reads the database into briDJe’s working library. The VirtualDJ files are not changed.

If playlists are missing or flat, check that the Playlists folder is still next to database.xml and wasn’t moved or copied separately.

What to check

Load a few tracks and check by ear: beat grids, hot cues, loops. Imported smart rules are static snapshots and are not executed. Missing tracks usually mean the stored audio paths no longer match your files.

On a free-tier library, imports lock once 15 tracks have been reached; a first batch can go beyond that. See License Activation.

Exporting to VirtualDJ

Choose VirtualDJ as the target. briDJe writes the XML plus a sibling Playlists tree of M3U files. Leave Target library blank for a new library, or supply an existing path to merge, with a separate output path. Preview first, since it writes nothing.

• Loop lock flags aren’t transferred.
• Unusual meters or tempos can warn or block.
• Audio files aren’t copied or converted. The export refers to existing paths.
• Backups cover existing library and playlist files, not audio.

Close VirtualDJ before exporting, and verify a small test in the app before sending more. See Exporting and backups and Preparation and reimport.