Tip for mapping modifiers

When mapping modifiers I noticed that a times the mods would get stuck on, kind of a random thing. Not sure if anyone else has noticed this....
But the tip I have is to map all modifiers to a reset button(basically map them all to hold and off(0).

On the s4 I set all in each mapping to a usbthru switch on the back.
So at the start of mixing I just flip it and all mods are set to off.
Hope it makes sense.

Another tip, if I can explain this?

Is if you map one modifier to increments.
You can map it with one button to increase only the number you want,

example
1. modifier 1 set to inc.

2.(same button) modifier 1 set to hold and "0"
add modifier to this m1=3

this example would only let the modifier increase to 3 and the reset to "0"

the point of this would keep track of an increment and only use the modifier states you want for the functions you want, without going past and losing track.
I never would use all states and sometimes only have one button open.

maybe this will help someone

 

Mods are fun stuff! Let's keep this thread alive by frequently posting tips.

The stuff I'm going to write below is highly theoretical. The example I set forth is not a recommendation for practical application, but just to give you an idea.

Suppose you were using a Modifier to change the layers of a drum pad. When M1=1, it does an entirely different set of things than when M1=0. Maybe load a whole new set of one shot samples.

You found this very useful and continued adding layers, and you finally reach your 8th layer; modifier value =7.

What you might do is to start using another modifier, M2=1, 2, 3...etc...

However, if you have the same pad to do different things at M1=1 and M2=1, you can have a conflict when the respective modifier conditions are just those.

You maybe inclined to tackle this situation by adding Modifier conditions to the "Newer" mappings. For example, you can add in the Modifier conditions; M1=7 and M2=0, M1=7 and M2=1, etc.... but since you get a unique combination for all the other values of M1, here's the time to tidy up and prepare for the next level of layer paradise. Go back to all the mappings of the previous layers and add a second Modifier condition, M2=0. Now that you've exhausted all 8 possible layers of M2=0, you can move on to M2=1, then to M2=2...all the way up to your 64th layer at M2=7 and M1=7.

Practical application... hmm... One I can think of is, you and your buddies decide to do a live with just a laptop running Traktor, and you're on the pads. You can double the top left button in each layer as a one-shot load button to the sample deck for all the sample/loops of that layer. You can switch layers after each track or even during a track as you like, and go through your 64 layers during the gig. This should last you quite a bit, and you won't even have to be near the PC, making the audience wonder what model your pad-sampler is. It's actually just a midi controller.

 

doraemon

I am actually quite new to mapping with modifiers.

I have made a few mappings separate using, well reusing the same modifiers,

Question? I notice no conflicts doing this it seems each map and modifiers reads as its own.
Is this true or am I just waiting for disaster.
The main reason I keep small separate mappings is to avoid confusion, so I hope this is a good way to go about this.

The main reason i learned about shortening the lengh of the mod increments and reset to zero was to give a small controller layers but not have to scroll through too far. I could use two buttons but I already had the thing full.
Also could solve an issue of finding what mod someone is in 123 is easier than 1234567. with one button for sure.

Have you had issues with the mod change stuck to value of '1' . when starting up. I solved my issue with my reset map but all I could think of is that I saved the maps I was creating while in mod states other than "0".

 

It really depends. One reason why you can get away with being less than careful with modifiers is because usually most people set no modifier conditions to the default behaviors of the button, and use a "HOLD" interaction with Modifiers on a need-to basis.

One thing you can count on, though, is that a Modifier value can only be one value at a time.

Suppose you had a M1=0,1,2 toggle for one of your effects, and you set up a shift button that shifts M1 to 3 (HOLD) and back to 0 to double the CUE button to act as the SYNC button when shifted.

You would always get the SYNC right because you're pushing the shift button, and you'll always get something (0,1, or 2) out of the effects because you won't be pushing the shift button at that time. But one day, you might be holding the shift button for some reason and trying to use the effect at the same time... too bad, nothing happens with the effects when M1=3.

This example is too obvious but the important thing is, again, that a Modifier can only be one value at a time, so you just have to watch out when you have a lot of modifiers so you don't change an important modifier's value without knowing.

 

Yep I guess with separate maps you can use the same modifier value over and over? Right?

 

If you mean separate buttons and faders etc.. in a single .tsi, I am saying that you can, but you want to be careful because it can cause trouble. I wouldn't say can to someone just starting to map. That's like saying you can cross the street when the light is red to a child.

 

Ok I get what you mean about a mod value only able to be as ot is.
I geuss what confuses me is if I use the modifiers (lets say m1) in separate mappings when using the controller editor. I have checked to see if they show a change by looking at the modifier states in the editor.
They only change for the mapping shown. Thats why I thought the maps read as individual settings. But what you say makes more sense to me.

 

Can someone please explain to me how the "condition2" in control manager? I have used condition1 but I'm trying to grasp the concept of using the condition2 in control manager.

 

It's a IF Condition 1 AND Condition 2 statement, so would let you do something only if two modifier states were active.

An example of this could be one button to toggle on M1=1 and another button needs to be held down while you press the final button for the actual action. I suppose using an FX slot a particular way is an example - with one modifier enabled when pressing the FX On button and then pressing SHIFT to enable the second modifier and finally turning the FX knob uses these conditions to do something else (maybe filter?).

 

Thanks tmccoy!

Since I'm as dumb as a door nail, it took me a little bit of time before your explanation sank in. I did a bit of reading and hands on testing. But now I actually know what you mean.

So basically if "A" button is setup to trigger a modifier state in M1 and M2 I can use the "condition2" in control manager. So for example I want PAD1 to load a track in the remix deck and the condition1 and condition2 is setup like M1=7, M2=7 then I have to setup button "A" so when pressed the modifier state will have M1 and M2 have a value of 7.

WOW! that just opened up more world of options for me. I'm trying to setup the Pioneer DDJ-SR's "SAMPLE" button and I was going nuts trying to figure out what and how to get more options. After reading your reply and another article on it, it flicked a switch in my head of how the modifiers cond1 and cond2 work. I can setup cond1 easily but I was struggling to understand using cond2 before. So thank you for taking time to explain it to me. Much appreciated!

 

I don't think that explanation quite describes how you can use it - although it might just be the way you are writing it and you might have already figured it out. I think the example of the pad is a good one with the DDJ SR, where you have the pad function select buttons above the 2x4 pads. So if you press the SAMPLER button, you could set M1=7, which you can now use to identify a "remix mode". Then you could map another button to be a "capture" mode button and set say M2=8.

Then you create a new mapping for the function of say "capture remix slot" on the press of the first of the 2x4 cells and use the modifier conditions M1=7 M2=8. Then only if you have first pressed the SAMPLER button (to enable your "remix mode") and then your chosen "capture mode" button will pressing the 2x4 pad actually capture.

 

following