Traktor is loading mappings that are not even loaded?

[avaizhashmi]

Hey guys, I am back for help

In short... Traktor 2.6.1 is not loading mappings properly. My controller is responding to some mapping that is not loaded in the Controller Manager and when I am working on a mapping, LEDs start responding differently all of a sudden, LED is ON instead of OFF.

Discussed here as well. http://www.native-instruments.com/fo...ppings.183201/

I think its a conflict somewhere. Is there a cache or something thats causing this?

Thanks.

[DJAdeSands]

In controller manager, are there any live mappings that shouldn't be there?

[avaizhashmi]

Thanks so much! I had to clear all the profiles under Devices. So does it mean that all those profiles are active as the same time? I mean they are conflicting or they are all selected at the same time? I am not clear on this.

[mostapha]

They're all there.

You choose which device is attached to a mapping with the in and out drop-downs.

IME, traktor is actually pretty good about simple things. For example, I have 2 X1s, but I only use 2 effects units. Rather than having the top half of one of them useless, they do other things. When they boot up, you select a/b, c/d, a/c, etc.. But the manual mapping for the top section stays with the one defined with those drop-downs.

If you take the lazy approach and set any of them to "all ins", it's really easy to get incredibly freaking confused, especially if you're using things that work via generic MIDI instead of Traktor's protocol.