[Traktor Suggestion] Modifier (Shift) keys on keyboard applying to controllers

[Kelvin Yap]

Hey guys,

Today I thought I would add an extra feature to one of my M-AUDIO X-Session Pro knobs to control the gain (it's been bugging me a little bit, not being able to control the gain physically), so I decided I would set it to change the gain when a modifier key is held down.

Sounds easy enough? Not in this case!

Here's the problem:
I'm out of buttons to set as a modifier key on my MIDI mixer, so I thought making a modifier key on the keyboard would be a good idea (in this case, I wanted to map it so "." acts as Modifier #1 when held down).

It seems modifier keys on the keyboard only affect the keyboard and not other devices like the controller! I thought I mapped it wrongly, so I tried again with a different key on my keyboard, but to no avail.

I decided to try deleting a button my MIDI mixer temporarily (for "troubleshooting's sake") and map that as Modifier #1 and what do you know? It worked!

Conclusion: Setting a key on your keyboard as a modifier (shift) key only applies to the keyboard and not your controller. This is either a feature in Traktor or they didn't just didn't need to do what I'm doing so they left it out.

I reckon it would be awesome if Native Instruments added a feature into Traktor where the user can pick whether or not the modifier on Device A will affect the mappings in Device B or not, or if they want to make it even more customizable, allow the option to pick which devices a modifier from another device can be applied to!

I even added a poll so you guys can vote as to whether this would be a good idea to mention to Native Instruments or not

tl;dr If you set a modifier key on the keyboard, it won't affect/apply to the controller.

Cheers!

PS, I spelt necessary wrong in the poll options ._.

[zestoi]

the issue is bigger than just being related to the keyboard ofc. it's that modifiers are scoped locally to the Device that are mapped from. the offshoot is that if u run out of modifiers it's not biggie as u can just add a new Device linked to the same midi ports and u instantly have another 8 modifiers to use.

i think they should:

* extend the number of modifiers to something more sensible like 32 per Device
* extend the number of values that can be stored in a modifier
* add "global modifiers" that aren't scoped to any particular device at all (to solve your issue)
* allow a modifier to be set from an OUT as well as IN (would allow stuff like multiple out's for the same midi note/cc to be mapped, i.e: for multi coloured hot cues since traktor will send out all values (even to the same note/cc) unless they are masked with modifier conditions)
* extend the "conditions" to include stuff like ranges and more than just two conditions per control

edit: voted 'yes' but on the basis that the poll is just about whether they should they extend the functionality of modifiers

[Stewe]

* extend the number of modifiers to something more sensible like 32 per Device
* extend the number of values that can be stored in a modifier

At least 16 would be fine with me, but 32 would be sick

[Kelvin Yap]

i think they should:

Ahh yes, very good ideas there!

* add "global modifiers" that aren't scoped to any particular device at all (to solve your issue)

This would be even better if they allowed which devices to be blacklisted/whitelisted!