briDJe User Manual
Engine DJ
Last updated
For Engine DJ, select the Engine Library folder itself.
briDJe support still being refined. Engine DJ import and export work today and we’re still refining briDJe’s support for them, so expect some edge cases. Test a small export first and keep a copy of your library.
Import steps
- Close Engine DJ so the library is saved and consistent.
- In briDJe, open the Import tab or press
Cmd+I/Ctrl+I. - Under DJ apps, choose Engine DJ. In the Library folder card, click Browse and select the
Engine Libraryfolder, or click Use this library if briDJe found it. - Under What to import, keep All tracks + playlists (the default) or pick Choose playlists…; ancestor folders are included.
- Click Preview import.
- Review the preview: new, changed and absent tracks, new, changed and removed playlists, plus local edits, conflicts and uncertain matches. The Summary card counts what’s new, updated and in conflict.
- Click Import.
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
On the Export tab, choose Engine DJ and an Output folder. The output folder gets a Database2/m.db library. Leave Merge into unset and briDJe merges into the library already at the output if there is one, or writes a new one if not. To merge into a different library, click Choose… on the Merge into row; merging expects a version 2 target. Click Preview export first (it writes nothing), then Export to Engine DJ.
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.