1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE
NOTICE:

Our Traktor Pro Public Beta is available again in our new online community. Join us if you want to try new features.

MORE INFO

Modifier compression - a technique for saving modifiers

Discussion in 'TRAKTOR PRO / TRAKTOR SCRATCH PRO' started by dalgard, Sep 26, 2009.

Thread Status:
Not open for further replies.
  1. dalgard

    dalgard Forum Member

    Messages:
    47
    If one were to try and map every feature of Traktor to some midi device, Traktor Pro would have a fatal lack of modifiers. And even with normal use, I find that there's not nearly enough. This is a bit puzzling since one would image that having 8 or 16 wouldn't really make a difference programming-wise.

    Anyway, I've come up with a method of saving modifiers, which I call modifier compression. It requires creating the double amount of midi rules for functionality (and a bit more for assigning modifiers), but it will be worth it in a tight spot. It is a bit difficult to explain, so please beer with me...

    Modifier compression works by using one modifier instead of two for purposes where modifiers have three states or less. The following chart explains the case of only two states, but can be extended (or combined) once the principle is understood; I have put the assignments that must be created below.

    - - | 0
    A - | 1
    - B | 2
    A B | 3

    On press shift-A if mod# equals 0 set mod# to 1
    On press shift-A if mod# equals 2 set mod# to 3
    On press shift-B if mod# equals 0 set mod# to 2
    On press shift-B if mod# equals 1 set mod# to 3


    With these rules the state of the "other" button is carried on, in a way. If the modifier-buttons work more like CAPS LOCK than like SHIFT, the reverse rules must also be created. After this is set up, two rules - which will never be met at the same time - must be created for each function:

    On press A if mod# equals 1 do x
    On press A if mod# equals 3 do x
    On press B if mod# equals 2 do y
    On press B if mod# equals 3 do y



    The above may contain a slip of mind or two, I hope you get the picture ;) It works like a charm (I have used it for remembering the loop in/out states of four decks using mod7 and mod8 only).

    Enjoy,

    Kris


    P.S. Below is the chart for three states - notice how all possible states is represented. Be advised, though, that the amount of modifier assignment rules that needs to be created for making this work has increased dramatically.

    -- -- | 0
    A1 -- | 1
    A2 -- | 2
    -- B1 | 3
    A1 B1 | 4
    A2 B1 | 5
    -- B2 | 6
    A1 B2 | 7
    A2 B2 | 8
     
  2. rainerh

    rainerh Well-Known Member

    Messages:
    2,465
  3. dalgard

    dalgard Forum Member

    Messages:
    47
    That is really not anything similar at all... But thanks ;)
    ---
    Forgot to mention, the technique can also be used to fit three two-state modifiers into one (something that is rarely of any use, though):

    - - - | 0
    A - - | 1
    - B - | 2
    A B - | 3
    - - C | 4
    A - C | 5
    - B C | 6
    A B C | 7
     
Thread Status:
Not open for further replies.