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

Traktor Pro2 + Akai APC20 Problem!

Discussion in 'DJ Controllers' started by Skullee, Mar 14, 2013.

  1. Skullee

    Skullee New Member

    Messages:
    22
    Hi all :)
    Okay, so..i got Traktor Pro2 v1.0.3 i think it is, together with APC20 running on Mac OSX10.6.8.

    I have allready mapped everything that i want, but i am having some minor issues with it and since this was my first time ever mapping in traktor, i would like to start all over again with a totally fresh Generic midi mapping in traktor to see if i can get everything 100% and maybe do it even easier.

    The problem is..it wont let me start a new mapping!
    I tried to select Add generic midi and it showed up empty as it should, but it acts like if the midimapping i have allready made is still enabled! The LEDs are still on and everything works like if i have imported my allready made midi mapping.

    I would very much appreciate if any of you guys could help me out!
     
  2. solger

    solger NI Product Owner

    Messages:
    3,941
    The APC20 reacts to all midi-mappings, for which the in/out-port (in the Device Setup section of the controller manager) is set to the APC20.

    So simply go to your first mapping and set the in/out-port to NONE.

    If you want to get back to only use the first mapping again:
    o) mapping #1: set in/out-port to the APC20
    o) mapping #2: set in/out-port to NONE
     
  3. Skullee

    Skullee New Member

    Messages:
    22
    Oh, hmm..i have set both in and out to APC20 in the mapping i have done! Should i change them there? By going to my first midi mapping..do you then mean to just import the tsi file?

    EDIT:
    ah, okay..so..with the allready made mapping i keep the i/o as APC20, and when starting a new one i select NONE on i/o?
    I thought you had to select the i/o to APC20 no matter what when you´re gonna do midimapping?

    I don´t quite get why the i/o should not be set to APC20 on the new mapping!
     
  4. solger

    solger NI Product Owner

    Messages:
    3,941
    As example, let's say if you click in the Device box, you have the following entries:
    Generic Keyboard
    Generic Midi 1 (GM1)
    Generic Midi 2 (GM2)

    Now let's assume you have the in/out-port for both GM1 and GM2 set to the APC.
    THen the APC will respond to both mappings (the mapping in GM1 and GM2).
    So if you only want to use one mapping at a time, you only set the in/out-port to the APC20 for that one.

    The same principle applies when you use 2 midi-controllers:
    You can assign the in/out-port in GM1 to the APC and in GM2 to another midi-controller.
     
  5. Skullee

    Skullee New Member

    Messages:
    22
    Does that mean i can only have 2 different types of midi mapping with my apc ..or any other controller for that matter? Since you can only set i/o to None OR APC20? Sorry for my lack of knowledge and maybe stupid questions, i´m just trying to understand the basics and knowledge about this!
     
  6. solger

    solger NI Product Owner

    Messages:
    3,941
    Well, if you only have the APC20 connected, there might only be None or APC20 available in the in/out-port.

    If you use for instance more midi controllers (APC20, launchpad and a Nanokontrol), you would be able to choose the other midi controllers in the in/out-ports as well.

    So if you have, for instance, 3 mappings in your controller manager, you could assign the in/out-ports like this:
    mapping #1: APC
    mapping #2: launchpad
    mapping #3: nanokontrol
    ...

    So for each mapping you have in the controller manager, you select the appropriate in/out-port of your
    midi-controller. And each mapping itself (which can also be imported from/exported to a .TSI-mapping file) includes the midi-commands which maps the knobs, faders, etc... of your controller to the Traktor-functions.

    Hope this answers your question.

    You can also find some additional infos about that in the manual or check out the links in this thread: http://www.native-instruments.com/forum/showthread.php?t=190247
     
  7. Skullee

    Skullee New Member

    Messages:
    22
    Thanx a lot for the in depth replies man! I will try this out tomorrow..and hopefully it will work..if not i will probably nag a bit more on here :) Oh, and thanx for that link as well, very usefull indeed!
     
  8. Skullee

    Skullee New Member

    Messages:
    22
    Unfortunately it did not work! I have no idea why..but i tried and it failed...it still just worked like the mapping #1 is active!

    One question tho..i have saved the mapping as a tsi file..!
    Can i just delete the settings of the tsi file in the manager and start with a new mapping that way and save it as a new tsi file? That wont cause any problems with #1 mapping tsi file as long as i save the #2 mapping as something else (Name it differently). Right?
     
  9. solger

    solger NI Product Owner

    Messages:
    3,941
    Yeah, if you already have exported/saved your mapping to a .TSI-file (Edit -> Export) , you can delete it from the controller manager (Edit > delete) and start a new mapping (Add -> Generic MIDI)

    You can also change an existing mapping and export it to a new .TSI-file (with a different name).

    If you want to go back to use other mappings, you can simply load the TSI you like (Add -> Import) and
    o) export/delete the other mappings or
    o) set the ports to NONE for the ones you are not using.
    ------------------------------------------------
    So basically you have two options:

    (1) Like in my post above, if you have more than one mapping-file for the APC loaded in the controller manager, simply set the in/out-ports of the other (not used) APC-mappings to NONE.

    (2) only keep one mapping for the APC in the controller manager (and export+delete the ones you don't use)

    The naming doesn't make a difference.
    It's important which (midi) in/out-port is selected in the Device Setup..

    If you add a new midi-mapping (Add ... -> Generic MIDI), by default it uses 'All Ports'.
    So this mapping is 'listening' to all ports of (all) connected midi controllers (if a midi-message is coming in which is mapped to a Traktor function).
    ----------------------------------------------------------
    Different naming is useful, if let's say you have 3 mappings loaded into the controller manager. Now if
    all 3 mappings are named the same ('Generic MIDI'), you might have trouble to find out what each mapping does or for which midi-controller it's meant to be used.

    So to easily distinguish between the 3 mappings, you would, as example, rename them to something like:
    'APC20 2-decks' -> in/outport set to: NONE (this mapping is not active)
    'APC20 4-decks' -> in/outport set to: APC20 (that's the one which is currently used for the APC)
    NanoKontrol FX-only -> in/outport: NanoKontrol

    ----------------------------------------------------------
    In addition these links might also be interesting:
    How to use the controller manager
    Set up multiple controllers
     
  10. Skullee

    Skullee New Member

    Messages:
    22
    aaaah, i think i totally misunderstood what you meant how to set the I/O´s! Now i changed the I/O on the existing mapping (Mapping #1) to NONE. Then all the LEDs got turned off on the APC, and it does not interact with Traktor. And now i started a new Generic Midi with I/O to Akai APC20 and it works like it´s supposed to! Thank you! It was me that misunderstood the point of the I/O...something that was really obvious now when i first understood it :)

    SO..let me get this straight...whatever mapping that is set to I/O to APC20 (in my case) will work with the apc! And if i set it to NONE..it wont interact at all!
    It´s basically an "ON/OFF" switch for mapping to work with the controller...sorta!
     
  11. solger

    solger NI Product Owner

    Messages:
    3,941
    Exactly.

    o) Mapping is OFF (ports are set to 'NONE') -> the mapping is inactive.
    o) Mapping is ON (ports are set to 'APC20') -> the mapping will only listen/react to this midi-controller (-port).
     
  12. Skullee

    Skullee New Member

    Messages:
    22
    Totally my bad for all the confusion :) Thanks a lot man! Now it´s clear as day! One more thing...would you or anyone else know how to deal with this problem:

    I´ve started a brand new blank mapping for the APC20, but im having troubles setting up the LED outputs for my modifiers.

    I have 4 buttons. (It´s the "Scene Launch" buttons.)
    Button 1: Set modifier 1 to 0
    Button 2: Set modifier 1 to 1
    Button 3: Set modifier 2 to 0
    Button 4: Set modifier 2 to 1

    Im basically using them to swap between decks A and C, and B and D, and I would really like to have the LEDs mapped out so that when modifier 1 = 0, button1 lights up when i push it, when modifier 1 = 1, button 2 lights up when i push it etc.. So I can tell from a glance which decks I am controlling.

    If anyone could do a quick walk thru of this it would be great! This is my main problem!
     
  13. solger

    solger NI Product Owner

    Messages:
    3,941
    Basically you would do it like this:

    1) Add Out -> choose your command
    2) Hit 'Learn' and press the button you want to map
    3) set the Modifier condition (Modifier/value)
    4) Adjust the LED-options

    Also check out:
    - APC20 led mapping
    - Traktor led feedback
    - Sqeezing multiple states into one modifier
     
  14. Skullee

    Skullee New Member

    Messages:
    22
    Right now i have just set up Modifier #1 with 1-0 and 1-1!

    Now it works the way that the if i´m on M#1=0 (Button1), the button1 has no LED light, but the M#1=1(Button2) is lid up. If i click on the M#1=1 button(2) (that is currently lid up), the light closes on button 2 and lights up button 1. So..it´s basically backwards of what i want! It switches back and forth which is what i want, but the LED is active on the wrong modifier.

    I took screenshots of the 4 different modifier mapping thingys here:

    M1=1 OUT.png

    M1=0 OUT.png

    M1=1 IN.png

    M1=0 IN.png