Skip to main content
Dub reads your other DJ apps’ libraries. It never writes to them, so you can keep using Serato, Traktor or rekordbox alongside it.

What Dub reads

Serato DJ 4 keeps its library in a new database instead of the _Serato_ folder. Dub reads that too, and when both are on your Mac it reads the one Serato wrote last. Serato’s smart crates don’t come across. Dub has been checked against Serato 4 but not yet Serato 5. If your Serato 5 crates don’t show up, export from your library manager to rekordbox XML instead, or see Lexicon.

Turn a source on

Open Preferences ▸ Library and switch on the apps you use. Dub looks for each library where that app keeps it and adds the app to the sidebar under IMPORTED SOURCES, with its playlists underneath. If your library lives somewhere else, right-click LIBRARY or All Tracks in the sidebar and choose Import, then the source and its file.

Apple Music

Apple Music can keep several libraries (hold ⌥ as you open Music to switch or make one), so you can keep one just for gigs. Dub follows one of them:
  1. In Music, open Settings ▸ Files and turn on Share Library XML with other applications. Music then keeps an XML of the open library up to date. (Or export one with File ▸ Library ▸ Export Library….)
  2. In Dub, open Preferences ▸ Library, click Choose… on the Apple Music row and pick that XML. Default goes back to the library in Music’s usual place.
Dub reads that library each time it starts. Changed it in Music since? Right-click Apple Music in the sidebar and choose Reload Apple Music Library. Dub never rereads it on its own, so nothing competes with your set for the disk. Choose another library and the node changes over to it. A track that leaves the library leaves the node, but it stays in your collection if you played it. A track whose file is on a drive that isn’t plugged in stays put until the drive is back.

Browsing versus your collection

An imported app’s tracks are there to browse: they show under that app’s node, but they don’t fill up All Tracks. A track joins your collection when you play it, or when you import its folder (Import ▸ Folder…). Your grids and hot cues from the other app come with the track: the grid drives Dub’s beat grid, and the hot cues fill the deck’s pads. Dub still analyses tempo and key itself and flags a track with ⚠ when its own reading disagrees with the imported grid.

A track in more than one app

Dub matches the same file across apps, so a song you find through an Apple Music playlist carries the grid and cues Traktor has for it.
  • Beat grid: a grid you fix in Dub comes first, then Serato, then rekordbox, then Traktor, then Dub’s own analysis.
  • Hot cues: cues you set in Dub come first. Otherwise the pads show one app’s hot cues, the first of Serato, rekordbox and Traktor that has any. The HOTCUE heading says whose, for example FROM TRAKTOR.
  • Your first change to one of those cues makes the set yours. The change sticks, a cue you clear stays cleared, and later edits in the other app no longer reach Dub’s pads. The other app is never written to.
The same explanation is in Preferences ▸ Library.

Re-importing

Importing again refreshes what Dub knows from that app and picks up new tracks and playlists. It never touches what you did in Dub: your crates, beat-grid corrections, ratings and play history stay.

Missing files

If tracks have moved, the corner of the library shows how many are missing. Click it to relocate them.

Taking it back out

File → Export Library As… (⇧⌘E), or Export As… on a crate’s right-click menu, writes:
  • rekordbox XML: tracks, beat grids, hot cues, loops and crates. Serato, Traktor, rekordbox and Lexicon can all read it.
  • M3U8: a plain playlist of file paths, readable almost anywhere.