Return to 1st cue point after ending

Hey there,

→ See this video

Situation:

  • When a track is loaded from the library, it automatically jumps to the First Cue or Start Cue (depending on the setting: General > Jump to Cue Point).
  • After a track has ended, it automatically returns to the beginning.
  • But it just goes all the way back to the start of the track, not to the First Cue or Load Cue.

That seems like a bug to me.

===
Device: MacBook Pro (16", 2019)
Processor: 2,6 GHz 6-Core Intel Core i7
Operating system: Mac OS / Sequoia 15.4.1 (24E263)
Djay version: Djay Pro 5.3.1
Hardware/controllers used: Reloop Mixon Pro 8

And here’s my new suggestion for an additional option: combining the Start Cue with the Earliest Cue Point.

If you like it, please give it a vote!

Hi @DJ_Big_Blender, I believe this is currently expected behavior as that setting is for “Song Loading” and in this scenario the song is not re-loading. However, you do make a valid point and this does make sense. I’ve passed this onto the dev team for consideration. Thanks!

1 Like

It’s a small thing, but it shouldn’t be too hard to apply that same setting to a reload as well.

In case you want or need to play the same track again, it’s better if it’s reloaded to the correct point. This also makes it easier to monitor the loading behavior.

I’m not sure where this currently stands, but I’d still love to see it addressed. There are live DJ scenarios where you may need to restart the same track immediately, whether to continue a mix, fine-tune timing, or recover from a technical hiccup. When the track jumps back to the absolute beginning instead of the First Cue, it adds unnecessary friction and slows down the workflow.

Having consistent cue behavior, even after a track ends, would make live performance smoother, more predictable, and ultimately more professional.

==> If you agree this would improve usability, please upvote or comment. The more traction, the better.

Thanks!

Hi @DJ_Big_Blender, as this is currently expected behaviour, I have changed this topic from a bug report to a suggestion. The dev team will take this under consideration if there is additional user feedback and support for it. Thanks!