Question about looping from a controller

1 view
Skip to first unread message

Acer B-T

unread,
Sep 7, 2025, 3:01:16 PMSep 7
to AccessibleDJSoftware
Hi,

I've been trying to determin if this is possible, without any luck. I know that I am able to start loops on either deck, from both my keyboard and controller, but I am wondering, is there a way to make the loop act as if it's playing over the top of the track, to make it so I can loop a section but still have the song continue from where it would have if I hadn't started the loop? I ask because I use looping as a remix tool more than a way to extend something, where I'd want the transport to continue under neeth rather than playback going to the loop out point when the loop is exited, so I'd like to know if this behavior can be configured to work from the party mix 2, and the keyboard. I'm assuming it will probably require that i map a custom pad page and replace one of the pages in the controller mapping with it, but I don't want to do that if there's an easier way.

Zenek

unread,
Sep 8, 2025, 6:30:06 AMSep 8
to AccessibleDJSoftware
Hi, use one of these actions for the selected pad or shift+pad. You can also use one of the controller buttons as a switch with a long press.

slip_mode
While in slip mode, during loops hotcues or scratch, the play cursor will keep moving unaffected, and will resume from there after release

slip
activate or deactivate a global slip mode, that will save the position on "slip on" and resume where it should have been if untouched on "slip off", letting you do any scratch/loop/effect/etc in between

holding
execute different actions depending if the key is pressed for a long time or not: 'holding ? automix : mix_now'. you can specify the time ('holding 1000ms'), by default it's 500ms.

doubleclick
execute different actions depending if the key is pressed twice in a short period of time or not: 'doubleclick ? automix : mix_now'. you can specify the time between two presses ('doubleclick 1000ms'), by default it's 300ms.

That's why I recommend holding, because doubleclick waits time ms before performing the first action after the first press. Holding has no delay for the first action.

In your mapping I see that doubleclick clones decks, so if you don't use that you can use those buttons.
This way, loading of tracks will be instantaneous, and holding for 100ms will switch to sleep mode.
<map value="LOAD" action="holding 100ms ? slip_mode : load" />

If there is no voice prompt after switching sleep modes, type the actions below.
<map value="LOAD" action="holding 100ms ? slip_mode & slip_mode on ? deck all show_text &quot;# slip on &quot; 40ms : deck all show_text &quot;# slip off &quot; 40ms : load" />

Greetings and good luck, Zenek
Reply all
Reply to author
Forward
0 new messages