You can’t replace commands (not exactly see below) if you use the embedded mapping. You don’t really “overrides”.
So if you’re using a user traktor s4 mapping either you build it from scratch, or use the default one provided in your files; or you use the embedded one.
Using a full user mapping implies to have erased from your controller manager the embedded one.
That’s the generic thinking, however there are some possibilities to twist the embedded one, twisting only, not really being able to fully customize it.
I’ll suggest to have a look at the Traktor’s bible site, there’s good inspiration there.
-
there are some controls that may not be in use, like when you’re using 4 fx units, each one being assigned to one channel: 4 of the channel fx assign buttons not being in use anymore. A good spot for putting a low kill for example. You’ll find at the Traktor Bible 's site a small mapping allowing to reassign the fx units if you prefer (by the way the leds will not work so I don’t think it is a good idea).
-
some controls can be twisted:
(*)like the sensitivity of the jog wheel for example. You think the jogwheel is a bit slow when used as a control for controlling filters? Just add a new user traktor mapping, create an on/off modifier which will be the load buttons for the S4 (the one that engages the use as a control for the filter), be sure it equals one when the load button is lit on the hardware, add a new command managing the filter setting with a new sensitivity. One will add around 25% sensitivity with the settings of the encoder to 300%/100%.
On the contrary if you don’t like the gain encoders (hardware) as gain encoders and want to use them for something else you can add a function for gain control and you’ll bet the encoder to settings 0%/0% as that should stop the encoder (hardware) from moving the encoder (software from moving).
(*)You can add or remove controls on some circumstances. I’ve talked about the jogwheel used for filter and how by creating the same modifier you could change the sensitivity, but that applies too when you use it for FX: let’s say you prefer to control the first fx in the group mode and the second and may be the third but without changing its setting. And all that with engaging the FX themselves. That’s feasible by creating the corresponding modifier from your hardware (in this case the load button) in a user mapping. The rest is classical mapping.
For the jogwheel(s) as they react to the browse mode (which is a modifier) you also to create a modifier that would reflect that state too. Think that your modifier(s) and the hardware/software must be ‘synchronised’ (like when load is lit your modifier equals one in your mapping.
*For the jogwheel(s) as they react to the browse mode (which is a modifier) you need also to create a modifier that would reflect that state too. Think also that your modifier(s) and the hardware/software must be ‘synchronised’ (like when load is lit your modifier equals one in your mapping.
But I’m going to use my own perception here as I’ve been mapping this thing since two week extensively and studied it a bit. The embedded mapping is a thing of beauty, it’s quite well thought (not perfect) and gives you on the hardware a lot of information coming from the led feedback, without even speaking of the loop length screen that is a bless to have really.
You won’t come any close to reflecting the embedded mapping. You’ll loose a lot of details and a lot of information. So you’ll really have to question yourself about the compromise you’re going to have to make if you want a pure custom mapping. But that’s a matter of personal preference really but at least for me, made me think a lot about it.
One thing to note is you’re not obliged to use midi to do a custom mapping but that implies two things:
- you won’t be able to map some functions on some controls: you can’t use a fader as a button setting like in Traktor, the controller manager will tell you the control being inappropriate. So no fader engaging a FX like in ‘juggle’ (you can find different ways, but not with a fader or a knob).
- the embedded mapping(not the default user one) is very complex to reproduce, very (or in this case, trying to get near it). Especially because each deck ‘layer’ use the same one as its duplicate (a&c; b&d) so any mapping would involve a lot of modifiers and/or will obliged to create several devices to manage the modifiers available (for more advanced power users)
The middle way towards customizing is twisting the embedded mapping with the tips I explained above. You get the benefits of the embedded mapping and twist it here and there. But, you’ll get frustrated because more than often you’ll realize that you are limited even with the options offered, the nicest one being to change how to work with the fx with the jog.
Another way is to use the default user mapping as a base, study it to learn the modifier system, to learn about some new functions and how they are used (always some info in there). I think that’s the best start to custom map the unit especially when you/we/I at the starting point of the learning curve of this unit.
I did that, erased some functions I didn’t like, created new ones, studied a part so I could reproduce it by in my own way, etc… BUT, man, I really miss all the smart details the embedded mapping gave me.
Lastly there’s still the possibility to switch the unit into midi mode, and then you can do what you want, you’re just restrained by what the controller manager offers and your scheming. Actually it can be good idea to create a full juggle mode: you use the embedded mapping and enjoy all it has to offer and switch to midi mode for some fun time (juggle mode, fader Fx, superknobs, whatever). You can duplicate some functions and visual feedback so you’re not lost when passing to midi mode like the channel volumes, etc. The switch from HID to midi mode being easily done and already previewed on the S4 by pressing shift + browse mode.
A final word:
the Traktor S4 combo has really been thought to be used as two decks and two sample decks. That even makes you think of the need to have 4 decks as track decks available, bearing in mind you have almost another source with the loop recorder.
NI’s just offered us a really good controller but also a good bucket of creativity with the software combo.
