Traktor Multiple Active Controller Mappings Conflict/Question

Traktor Multiple Active Controller Mappings Conflict/Question

Hi,

I have been using Traktor Pro on a DN-MC6000 (controller/mixer) for some time without any problems. A few months ago, I also started using a Denon SC2000 (single deck controller) for club gigs where a mixer was already available and it was unpractical to bring the MC6000. I had a lot of problems after installing the included SC2000 .tsi files because some functions became erratic on both. It’s as if the mappings had conflicts between each other. The way I KINDA fixed it, is to have two separate SETTINGS folders on my Mac, one with the MC6000 tsi files, and one with the SC2000 version, and dragging either one into Traktor’s folder each time I switch controllers. As of today, I am also going to incorporate an MC3000 (smaller mixer/controller) into my setup for using at smaller gigs. I am having the same problem as when I imported the SC2000 files into Traktor. Adding the MC3000 tsi to my Traktor software alongside the usual DN-MC6000 files, results in erratic behaviour. I figure that maybe some mapping functions are redundant (for example scrolling in the browser skips the next track every time and lands 2 tracks from the current one). I searched inside the Controller Manager and deleted the mapping line that controls this in the MC3000 file. Now the browser knob works fine (I suppose that it is obeying the older MC6000 mapping which is now the only one programmed for browsing and thus not redundant). Problem is, other functions are also misbehaving (PLAY buttons only work when SHIFT is pressed, etc.). I am not very comfortable tweaking settings or mappings in the Controller Manager, thus not looking forward to a long and confusing session trying to sort these things out. Having practically accepted that working with Traktor mappings for all 3 controllers installed at the same time is not possible or practical, I’d like to ask anyone who has any insights or advice as to which is the best way to handle this scenario. I believe it is important to state that for adding .tsi files, on the Controller Manager window I’m using the upper ADD… button instead of the lower IMPORT option. The reason for this is that the ADD option simply adds the new mappings to my existing settings, but the lower IMPORT option overrides all my previous information and installed files and leaves only the mappings that are being imported.

In spite of my limited experience working with the Controller Manager, I figure that one possible solution is to create 3 versions of my personal .TSI file, one optimised for each controller, and then IMPORTing the right one every time I switch controllers for a specific gig. This would override the current files and install the new desired one (including whatever other tweaks, layouts or personalisation I use). Doesn’t sound very practical but I believe that it might work. The problem with just doing it like that straight off the bat with Denon’s supplied mappings, is that as of now, besides the mappings for each of these Denon controllers I also have mappings for other gear installed - like two Traktor Control D2’s that work flawlessly in tandem along with my MC6000 and some mappings for browsing on a DNX1600 mixer at the club. I wouldn’t want these mappings to be overwritten or deleted every time I IMPORT Denon’s original tsi files when switching controllers. I have to add that none of these additional mapping files have been causing any conflict with my MC6000. It is only when I add another Denon device that the problems arise. Surely, there must be a clean and practical way of solving this.

Thanks in advance to those who read my long post, and more so to anyone who can share their thoughts.

System: Macbook Pro, El Capitan, Traktor Pro v. 2.10 (latest). Latest firmware on all devices.

Check your in port/out port routings on controller settings are for the relevant connected devices. Make sure each command table is for the correct input device. If you have the routings down as all ports, that will have conflicts when the 2 Denon Units inevitably run the same commands (CH and CC/Note)
On each imported .tsi make sure ‘All Ports’ are changed to the appropriate denon device for the proper .tsi import file. (small import at top, not the large button at the bottom of controller manager)

Thanks a lot for your response. I will try to make sense of your suggestion and see if that works. But after fiddling a little with that OUT PORT section, I have a feeling that it might have something to do with it.

Best!

The ‘in’ port is the important one here mate.
Glad you are making progress.. nice :smiley:

Wonderful. Yes, tweaked the IN port to the appropriate controller, and although I only have one device here at the moment for testing, all .tsi’s are loaded and behaviour is perfect. Thanks for such useful help, it went a long way!

Great! Glad you got sorted

Beware, some SC-2000 mappings need to use “All” for In/Out ports so I would suggest setting just the MC6000/3000 mapping to dedicated ports.

Good to know my friend. Thanks for the help!

All ports means that SC-2000 device would also pick up other controller signals. In this case ensure that both controllers are sending messages in different MIDI channels.

Stewe, you would have fun with these - they have hardware modifiers not just for deck change but also for FX banks. I was planning on doing some smart fx mapping but I can’t seem to update myself to TP2 :smiley:

Hi,

Do you know why they need to use all ports? I have had a similar problem to the OP. I would now like to use 1 of my SC2000s for controlling deck C and D only, Would it be simple to make my own mapping for this?

Thanks