How to Load Dropkit Tracks Into Engine DJ for Denon Players

Engine DJ loads a Dropkit track through its Desktop app: add the MP3 to the Collection, let Engine analyse it, set cue points in the Performance pane from cue points.txt or the comment tag, and export to a drive formatted exFAT or FAT32 for a Prime player. Engine DJ reads BPM, key, artist, title and cover from the standard tags but does not read the Serato hot cues embedded in Dropkit studio tracks. There is a second route if you also use Serato: load the tracks in Serato first, where the cues appear automatically, then import the Serato library into Engine DJ.

Steps

1. Download and organise the files

For studio tracks, download the DJ pack and unzip it so the MP3 and cue points.txt sit together. For DJ edits, press MP3 320. Put the audio in a folder that will stay put; Engine DJ references files by path and a moved file shows as missing. Keep the file names as downloaded, which are short and plain ASCII, so the Prime player displays them without trouble.

2. Add to the Collection and analyse

Open Engine DJ Desktop and add the folder or files to the Collection, then analyse them. Engine fills in BPM, key and the waveform. The BPM should match the TBPM tag because the file was rendered at a constant tempo. Check the beat grid: with the default Hard start on bar 1 a studio track begins on the first downbeat at 0, and a DJ edit begins with its drum loop on a bar, so the first grid marker belongs at the start of the file.

3. Set cue points in the Performance pane

Load the track and open the Performance pane. Using cue points.txt, move to each m:ss.mmm time, snap to the grid, and set a hot cue named for the line: intro end, first drop, outro start and vocal in when known. For a DJ edit, read the comment tag, which ends with start, intro end and outro start, and set those three. Intro end is exactly Intro bars from the start and outro start exactly Outro bars before the end, so counting on the grid works just as well as typing times.

4. Or import the Serato library instead

If Serato DJ is on the same computer, drag the studio MP3s into Serato first. Serato reads the embedded Serato Markers2 hot cues and Serato BeatGrid, so the coloured cues appear with no work. Then use Engine DJ's Serato library import to bring those crates into the Collection; the hot cues and grid come with them. This saves hand-setting cues on studio tracks, though DJ edits still need their three cues set by hand because they carry no Serato data.

5. Check the key

Engine DJ runs its own key analysis and shows that rather than the TKEY, INITIALKEY or OPENKEY tags. Dropkit's key is still in the comment of a studio track, for example 8A, 1m, A minor, and in cue points.txt. Compare if the two disagree, and edit the key field in Engine if you want the Collection to match the tag.

6. Build a playlist and export

Put the tracks in a playlist. Connect a drive formatted exFAT or FAT32, choose it as an export target in Engine DJ Desktop and export the playlist. Exporting, rather than copying files in the file browser, is what writes the cues, grid and waveform into the Engine database on the drive so the Prime player shows them. MP3 320 CBR and the 24-bit 48 kHz WAV both play on Prime players.

7. Verify on the player

Plug the drive into the Prime player and load a Dropkit track. The hot cue pads should show intro end and outro start where you set them, and the grid should sit on the kick from the first beat. If something is missing, go back to Engine DJ Desktop, correct it, and export the playlist again.

Tips

• Set intro end and outro start on the same two pads on every track, so mixing any file feels the same on the player.
• The Serato import route carries the hot cue colours too: red intro end, orange first drop, blue outro start, green vocal in.
• Keep cue points.txt in the track folder; it is the quickest reference when you set cues and it has the key in Camelot, Open Key and musical form.
• A tempo-shifted DJ edit lists its scaled cue times in the comment and the target BPM in TBPM, so trust the tag over the original song.
• Export to the drive from Engine DJ Desktop every time you add cues; the player reads the drive database, not your computer.

Common problems

• The track has no cues on the player. Files were copied to the drive instead of exported. Export the playlist from Engine DJ Desktop.
• No hot cues after adding a studio track to the Collection. Expected. Engine does not read the Serato frames. Set cues in the Performance pane, or import through Serato.
• The DJ edit has no cues even after the Serato import. DJ edits carry no Serato data. Set start, intro end and outro start by hand from the comment tag.
• The key differs from the comment tag. Engine analysed its own key. Edit the field to match the comment if you mix by Dropkit's Camelot values.
• Tracks show as missing after a move. Engine references files by path. Put the folder back or relocate the files in the Collection.