+20 for this. I am frustrated at Traktors lack of development and REALLY LIKE what I see in so many ways with Dj Pro. I’m trying to move full time to DJ pro, and this is one of those factors for me, and other Dj/Producers we work with. I also believe we absolutely need more modifiers/states to make this really competitive and get working Dj’s moved over.
Been working on a mapping for our K2’s within Dj Pro Ai, to match what my wife and I do with Traktor. STAFF AND MODERATORS: please read this, we are trying to make the leap to DJ Pro AI, completely, but it is very difficult without advanced Midi functions like this. If you want to grab widespread adoption, I would suggest this as a way to do so by real working Dj’s. We also need to be able to control the OUT states of midi for lights etc. Use case would be, the button I use for “Play” on my K2, blinks while playing, rather than when stopped, or even blinking to the BPM. Right now if I use the lights, for things like cues etc, the whole controller is just on with red lights. Not very useful when working high paced in the booth.
Anyhow, I digress…it is very limiting only having one modifier(the shift key) in DJ Pro because it leaves much of the controller only able to function in a minimal way. There’s been so many positive developments with DJ Pro, I hope that you can look at features that will make it more usable, like this, rather than adding more toys that nobody really uses. Another good example that working DJ’s producers could really use, are sampler and looper that we can load with our own.
I hope this feedback comes in handy because I really think that this software is on to something! Thanks for listening!
2 Likes
I’ve heard other people mentioning that you can do this by editing the XML files if you can’t wait for Algoriddim to add this to the UI. I myself, have very little experience with XML files so I wouldn’t really no where to begin.
I know nothing about this at all. I’m a Dj, not a programmer…LOL!
1 Like
LOL! Exactly! Sounds like it’s doable and not really that difficult if you’re willing to do some research and learning. I mean let’s be honest… complex MIDI mapping in Traktor with multiple modifiers and conditions isn’t exactly a walk in the park 
although complex MIDI mapping in Traktor is much faster and easier than doing it in an XML editor. All Algoriddim needs to do is have a ‘super advanced MIDI’ option in the settings that those of us can activate if we want to, but would stay hidden for anyone else
Please Algoriddim, can we get this done? 
2 Likes
+1 for Traktor-style modifiers… would greatly enhance the possibilities with something like rellop’s neon, for example… allowing use of the bank buttoins to select separate decks.
The ‘if in active loop’ modifier in Traktor is also very handy.
2 Likes
Hey @Jake_Williams and everyone who posted here,
Thank you for your feeback, we are grateful for it and find it useful, so don’t hesitate to share or to keep sharing it!
I will be passing this feedback on to our Dev Team and keep you posted with any updates. Cheers 
2 Likes
This would be awesome for mapping my midi fighter 3d
3 Likes
Just think about how much more ‘bang for your buck’ you could get out of just one controller. Also, learning about modifier states and conditions when I used to map with Traktor was what got me interested in coding later on.
1 Like
+1 for modifiers. It is very important to have more modifiers available to make complete maps on midi controllers. I also switched to djay pro because I see future and development but we have been asking for this option for a long time now, please make this possible. thanks
I’m up to this! im using some controllers for the FX and neural but sometime i’m limited because the lack of modifiers
1 Like
Hi, is there a chance that DjayPro implements so-called modifiers (like NI Traktor) for the mapping? Since the shift button does not cover all possibilities. Greetings
I realise this is an old thread but I am new to trialling DJay Pro from Traktor and these suggestions for modifiers would be awesome to allow us to get more out of our NI controllers. I have just about every Traktor controller and would love to get more out of my S2 Mk3 and D2s. Recognising active loops or even just the shift key would be a welcome addition. I’ve been using DJay Pro only a couple of days and I’m already wishing it did this… thanks.
1 Like
Hi @DoctorBlock, thanks for the input. I have passed this onto the dev team for consideration. In the meantime, please use the blue Vote button at the top left of this page so we can gauge user demand for this.
I support this feature. A dj software and midi controller are the leading actors and the correlation between the two is important. Midi is one of the most important basic concepts here and it is important that it is capable. I have been a Traktor user almost since the day it was first released, and one of the few things that binds me to Traktor is this flexibility in midi mapping. And additionally midi mapping should be improved in general. +1500
(used translation)
I agree with that, but this would be new Pandora’s Box for sure.
1 Like
@Slak_Jaw, please escalate this to the R&D team again. Let us have a “Conditions” in the Advanced Section, where we can see and set per command modifier conditions in the mappings UI.
They modifiers support is there in the engine, and every command can evaluate a condition. It’s just not accessible to us, the users. And we need it.
As a first step, just let us see and edit them per command. That should be relatively easy for the Dev Team.
A full implementation to manage and construct new modifiers would also be useful for unsupported controllers, but for enhancing supported ones, the mapping team does great job in defining modifiers, and we can just build on top of what they did.
Example Use Cases:
I’m overmapping stuff with a custom SHIFT (secondary) key on an MC7000.
- I want and to set 3rd action for the PADs. But through the UI, I cannot take into account the selected Pad Mode. There’s a “condition” defined in the XML which evaluates the Pad mode, and does different things, but it’s not accessible to me at mapping time through the UI. Therefore, I can only set one custom SHIFT override for all the PAD modes for the deck. If I can adjust the condition in the mapping UI, I will be able to set different things for the pads to perform in each of the Pad Modes (Cue/Roll/Slicer/etc). This would give me tons of extra actions to perform in the context of the selected Pad mode.
If the UI has the “Condition” section, I would read the conditions of the stock Pads maps; do a “Duplicate” of the (+SHIFT) entry; edit the condition of the duplicate; set the right condition for it and define the assignment command for selected PAD mode.
- I want to set the FX1/2/3 On/Off buttons of the controller to assign the Drums/Harmonic/Vocal NM channel to the respective FX 1/2/3 slots when a custom +SHIFT is pressed. It works well for decks 1 & 2, but it’s not working for Decks 3 & 4, as there’s a hidden condition in the mapping file for when we switch decks 1/3 & 2/4. As I cannot see/edit a condition in the mapping UI, my custom SHIFT mapping only works for 1&2 no matter that decks 3/4 are active.
If the UI has the “Condition” section, I would read how the stock FX maps are configured, will do a “Duplicate”; edit the condition of the duplicated entry; and apply the NM FX assignment command with the right condition for Decks 3 & 4.
A condition in the XML looks like this:
<key>condition</key>
<string>modifier5 == 0</string>
For the MC7000, “modifier5” holds the state of which deck is selected - Deck1=0, Deck3=1. Simple.
I’m now playing with this and achieve what I want with a “duplicate” through the UI, followed by adding/editing the conditions in the XML, but that’s a very hard way to do it. Dev-wise, it’d be relatively easy to expose the “Condition” string in the Mapping editor UI.
I will create a HOWTO post for others to do these settings with their controllers too, but messing with these XMLs directly is unsafe and not the right way to do it. Yet, it works 
There are multiple modifiers in the XML, and are not documented (and no comments in the XML), but who cares. It’s easy to check what is used in a similar command, test one-two values and figure out what does the job. If we have access to the string in the UI, we don’t need to mess with the XML code in the file.
BTW, we have communication on this in a thread from few years back…
1 Like
