Add Transition Memory feature

Feature Request: Transition Memory — Save & Auto-Cue Track Pairs & Autostart Track

The Problem

When I find the perfect transition between two tracks, there’s no way to save that knowledge in djay. Every time I load those tracks again, I have to remember the exact point (Track A) where I start the transition and at which point Track B starts. I know there are cue points which i can set and but quite often it makes sense to have this specific memory stored on the app.
The transition itself i would like to do on my own.

The Feature

Transition Memory — the ability to save, rate, and auto-start the transitions between track pairs.

How it would work:

  1. Save a transition: I’m mixing Track A into Track B. I’ve found the perfect moment where the transition starts
    Track A’s at 4:43 - the transition begins here,
    Track B autostarts at 0:30.
    that is basically it!

    djay stores:
    Track A cue point (e.g., 4:43) -
    Track B entry cue point (e.g., 0:30) - Autostart when Track A is at 4:43

  2. Auto-recall: Next time Track A is playing, I open the track browser
    and have a dedicated Tab for that, or integrated in Match

    Tracks that have saved transitions show a special indicator — maybe a link icon
    When I load Track B, djay automatically sets the cue points to the saved positions.

  3. Auto-start when Track A reaches the saved point, Track B auto-starts at the saved entry point, already synced. The DJ still controls the crossfader. The timing is just handled.

    Real-World Use Case
    Here’s a concrete example from my setup:
    ∙ Track A: Guy J — Karma (Original Mix) | 122 BPM | 9B
    ∙ Track B: Guy J — No Drama (Original Mix) | 123 BPM | 9B

    Same key, nearly identical BPM. I have set cue points here for those 2 Tracks.
    I need start the cue points exactly - so that i can switch the songs instantly - within one second. I need the perfect timing.
    Honestly, i can do that easily without the requested feature.
    But its a time saver on top of that.

    With Transition Memory, I’d load Karma, see that No Drama is a 5-star match, load it, and the cue points are already set. No Drama even auto-starts at the right moment. All I do is move the fader.

    Why This Matters

    For DJs who practice regularly and build deep knowledge of their library, the real skill isn’t beatmatching — djay’s sync handles that. The real skill is knowing which tracks work together and exactly where to transition. That knowledge currently lives only in the DJ’s head.
    This feature would:
    ∙ Reduce cognitive load during performance — focus on track selection, not transition logistics
    ∙ Build over time — new tracks get tested against the library, only 5–10 per week, with a few logical candidates each
    ∙ Make the library smarter — the more you use it, the better it gets
    ∙ Complement existing AI features

    How It Fits djay’s Roadmap
    djay already has:
    ∙ Match / Related Tracks — suggests tracks by key and BPM
    ∙ Neural Mix — AI-powered stem separation
    ∙ Auto-play when triggering cue point — instant playback from cue
    ∙ Cue points with color coding — up to 16 per track

    Transition Memory is the natural next step: take the DJ’s tested knowledge and make it persistent, recallable, and actionable.

    Platform

    I primarily use djay Pro AI on iPhone (iOS). This feature would be equally valuable on iPad and Mac.


Submitted by a progressive house DJ who practices 1–2 hours daily and believes the art of DJing is playing the right tracks in the right order.

I’d like to piggyback off of this idea, specifically for the Automix feature – I would love to create a self-playing mixtape playlist that locks in certain transitions I’ve set - something I can call upon if needed where the entire auto mix doesn’t need to either be set to “auto” or have the exact same transition type/length. it’d be great for songs A and B to use one transition type/length, and then B/C to use another, and for C/D, D/E, etc etc. What I’m asking for is definitely a departure, but I believe the underlying code for both features could have a lot of overlaps. If this should be a separate request, I’m happy to do so! @Senor_Robiwan love your idea!

1 Like

Hi @Senor_Robiwan, welcome to the Community! Thanks for the suggestion. I’ll share this with our devs for consideration.

Thanks for the additional input as well @jakemprice

1 Like

thank you very much for taking into consideration.
I am happy to help

1 Like

You’re welcome