Mapping wishes

Toltemic

• These are my wishes and thoughts for every time I've come across a hurdle within mapping the rane a trak (70) so these ideas and requests are more focused on the DVS & mapping community considering dj hardware has gotten considerably more advanced since 2013.

Traktor Mapping framework wishes:

• All modifiers now have a null state option- A '-1' / null option for modifiers would be a god send due to most hardware having 8 pads. But because, I imagine, the use of 3bits only limits to 8 values, it would be near impossible to implement more modifier values. however I think formally utilising fader button glitch as an actual defined null state would help

my use case- nearly all controllers use 8 pads for input, but having a 'no input state' means you need 9 values, so currently you end up using 2 global modifiers. Which means you have to do a whole song and dance with commands to play nicely if you're sharing that extra modifier for your 9th value.

• Shift is its own dedicated modifier outside of global modifiers , Shift is universal across many controllers and to reflect that I think shift should have its own modifier status, this is to be more user friendly with new mappers. You can now have toggleable option within mapping gui similar to invert.

Having shift natively change the output midi commands on the rane mixer helped me have an extra modifier choice and allowed me to do a lot more within my mapping.

• Multiple, contained mapping, GUI. I think this will be a better answer for more modifiers and better mapping organisation. You can now have multiple mappings as modules and they can be turned on and off, you can visually see all the modifiers- you have an expand arrow that'll let you edit that specific TSI mapping file. On top of that you have a universal modifier table for auto control on turning on/off mapping modules. This can also enable user defined options similar to preferences under Traktors in house controllers

• button delay option, just a couple of ms delay would do wonders for modifier condition checks. This seems to already work with output. However due to output check, would be happening on the same cycle

• fader/knob now has 'zoned' option this works similar to how you'd set a fader to button mode and hold. But this wish has the same GUI of output for better control- so you can set your max value and min value with 1-127 being where the max/min zone is set

• Direct mappable control over TSI global focus, most controllers are now 4 decks with deck A & B using the same physical buttons, With mapping nearly all features per deck you need to have multiple mappings but this is becomes a big issue as you'll need to have the mapping copied 4 times for each deck letter, and like what I've done with my rane mapping possibly ~4 mapping per deck which leads to 16 TSI's in total, this can be halved by having direct control with which deck the tsi is focused on. Traktors internal focus only does 1 deck which is too limiting. This all need a new assignable (like device target) called TSI target.

• Blink Led, instead of hackly using beat phase for extra visual information, it would be more user friendly to have it as a option. My immediate thoughts is to have 2 drop down menus under min and max with the options- Solid, Slow, Fast, pulse (fast momentary blinking flash). This will give you a new defined parameter which is min crest and min trough as well as max crest and max trough. This new defined parameter is only usable if selected on an animated option.

• a 'direct' auto repeat / knob/ encoder resolution - The traktor defined resolution works in percentages, this doesn't universally work, especially with bpm- I think having the user also define what the parameter jump is is more friendly than having' ÷ 8'

• Mapped button presses can be quantised in mapping editor. In the button GUI you now have a quantised option, when turning on quant within traktor, it will also affect quantised selected mapped buttons, useful for keyboard play for example

• Time code signal control as a Control type This may be quite complex to add but my idea is that traktor has a new interaction that you map to physical button that acts as an 'activate timecode control'. This will sets a hidden cue from the point a physical button is pressed, and uses a hidden 'seek position' value to translate into a an encoder value.

• A new output like LED option called user modifier - take for example loop select division- this is already a defined attribute on select and set loop with -1 - 11, this can possibly work as a modifier. Basically sends the led value internally and the condition checks against it. This will open up mapping to a lot of new modifiers conditions. Such as: is Quant on, is snap on, Is keylock on, Is flux on, is freeze on, is deck in abs, rel, int, hap

Additional inputs and outputs wishes, these are options that don't exist even if user modifiers using output is implemented:

• Direct cell play type in (oneshot and loop) instead of slot. The cell can in traktor can be independently be set to one-shot/loop, so having the cell only be changed whilst active in a slot is limiting

• Is Key Modifier, this sends the tracks key out, great for visualisation on a deck basis

• Capture type, can choose to capture a loop as a loop or oneshot upon capture and sent to remix deck

• Cell colour, set colour for input, 0-15 (min/max) for output per cell the user will have to define the rgb like with hotcue out. I know this will end up being 16x4x64 possible commands to display all cells, but that's just traktor mapping, stuff is just tedious

• Stem Slot Colour, Similar to above

• Select column in 1- to however many in playlist/browser, basically a hardware control for playlist organisation, but works universal to however the user has placed their columns similar to fx output 0-47

• direct select column in playlist/browser, similar to above but is irrespective of user layout

• global tempo clock out as a beat phase, a beat phase that's always on

• Set deck bpm, Similar to set master clock out, this allows users to not work with tempo percentages to set bpm, and similar to set master tempo, the out is 0-300 as controller range, allowing users to send out post tempo fader bpm information

• Direct Cue select, a better way of interacting, silently, with cue points

• Cue Trigger, only triggers floating cue. Cue place isn't needed as its already accessible using loop cue in place

• Deck swap, retains play head and is in play, like what duplicate does, useful for single deck play

• Direct Tempo Adjust, 0% to %1500

External Audio Wishes:

• 5 fx send and returns, 4 for per deck channel, 1 for external, mixers are now starting to support having an internal send & return for mixing software effects post fader, and this would be great if it's supported in traktor

• Post fader EXT option, With the addition of above, due to latency a new type of fx routing will need to be added, this has no audio pass through when off, and wet dry becomes post fx level. The module will always be set to 100% wet.

• fx now now has a default locked preferred routing, in effects options you now have the option to define what routing the effect upon loading will be set to (only on single mode). So for example you can set delays and reverbs to, when loading in, postfader routing. Or have beatmasher, slicer set the module to pre fader.

• loop recorder has an internal mode on external mixing, on external mixer mode and can use deck input like audio recorder when set to external mode

New additions for mapping and utility:

• hidden mappable gliss or cue amp env attack will help smooth key play

• volume faders still work on external mixing mode, useful for temporary muting with a hard limit decibel limit unlike gain

• Flux and DVS I get why flux doesn't make sense on timecode absolute but I think it can still be implemented when in relative mode, I think if the blue play head switches to internal play back whilst the red stays on timecode whilst is flux on- it can be implemented. Tempo for the blue head should continue with last tempo recorded/set on press. I'm assuming flux uses the blue play head to show the true position which you have a control vinyl, and that code was used for flux in internal playback, so maybe an internal play back play head would be necessary for this to work (green?)

• battle style monitor (headphones) cueing- there's no support, mainly channel mix and split cue. I think a headphone cue level & pan monitor submix per channel would solve this.

• better explanations in the controller part of the manual, literally had research old djtechtools forums from 2014 to find information about certain features

• Preview has per deck audio routing

• remix files have a defined preferred deck to load to when using load from list command

• per deck quick store buffer similar to preview but at deck level so if you load a remix deck from list you can swap back, this is basically to enable scratch bank, as well as deck swapping

• Last loaded track is stored per deck when changing deck flavour for quick loading

• Last load track per deck

I think mapping is a powerful tool which the community has held up quite highly but commands are starting to get quite complex and trying to cram everything within 2025's standardised controller performance features- it's becoming considerably more difficult or near impossible, but what's more frustrating is that most of these features are just previous settings and parameters repackaged for performance which is great for traktor mapping because of the advance control of said parameters. For example scratch bank, that can be done with remix deck, however there's no way to quickly reload the previous track, hindering its implementation. And then there's the sheer amount of commands you need to control 4 decks and 1 TSI just will not cut it. Multiple TSIs, in a ZIP package- you can already do that but it's just getting them all to follow user input ends up reserving a lot of modifiers. I am coming from mapping a limited control surface in terms of available buttons and input, whilst on top of that having limited control over audio due to being in external mixing mode, so my wishes are niche of niche

Sûlherokhh

I want all of it.

But i would already be satisfied with twice the number of modifiers with 4bit (hex) value range instead of 3bit, so values 0-15. This would make all mappings so much easier.

Stevan

I'm just happy to see somebody think about Controller Manager updates. Thank you!
TRAKTOR team doesn't care about this just so you know to not hold your breath. I've been talking about these kind of updates for more than a decade. We can't even have thrd modifier condition - which would be a single most useful addition.

Toltemic

There's probably a deep fear of breaking the mapping system if its played around with too much 😁

Really, I if had to choose 1 feature from this niche list, it would be the multiple contained mapping gui + universal modifiers for communication between tsi's, as it would introduce a more modular system, than trying to get everything with in one tsi file. This would in theory alleviate global modifiers to one specific feature, which in turn would allow modifiers to affect, now available, modifiers to work around the 2 condition limit- the only problem now is that I have to wake up from this dream