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

Running into a couple snags

Dieses Thema im Forum "KONTROL D2" wurde erstellt von zacharia360bpm, 11. Mai 2015.

  1. zacharia360bpm

    zacharia360bpm Forum Member

    Beiträge:
    32
    Hey guys,

    Just got my D2s and am totally loving them:)

    I have dove into the remix decks and am running into a few snags I'm hoping to get some input on.

    1. I am using an MP2015 and am wanting/needing to Cue particular remix slots before bringing them into the mix.
    I would think this would be possible by routing the Output Preview (in the Output Routing section of Traktor) to an open USB channel on my mixer but that isn't working. Can anyone shed some light on how I can get this done? Blindly triggering sample slots is not ideal.

    2. Tagging... Trying to play stems without knowing what key each one is in is.. well.. impossible.
    I noticed changing the Deck Headers in the Track Deck section doesn't carry over to Remix Decks. I suppose this makes sense if you are adding stems that aren't in the same key into the same Remix grouping. So far the only way I can see the key is if I open the browser and look at the stem in there but this is not practical.. way too time consuming. I'm hoping there is an easy way to have the key info show up within the sample slot without me having to manually type this info in.

    3. Question.. What are the number/letters that show up in front of the sample names within the browser?

    4. Quantize... I prefer to trigger my samples using the 1/4 quantize option. Currently I'm having to change the quantize option every time I load a new Remix Track. Is there a way to make 1/4 my default?

    5. I'm noticing after loading a Remix Track and playing a Sample slot for the first time it glitches and won't trigger on time most of the time.
    The way I'm able to work around this is by triggering ALL the samples before bringing anything into the mix but this is cumbersome and is obviously something I shouldn't have to do. Hoping there is a workaround for this?

    Note.. I am still running 10.8.5 and know this isn't a suggested OS for Traktor 2.8. Aside from a memory leak (and perhaps issue number 5) 10.8.5 is working fine for me. I will be updating very soon regardless.

    Thanks for reading this long thread and I appreciate any input:)

    -Zach
     
    zacharia360bpm, 11. Mai 2015
    #1