Engine DJ

For Engine DJ, select the Engine Library folder itself.

Import steps

1. Close Engine DJ so the library is saved and consistent.
2. In briDJe, click Import or press Cmd+I / Ctrl+I.
3. Choose Engine DJ and click Browse. Select the Engine Library folder.
4. Choose the scope. The default is everything. 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 library into briDJe’s working library and leaves the Engine files unchanged. briDJe can work with different Engine database generations on the source side, but test your own library rather than assuming every version works.

What to check

Load some tracks and verify by ear: beat grids, hot cues, loops. Imported smart playlist rules are static snapshots and are not executed.

If tracks are missing, the stored audio paths may not match where the files are now, for example when they live on a removable drive.

On a free-tier library, imports lock after 15 tracks have been reached, and a first batch can exceed that. See License Activation.

Exporting to Engine DJ

Choose Engine DJ as the target. The output folder gets a Database2/m.db library. Leave Target library blank for a new library. To merge into an existing one, supply its path; merging expects a version 2 target. Preview first (it writes nothing), then export.

Limits:

• Unnumbered memory or load cues are left out of pad banks unless you assign them to free pads.
• Loop lock flags aren’t transferred.
• Unusual meters or tempos can warn or block.
• Audio isn’t copied or transcoded automatically. Exported libraries refer to audio paths.
• Hardware and firmware compatibility isn’t guaranteed. Test a small export on your own player first.

Close Engine DJ before writing. Backups cover existing library files, not full audio. See Exporting and backups and Preparation and reimport.