rekordbox XML
DJWhat it's for — Moving a prepared collection between rekordbox and CueSync as a file, with no Pioneer hardware in the room. Bring in the hot cues and beat grids you set in rekordbox on a studio laptop, or send the cues you placed in CueSync's Track Prep back to rekordbox for the USB. Both directions are part of Track Prep, so they need DJ Edition or CueSync Production.
Importing a rekordbox collection
In rekordbox, export the collection as XML (File → Export Collection in xml format). Then choose Import rekordbox XML… in CueSync and pick the file.
- Every track whose audio is on this machine is imported — its beat grid, hot cues, memory cues, loops and key land in CueSync's analysis, so opening it in Track Prep uses rekordbox's grid instead of analysing from scratch.
- Tracks whose audio is not on this machine are skipped and counted. Copy the audio across, or import the XML on the laptop that has it.
- Phrases come only from rekordbox's analysis files. The XML has no phrase map. If the track's
.DAT/.EXTanalysis files sit beside the audio, CueSync reads the phrase map and the measured beat grid from them too; without them AutoPilot has no phrases for that track. - A track CueSync has already analysed keeps its phrases and grid. rekordbox's hot cues, memory cues and loops are merged into it.
- A row with an impossible tempo or length comes in without a beat grid. A track whose tempo and length ask for an impossible number of beats, or that would take the whole import past what one import takes, is still imported, but without a grid, and the confirmation counts them (N without a beat grid). Ordinary tracks keep their grids, a four-hour mix included.
The confirmation message says how many tracks were imported, skipped, merged, already up to date, unreadable, or without a beat grid. A file CueSync cannot read as a rekordbox collection is refused with a message saying so. A very large export (over 256 MB) is refused before it is read, with its size and a request to export a smaller collection or a playlist from rekordbox instead.
Exporting to rekordbox
Export to rekordbox XML… writes every analysed local track in Track Prep — its beat grid, BPM, key, hot cues, memory cues and loops, including the markers you moved, added or deleted in the Track Prep editor — as a collection file that rekordbox 6 and 7 import. It never touches rekordbox's own database: you load the file into rekordbox yourself.
- Markers CueSync detected are exported too. Hot cues, loops and memory cues that the analysis proposed — not only the ones you placed or moved — are written as ordinary rekordbox cues, and rekordbox cannot tell them apart afterwards. Delete the ones you do not want in Track Prep before you export.
- Phrase maps are not exported. The rekordbox XML format has no phrases, so phrase corrections stay in CueSync.
- Marker edits made against different analysis are left out. If a track's source markers changed since you edited them, that track is exported with its current markers instead, and a message that stays on screen names it. Re-open it in Track Prep, re-confirm the edits, and export again.
- Nothing analysed yet? The export says so and offers Open Track Prep.
When a USB stick's library is damaged
CueSync reads the library on a rekordbox-exported USB stick (an Opus Quad's included) directly. If the stick's database is damaged, a notice that stays until you close it says The rekordbox library on '<stick>' is damaged, so CueSync did not read it and none of its tracks are in the library. Export the library to the stick again from rekordbox. None of that stick's tracks appear in the library until you do. CueSync does not read the stick again until its library file changes, so a fresh export from rekordbox is picked up by itself.
When a USB stick stops answering
A stick that stops answering no longer holds up the rest of the app. A notice that stays until you close it names the stick: The USB '<stick>' has stopped answering, so CueSync has stopped reading it to keep everything else fast. Take it out and put it back, or try another port or cable. Reading stops on that stick instead of waiting out thousands of timeouts. Pulling a large stick's library no longer keeps all of it in memory, and the disk caches keep to their limits while the app runs. A link on a stick cannot lead CueSync outside the stick's rekordbox folder.
Related
- Track Prep — Analyse tracks and place the cues these files carry
- Library — Track Prep's browse level, where you find a track to open
- Devices — Reading rekordbox analysis live from connected Pioneer players
Looking for a quick fix?
The Help Center has short task-focused articles and a support team that responds within 24 hours.