Mapping w/ modifiers

jakesmith0610

Hello,

I've recently begun to attempt live sample chopping with four decks.

Previously, I've had the stems mapped to my 4 FX unit buttons/knobs (forgoing the usual effects), with the buttons mapped to the mute function and knobs for stem volume. I have two FX units on either side of the board. Naturally, applying the same mapping to decks C/D affects A/B as well. In other words, if I were to turn the vocals off for deck A then the vocals for deck C would be cut.

Here is what the unit looks like.

My ideal situation is that when I press the "mode" button, the stem mapping switches from deck a to deck c (or b to d on the other FX unit). I would assume that this requires me to add a modifier condition to the mode button, but I am unsure of how to approach that.

Any help would be appreciated,

Jake

Stevan

You need only two toggle type modifiers - on for each side. The following is example for one deck using Modifier 1.

Add In → Modifier → Modifier 1

Type = Button; Interaction = Direct; Condition = 0, Value = 1

Now duplicate that command and just swap the condition and value.

Type = Button; Interaction = Direct; Condition = 1, Value = 0

If you did this correctly then you will notice that the condition display indicates values 0 and 1 each time you press the button.

In this mapping scenario the value 0 is representing Deck A and value 1 is representing your deck C.

Stevan

You need only two toggle type modifiers - on for each side. The following is example for one deck using Modifier 1.

Add In → Modifier → Modifier 1

Type = Button; Interaction = Direct; Condition = 0, Value = 1

Now duplicate that command and just swap the condition and value.

Type = Button; Interaction = Direct; Condition = 1, Value = 0

If you did this correctly then you will notice that the condition display indicates values 0 and 1 each time you press the button.

In this mapping scenario the value 0 is representing Deck A and value 1 is representing your deck C.

jakesmith0610

The modifier works, thank you. I'm having a bit of trouble figuring out how to distinguish the commands, however.

When the condition is set to zero, the controls work for deck A, which is exactly what I want. When the state is set to 1, both A and C stems are controlled. I'm just missing something.

Here's how I set it up with the modifiers, thinking that when M1=1 only deck C would be affected. Below is how Modifier #1 is set up, I believe it is correct.

Thank you for all your help.

Sûlherokhh

This looks exactly right. Do you have a second mapping for the controller in the list?

jakesmith0610

I don't believe so, I just went through and checked. However, I'll leave a link to screenshots of my whole mapping if you'd like to take a look.

A lot of the mappings are overwritten and I haven't taken the time to clean them up yet.

https://drive.google.com/drive/folders/1dRhLShKiGbX-DQhWUu1171RGPWzZwUJG

I suspect it has something to do with some sort of logic gate issue.

Sûlherokhh

https://community.native-instruments.com/discussion/comment/220666#Comment_220666

Could you please just export the specific mapping (Edit… Export)? Then upload that specific TSI file.

jakesmith0610

stem4deck.tsi

Forgot I could do that lol.

Sûlherokhh

This one (orange box) needs M1=0.

Of course, since your mapping is not finished yet, you will have to delete the FX control assignments (not visible on screen) that use the same knobs/buttons. Otherwise the knobs/buttons will always (and additionally) control FX parameters in addition to the stem controls.

Sûlherokhh

https://community.native-instruments.com/discussion/comment/220670#Comment_220670

So, i just realized, you didn't EDIT→EXPORT. You used the big export button at the bottom. This exports ALL your mappings. Now i have this in my device dropdown menu:

As i wrote here:

https://community.native-instruments.com/discussion/comment/220663#Comment_220663

Well, you have many, many mappings in the list. Remove all duplicates, so that you have exactly ONE instance of every mapping you need. Otherwise ALL mapping assignments will trigger, even those of mappings which you did not modify.

You have to select each mapping separately, then press EDIT…→DELETE.

Now i have to do the same (sigh). The EDIT…→EXPORT way makes sure that you will only export a single mapping, so this that doesn't happen.

jakesmith0610

Definitely should have tried that one out. Here is the link to the mapping when exported from the edit menu.

stem4deck.tsi

I just saved it to the same place so it is under the same name.

Sûlherokhh

https://community.native-instruments.com/discussion/comment/220682#Comment_220682

First: delete your duplicates, man! :)

jakesmith0610

Frankly I dont understand why there are so many, it never was like this. But yes I will.

Sûlherokhh

When the condition is set to zero, the controls work for deck A, which is exactly what I want. When the state is set to 1, both A and C stems are controlled. I'm just missing something.

Duplicates are the main source of this kind of problem.

https://community.native-instruments.com/discussion/comment/220686#Comment_220686

And then test if your mapping now works as intended.

jakesmith0610

Ok cool, I'll try it out after the 5 years it's gonna take to delete them all hahahah.

Also, is there a way that I can keep the mapping saved to traktor? All these duplicates are probably due to me re-uploading the mapping each time I open the program.

Sûlherokhh

They stay in the list when you close Traktor. But you can export them to a safe location just to be sure, in case they disappear for whatever reason.

Stevan

https://community.native-instruments.com/discussion/comment/220686#Comment_220686

It is because you are just adding the same mapping over and over instead of using bigger import button at the bottom of preferences. It is designed to overwrite all existing mappings while importing the specific one.