I was working with a Serato user last night, using a DDJ-1000 SRT controller, and I just noticed that the Loop In/Out buttons, when a loop is active for the track, seemed to behave differently for that controller, as compared to the DDJ-1000 and DDJ-FLX10 - the loop out button especially, seemed to half the loop on press.
After checking the mapping, can see that, for example, for loop-in, the DDJ-1000 is mapped this way:
the DDJ-FLX10 is mapped this way:
and the DDJ-1000 SRT is mapped this way:
and the shift + Loop In for the DDJ-1000 SRT button seems to have the desired behaviour
I know that this can be remapped, but I'm just curious - what is the reason for the difference in behaviour?
I have to admit that behaviour difference caught me off guard - I actually didn't figure it out on the spot because I assumed the DDJ-1000 and DDJ-1000 SRT would be mapped similarly.
After checking the mapping, can see that, for example, for loop-in, the DDJ-1000 is mapped this way:
loop ? loop_adjust 'in' ? loop_adjust 'in' : loop_half : pioneer_loop_in
the DDJ-FLX10 is mapped this way:
loop ? dualdeckmode_decks & loop_half : dualdeckmode_decks & pioneer_loop_in
and the DDJ-1000 SRT is mapped this way:
pioneer_loop_in
and the shift + Loop In for the DDJ-1000 SRT button seems to have the desired behaviour
loop_half
I know that this can be remapped, but I'm just curious - what is the reason for the difference in behaviour?
I have to admit that behaviour difference caught me off guard - I actually didn't figure it out on the spot because I assumed the DDJ-1000 and DDJ-1000 SRT would be mapped similarly.
Posted Thu 24 Jul 25 @ 2:09 am
DJ VinylTouch wrote :
what is the reason for the difference in behaviour?
...
because I assumed the DDJ-1000 and DDJ-1000 SRT would be mapped similarly.
...
because I assumed the DDJ-1000 and DDJ-1000 SRT would be mapped similarly.
Their silkscreen (what's printed on them)
We have emphasized several times that when we map controllers we try to map them as close to their silkscreen as possible.
So, the DDJ-1000 (a Rekordbox oriented controller) has IN-1/2X and OUT-2X printed on the buttons:

On the other hand, DDJ-1000SRT (Serato Oriented) has only IN and OUT printed on the buttons:

To make matters worse, look what's printed under the buttons in reverse gray box.. That's the SHIFT+ operations.
For DDJ-1000, SHIFTed operations are loop adjust.
For DDJ-1000SRT, SHIFTed operations are loop half/double
Pretty much that's the reason the mappings are different.
Then sometimes there are some technical details/reasons behind some device specific functions.
For instance FLX10 has the ability to "SPLIT" a track on 2 decks because of STEMS. Therefore it's loop actions take that into account and if necessary, apply the loop actions initiated from one deck to both SPLIT decks.
Posted Thu 24 Jul 25 @ 5:39 am
Ah that make sense. I didn't get to read the markings on the controller there (it was minimal booth lighting anyways), or read/double-check the manual for the controller before that time, and I normally work with my DDJ-1000 which does the half/double logic without shift.
I'll keep that in mind for future 🍺.
I'll keep that in mind for future 🍺.
Posted Thu 24 Jul 25 @ 1:04 pm
Another MAJOR difference between the two, is which button is SHIFT.
If you develop muscle memory with one of the two variants then it's very easy to misshandle the other one..
Especially since "it's in the same place, but it's the other button"
;)
If you develop muscle memory with one of the two variants then it's very easy to misshandle the other one..
Especially since "it's in the same place, but it's the other button"
;)
Posted Thu 24 Jul 25 @ 9:24 pm
That caught me too - I ended up hitting what I believe is the grid adjust button a couple of times in an attempt to find out if the functionality was behind shift, and that did nothing, so I ended up not using loop size changing for the set from the controller (I did it from the UI), then looking at it afterwards and seeing that major difference (Shift is where Memory is on the DDJ-1000).
Posted Thu 24 Jul 25 @ 10:22 pm





