![]() ![]() You can add stuff to the mapping alright, but it's gonna be tricky. It selects fx2 as peak filter make it off It selects fxunit2 as group effect (all back to normal) It selects parameter3 on fx unit4 as 0.25 and offĭry/wet encoder controls only fx unit 4's dry/wet value When i press fx1on (while shift+fx3on is still on), ![]() It selects parameter3 on fx unit4 as 0.5 and off When i press fx2on (while shift+fx3on is still on), It selects parameter3 on fx unit4 as 0.9 and off It selects parameter2 on fx unit4 as 0.5 and on It selects parameter1 on fx unit4 as 0.6 and off It selects fxunit4 as single effect as delay and makes it on ![]() When i press fx3on (while shift+fx3on is still on), It selects fx3 as ice verb and make it onĭry/wet encoder controls either dry/wet value and all 3 effect knobs with same rate till 100% It selects fx2 as peak filter and make it on Shift+fx2onbutton sets modifier#2 to 1 / shift+fx2onbutton sets modifier#2 to 0 There is modifier#2 and shift+fx3onbutton sets modifier#2 to 2 /shift+fx3onbutton sets modifier#2 to 0 There is modifier#1 and holding shift sets modifier#1 to 1 When you have the LED's lit up, what function do you want them to have? This leads to 7 usable states per modifier.Įxample, imagine that “7” is the locked state.Ok. Ie, that the second modifier is being used to extend the states. In this case, use 2 modifiers with a reserved state that means “locked”. So the only way How to add more than 8 states ¶Īnother trick: what to do if you need >8 states? and there is no “OR” operation in traktor. Second, this trick leads to massive duplication on regular entries, because now actions that depend on the jog being pressed means "2" or "3". Plus you also need to add conditionals to all events. In this case you have to map the whole state machine explicitly, by separating presses (AKA direct) and releases (AKA invert). This no longer works with "hold" commands. The way to fix this is to map all combinations that might happen: Worse, of you then release the shift while still pressing the jog, you now forget that the jog is still being pressed! Only the last state is remembered.Įxample: If you press shift and then press the jog, you would forget that the shift is pressed. The issue is that this doesn't work for dependent events. If the events are independent, you could share the modifier trivially by holding different values as follows: In this example you would effectively waste 12 states. * M2=“jog pressed” (0=not pressed 1=pressed) * M1=“shift pressed” (0=not pressed 1=pressed) Typically you use one modifier per event you want tracked, with interaction "hold". How to share modifiers by holding multiple states of different buttons ¶ The remaining of this section explains how to go around these limitations. * extra MIDI pages make your preferences window slow. * modifiers remain local per page - there are no global modifiers However, this has the following implications: If you run out of modifiers you could get 8 more by just creating another page. Twisted Gratification: ( newer version)Īlso very relevant are Mods that change the controller screens and gives more features:Īnother good indicator is the list of most downloaded mappings (click "Downloads" to sort):Įach page has 8 local modifiers.These are the most complete mappings I've seen, which extend significantly Traktor with a lot of useful features. Twister Insta MixerFX: Midi Fighter Twister Insta Mixer FX (TPro3).If you are experienced, these are useful "standarized building blocks" to add to your own mappings. These are excellent to learn mapping without getting an avalanche of thousands of unrelated entries. TBD: List of single feature MIDI mappings ¶īelow is a list of mappings that showcase a single isolated feature. Rekordbox BOME emulation of jogwheels:.The second part of this section is are self-contained demos of Advanced tricks: Most of these refer to the limitations of modifiers. This section covers tutorials and advanced mapping tricks. What are demos of advanced mapping tricksĠ) Browse List or Tree (like rekordbox or Serato) How to share modifiers by holding multiple states of different buttons ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |