briDJe User Manual
Exporting and Backups
Last updated
An unfilled form: scope is 0 and tag consent is unchecked. It shows the controls, not a completed export.
Targets and what they write
On the Export tab, pick Traktor, rekordbox, Serato DJ, VirtualDJ or Engine DJ under DJ apps. Output is an NML file, a rekordbox XML, a Serato folder, a VirtualDJ XML plus an M3U playlist tree, or an Engine folder with Database2/m.db. briDJe never writes rekordbox’s master.db; import the XML in rekordbox yourself.
Output file (Output folder for Serato DJ and Engine DJ) is required: click Choose… to set it. Merge into is optional. 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. Engine merging targets version 2.
Scope, not selection
In the Tracks card, choose Playlists or All tracks. With Playlists, you can also tick Also export tracks that are in no playlist. Scope follows playlists, not table row selection or filters. Tracks are counted once even if they appear in several playlists. On the free tier, scopes above 15 unique tracks are blocked (Settings and Recovery).
Preview first
Preview export is read-only. It lists the tree, filenames, counts, warnings, how variable grids will be represented, and backup behavior. Its results appear under What will change and Summary. Fix blocking errors and review the warnings, then tick I reviewed the destination changes. Export the working preparation. and click the export button named for your target, such as Export to rekordbox. If the target changed since the preview, you need a fresh preview.
Backups
Keep Create backup (.bak) before overwriting ticked in the Options card. With backups enabled, briDJe preserves the existing output library and playlist files before replacing them. That may be snapshots or sidecar files, not necessarily a .bak for every format. It is not a backup of your music.
To use one, open the Tools tab, then Recovery bin. Under Export backup recovery, click Inspect export backup and choose a folder containing manifest.txt. Check the entries, then Restore copies to chosen folder copies them to a folder you choose. recovery-map.json maps original paths. Recovery leaves the original destinations untouched, so review the copies before putting anything back in the live app.
Serato audio tags
The tag-consent checkbox is unchecked by default. Serato cues, loops and grids need preparation written into the referenced audio files. The box reads Allow Serato preparation to be written into my audio files. Until you tick it, Preview export and Export to Serato DJ stay disabled.
Writers exist for MP3, WAV, AIFF/AIF, FLAC and M4A/MP4. OGG and WMA aren’t supported, and Serato preparation writing may block on them. M4A/MP4 positions are limited to 0–16777215 ms. Serato 4 ratings depend on the version. For a first test, copy the audio and export paths that point at the copies.
Limits to expect
A successful write isn’t lossless. Source preparation for a platform may stay only inside briDJe, and exports use the working copy. Serato and Engine omit unnumbered memory cues; they also keep only 8 loops a track, and the preview doesn’t list the dropped ones yet; Traktor can’t take arbitrary RGB; Engine ignores track color; loop lock and non-rekordbox meter limits apply (Loops, Beat Grids). Source audio isn’t copied or transcoded.
Verify
Close the target app before writing. Then check a small sample: audio paths, cues, loops, grids, playlist membership and sort. rekordbox needs a manual XML import. Test Engine hardware on its own firmware. briDJe doesn’t promise USB hardware sync. Undo in the status bar only reverses working edits.
