Bug: Being able to scroll past track end and set hot cues in empty space
→ I’ve recorded this video about it
Description:
In djay Pro (confirmed in both the latest and older versions), it is currently possible to scroll / skip beyond the actual end of a track into what appears to be a non-existent or “empty” space. Within this space, users can place hot cues — even though there is no waveform or audio content present.
Steps to reproduce:
- Load any track into a deck.
- Scroll (or scrub) toward the end of the track (with or without playing or PFL-ing it)
- Continue scrolling — the playhead will pass the actual end of the track into blank space.
- Observe that the timer continues to count up beyond the track’s real length (e.g., 150+ bars after actual end).
- Place a hot cue in this empty area.
- Notice:
- The cue is saved and can be triggered
- The waveform does not reflect this area or hot cue.
- When reloading the track, the hot cue remains placed in this non-existent area.
- Pressing the Cue button beside the deck returns to the start of the track, while pad-based cue triggers try to jump to the invalid area.
Expected behavior:
Once the track ends, scrolling should stop and probably bring you to the beginning again. No hot cues should be placeable outside the bounds of the actual audio file.
Actual behavior:
Users can:
- Scroll indefinitely past the track’s endpoint.
- Place and recall hot cues in an invalid, silent area.
- Visibly see cue markers on the deck display, but not in the waveform.
- Trigger unintended behavior when using cue buttons after this state.
Impact:
This causes confusion during performance or practice, as cues placed in these areas serve no purpose and may trigger glitches or inconsistencies during playback or deck reloads.
Suggestion:
Implement a boundary check that prevents the playhead from scrolling beyond the real length of the track and restrict hot cue placement to within the waveform/audio duration.
→ I’ve recorded this video about it
Thanks for taking a look at this issue!
To us that makes sense, but strangely there are DJs out there who want to set cues outside the boundaries, where there is no audio and the track “doesn’t exist”.
Something to do with triggering the cue early, then letting the silence play, until the incoming audio starts at some later point (e.g. a drop in the outgoing track).
Why not just set the cue at the start of the audio and trigger it when you need it? 
I find it odd, but to some it’s a thing.
Hi @DJ_Big_Blender, I’m pretty sure this is expected behavior as @PKtheDJ has suggested. I have reached out to the team to determine if this is indeed expected behavior or not. I’ll let you know what I hear back.
Hi again @DJ_Big_Blender, I heard back from the team and this is indeed intended behaviour. Currently we have the same behaviour as other software as this is often used by open format DJs. However, your UI point about the Hot Cues not showing on the overview waveform is duly noted. The dev team is going to review options for this. Thanks as always for the observations and input!
Ok, but I don’t really understand why this is considered expected behavior, especially since the hot cues in that ‘empty space’ ultimately lead back to the start of the track. When you press them, it sounds like the track starts playing unstable. The purpose of this is unclear to me, as it seems to cause glitches and inconsistencies that could be confusing during a live performance or practice session.
We’ve added this because other users request that they can set cue points past the end.
It doesn’t make any sense to me. I was even able to scroll through to a point beyond 1.440 bars—and counting. That’s over 50 minutes of empty end-trail. Who uses this, and for what purpose?
The problem is that it causes a lot of confusion. If you (accidentally?) set a cue point there, sometimes it triggers a part from the beginning of the song, and other times the start cue jumps to that empty part—which isn’t even visible. So you’re left wondering why your track isn’t starting to play… really frustrating.
