Traktor 1.2.7 - map faders to buttons on launchpad mini
Results 1 to 7 of 7
  1. #1

    Default Traktor 1.2.7 - map faders to buttons on launchpad mini

    hi there,

    i want to do the following: map faders (filter, fx-dry/wet) to buttons on the launchpad mini. it should work the way it does in ableton: slide up and down a row of buttons to move the fader including led feedback.
    iīve been searching the web and different forums, but canīt find a solution. can anybody hepl me?
    - iīm still on traktor scratch pro 1.2.7 btw

    regards, daswadan

  2. #2

    Default

    *bump*

    no one? seriously?

    i found various mappings in which a fader or a rotary is mapped to the buttons of the launchpad. unfortunately, these mappings donīt suit my needs.
    so can nobody explain to me how i map a fader or a rotary in traktor to a row of buttons on the launchpad?

  3. #3
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    Should be fairly simple task...

    Add the command you want > Midi Learn the button > change type of controller in to the 'Button' > set interaction mode to 'DEC' > adjust resolution to your likings (check 'Auto Repeat' box if you wish to adjust the parameter by holding down the button)

    Now duplicate this entry and repeat all from the example above - just ensure to set interaction to 'INC' this time.

  4. #4

    Default

    first of all, thx for your awnser. but this is not what i want to achieve. if i map it your way, i would have a fader mapped to just 2 buttons (increase / decrease). what i want to do is to map a fader to a complete row of 8 buttons. sliding the finger over the buttons should increase / decrease the value of the fader.

    i know this is possible, already saw videos of it. i just donīt know how to map it.

  5. #5
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    OK - I miss understand you. You should than make a direct button action. (you hit the button which sets some specific knob value)

    I've made one real quickly for anybody interested in this subject. Press 1 to 8 on your keyboard to adjust Deck A volume in steps. You can look right into it and see how I did it.

    Volume_Pads.zip

  6. #6

    Default

    thank you.

    2 questions left: is it possible to map smaller incriments than 0.200 to the buttons? and how do i get proper led feedback?
    what i want to do is, when i open the fader (press the buttons one after the other) the pads light up. when i close the fader, the pads turn dark again. and when i open the fader directly by hitting the fourth or fifth pad, all pads underneath light up immediately. like a "fader of light"

    - sorry, not a native speaker, i hope one can understand what i mean.

  7. #7
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    1) Sure thing - you can tweak the direct value in each pad command for what ever amount you wish.
    2) We'll need some modifiers for this - if you're not comfortable with them just do a quick google search on 'Modifier Basics'

    Going up to bottom they should be set as following:

    Button 7: M=7
    Button 6: M=6
    Button 5: M=5
    Button 4: M=4
    Button 3: M=3
    Button 2: M=2
    Button 1: M=1
    Button 0: M=0

    Then use actual Modifier Output command to display current volume fader position.


    Button 7: when M=0 / controller range is 0-7 / no color
    Button 6: when M=0 / controller range is 0-7 / no color
    Button 5: when M=0 / controller range is 0-7 / no color
    Button 4: when M=0 / controller range is 0-7 / no color
    Button 3: when M=0 / controller range is 0-7 / no color
    Button 2: when M=0 / controller range is 0-7 / no color
    Button 1: when M=0 / controller range is 0-7 / no color
    Button 0: when M=0 / controller range is 0-7 / no color

    Button 7: when M=1 / controller range is 0-7 / green
    Button 6: when M=1 / controller range is 0-7 / green
    Button 5: when M=1 / controller range is 0-7 / no color
    Button 4: when M=1 / controller range is 0-7 / no color
    Button 3: when M=1 / controller range is 0-7 / no color
    Button 2: when M=1 / controller range is 0-7 / no color
    Button 1: when M=1 / controller range is 0-7 / no color
    Button 0: when M=1 / controller range is 0-7 / no color

    Button 7: when M=2 / controller range is 0-7 / green
    Button 6: when M=2 / controller range is 0-7 / green
    Button 5: when M=2 / controller range is 0-7 / green
    Button 4: when M=2 / controller range is 0-7 / no color
    Button 3: when M=2 / controller range is 0-7 / no color
    Button 2: when M=2 / controller range is 0-7 / no color
    Button 1: when M=2 / controller range is 0-7 / no color
    Button 0: when M=2 / controller range is 0-7 / no color

    Button 7: when M=3 / controller range is 0-7 / green
    Button 6: when M=3 / controller range is 0-7 / green
    Button 5: when M=3 / controller range is 0-7 / green
    Button 4: when M=3 / controller range is 0-7 / green
    Button 3: when M=3 / controller range is 0-7 / no color
    Button 2: when M=3 / controller range is 0-7 / no color
    Button 1: when M=3 / controller range is 0-7 / no color
    Button 0: when M=3 / controller range is 0-7 / no color

    Button 7: when M=4 / controller range is 0-7 / green
    Button 6: when M=4 / controller range is 0-7 / green
    Button 5: when M=4 / controller range is 0-7 / green
    Button 4: when M=4 / controller range is 0-7 / green
    Button 3: when M=4 / controller range is 0-7 / green
    Button 2: when M=4 / controller range is 0-7 / no color
    Button 1: when M=4 / controller range is 0-7 / no color
    Button 0: when M=4 / controller range is 0-7 / no color

    Button 7: when M=5 / controller range is 0-7 / green
    Button 6: when M=5 / controller range is 0-7 / green
    Button 5: when M=5 / controller range is 0-7 / green
    Button 4: when M=5 / controller range is 0-7 / green
    Button 3: when M=5 / controller range is 0-7 / green
    Button 2: when M=5 / controller range is 0-7 / green
    Button 1: when M=5 / controller range is 0-7 / no color
    Button 0: when M=5 / controller range is 0-7 / no color

    Button 7: when M=6 / controller range is 0-7 / green
    Button 6: when M=6 / controller range is 0-7 / green
    Button 5: when M=6 / controller range is 0-7 / green
    Button 4: when M=6 / controller range is 0-7 / green
    Button 3: when M=6 / controller range is 0-7 / green
    Button 2: when M=6 / controller range is 0-7 / green
    Button 1: when M=6 / controller range is 0-7 / green
    Button 0: when M=6 / controller range is 0-7 / no color

    Button 7: when M=7 / controller range is 0-7 / green
    Button 6: when M=7 / controller range is 0-7 / green
    Button 5: when M=7 / controller range is 0-7 / green
    Button 4: when M=7 / controller range is 0-7 / green
    Button 3: when M=7 / controller range is 0-7 / green
    Button 2: when M=7 / controller range is 0-7 / green
    Button 1: when M=7 / controller range is 0-7 / green
    Button 0: when M=7 / controller range is 0-7 / green

    Here's the .tsi that you can learn/build from - made it on my BASE controller but all commands has it's comments to help you track the buttons.. hopefully you'll be good to re-map a whole thing.

    vol_pad_LED.zip

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •