F1 Custom Mapping

Dear All,

I recently decided to play around a bit with making my own custom mapping of the F1 controller for Traktor!

I think it's a great little thing to have for mobility reasons like taking your stuff to a park and having a small mix on the go .
I found some nice mappings available but none really suit my needs 100% so I want to create it myself.

I have been able to create a new mapping sheet with the commands i want to use, but I've noticed that some of the buttons are also mapped to do other things too... I assume they come from a different mapping which is also stored on my computer and both mappings are active (as an example I mapped one of the top filter nobs to be my channel A high EQ nob, but it seems that in midi mode it is also mapped to channel A filter... so the moment I adjust the this nob the high EQ gets adjusted at the same time as the filter nob :/ not ideal).

Should I somehow just delete the other mapping, and if yes, where ?

Thanks in advance for any tips !! and happy mixing!

Kuba

 

Hello and welcome.

You have two ways to achieve what you want:

- use the default mapping and overwrite its commands (so only one mapping works). It can be a full new version or accommodate for some changes you may want/need in the F1's workflow.
- use another layer (two options here either the 'user' layer that uses the same kind of protocol/messages than the original mapping, or the midi mode..using midi messages). In this case you can switch easily between the 'factory/basic' mapping and your custom one. Note that even in this case you can still modify the factory mapping if you feel like it.

How?
- to modify or completely change the factory/default mapping, go to Traktor's preferences, controller manager and in the drop down menu of your devices you'll find a F1 default mapping. Select it. You'll see it is empty. Actually it isn't, it's just that you don't see the commands. To modify anything, you just need to create new commands and use the override option available. Your new command will sit (and 'hide') upon the existing one. You can also add commands to what's existing without using the override option, in this case the original one and the new one(s) will exist together.
Be careful if you overwrite a command you may want to think ahead about any additional layers your control can have (shift commands and the like).
- to use a user or midi mapping. First you need to tell your F1 which one to use by default (you can't have the two at the same time). Go to your preferences and there's a F1's tab there. In the options you can change either user or midi mode. Then you just create the appropriate one. And you access/switch to it from the default mapping just by pressing shift+browse.

Hope it's clear for you. There are a lot more details about mapping (user or midi) that I can't covert here but I hope it will put you on the right path.
Take care.