There are different ways how to configure your Cue Button. One is known as “Pioneer CUE”. This is how the Pioneer CDJs work.
In dJay for iOS there a two seperate MIDI Actions that can be mapped to the hardware CUE Button.
- Deck 1 → Cue Points → “CUE”. This is the “Pioneer CUE” mode.
- Deck 1 → Cue Points → “Jump To Cue”. This works differently than Pioneer CUE. But it has a bug.
All the details can be found in the MIDI Mapping Table
The difference between 1) and 2) is Pioneer CUE sets (or moves) the CUE point when the track is currently paused. The second mode “Jump to Cue” does not.
Current Behaviour of "Jump to CUE"
GIVEN a loaded track
AND there is no CUE point set yet
AND the track is currently paused
WHEN user presses the CUE button
THEN the “Jump To Cue” Action jumps to the start of the track.
Correct behaviour of "Jump to CUE"
GIVEN a loaded track
AND there is no CUE point set yet
AND the track is currently paused
WHEN user presses the CUE button
THEN the “Jump to Cue” Action sets a cue point exactly to where the playhead is.
GIVEN a loaded track
AND there is no CUE point set yet
AND the track is currently playing
WHEN user presses the CUE button
THEN the “Jump to Cue” Action sets a cue point to the nearest beat.
=> This is the same behaviour as HOT CUES. (Midi Action Deck → Cue Point Pads → Cue 1-8)
Reasoning
Some people don’t like the Pioneer CUE logic. If you pause your track and then press the CUE button, then your carefully set CUE point is moved to where the playhead is. This ist very often not what you want, because you very carefully set the CUE point to a specific position before.
For the same reason HOT CUEs have been inveted. If a HOT CUE is set it first needs to be deleted before you can set it to somewhere else.
For those people who want Pioneer CUE => They have the default “CUE” Midi action
For thos of us who want to have the HOT CUE functionality also on the CUE Button, plese correct the behaviour of the “Jump to Cue” Midi Action.
