Hi @Ben_Cislaghi, the Cue Loop MIDI command is now a legacy command. This was replaced when we combined regular Hot Cues with with Cue Loops. In the more recent versions of djay, if you press a Hot Cue while you have a loop active it will save it as a Cue Loop instead of a Hot Cue.
If you want to have the option of either a Hot Cue or a Cue Loop, I recommend that you use the Saved Loops function instead.
I am not sure I was clear in my earlier post, sorry
I am not looking for a way to save loops as hot cues. I know how to do that.
I want to understand how to do what already existed before: a command that, when triggered, makes the software jumps to that specific point in the track and automatically activate a loop of a pre-set length (e.g., 4 or 8 beats), saving me from having to set one manually.
I do not want to save hot cues as loops, as I want the flexibility to choose each time whether I need the loop or the normal hot cue (not to mention that I have 4000 songs with normal hotcues and the prospect of saving them all as loops makes me want to jump off a cliff).
What I am trying to set is the command that existed before (I have it mapped on my X1). I had hot cues that function as a normal hot cues, unless a specific command is given through midi (what I need now), in which case djaypro starts a loop at the hotcue point. What do I need to do for that to happen? This existed (as I used it all the time) and was amazing because that way each time I could choose whether to start the hot cue and play the song normally, or having already as a loop in preparation of a transition.
Hi again @Ben_Cislaghi, please do not create multiple topics for the same thing. This just makes it harder to keep track of things and answer in a timely manner. I’ve merged your second new topic with your first.
I understood your original question. As I outline above, the “Cue Loop” MIDI command was removed in new versions of djay. If this command was already in an old MIDI mapping it will remain there, but it is no longer available in new MIDI mappings.
If you want to create a similar function without using Saved Loops and mapping those to your Shift Layer, you could try using the duplicate feature in the MIDI Learn tool to map multiple commands to the same button. In your case it would be something like Cue 1 and Auto Loop. I don’t have time to test and mapping this myself at the moment, but this might point you in the right direction.
On macOS, you can access the duplicate feature by R-Clicking on the MIDI Note or CC in the far left column and selecting Duplicate Mapping for Control. This will essentially create a copy of the MIDI command that you can assign to a second function. I hope that helps!
I’ll check in a soon as I can to see how your making out with this…
I had already tried this solution, but it won’t work as the autoloop gets created in a slightly different position as the cue point, (imagine cue point at bar 47.1, loop at 47,3 or 48.2). then I need to adjust it, so that becomes inefficient. Better to press cue, jog wheel back, let the song proceed, start an autoloop manually.
But you see how long that ales as opposed to the automated workflow that used to exist?
This is a critical feature for me as it makes preparing for transitions much easier. I designed blue hot cues to be, for instance, before all drops so that I just loop and sync when appropriate before transitioning.
Would it be possible to bring back the command in the list of possible midi inputs ?
You’re welcome @Ben_Cislaghi. I’ve changed your topic to a Suggestion and have adjusted the title accordingly. I have already shared this with our dev team to see if it’s possible to bring these MIDI commands back in the MIDI Learn tool. I’ll report back when I have more news. Thanks!
