Deck Focus mapping help

Well spotted. Typo.

Woooorrdd!

Wow, thank you so much to all of you who have replied. I have been busy with work so I haven’t had a chance to try any of these solutions out yet, but I am eagerly awaiting a chance to do so. However, I didn’t mean to stir up so much controversy, but I’m glad it came to a peaceful resolution. I do want to weigh in on dj db’s side though, as we all know, shit happens. I think that’s all he was saying in terms of preparing a mapping for the worst case scenario such as changing deck focus by mouse and having the last deck toggle send you back and forth between one right deck and one wrong deck. From my brief time programming java in college, I believe this is called “error catching”, and it’s good to have in every type of program. Thanks again though, to everybody, and I will get back to you soon with the results.

Also, I’m gonna get the Traktor bible soon, but I was just looking for a shorter term solution to this specific problem so I can practice.

:stuck_out_tongue:

Nah, no controversy here. haha. But as I said, I would have to agree with the toggle solution if you’re confident you’ll never use (and hide) C&D.

hmmmm

So, eventually, I would love to be able to use the sample decks just to have a couple different samples loaded into each side and have the third row


XXXX



be two samples on each C & D (drops, sirens w/e). And to clarify, I’m building this off the slicer map that was put up on the blog a few days ago, cause I nearly pooped myself when I saw that on serato, and thought it would be incredible with Traktor. Mapping those four to play samples I think I know how to do just fine, as there is no changing with the deck focus. But, db, if as mentioned, you could elaborate slightly on the modifier method for the AB toggle that would be awesome, as I have no idea what you meant. I am still totally a novice when it comes to programming in Traktor.

Gracias.

Well since you say you’ll eventually be moving towards using C&D for samples, I’ll go back to this method (not the toggle), expanded out a bit…(sorry karlos. haha.)

Add in:

  • Modifier>Modifier #1; Modifier Condition- M1=0, Type of Controller-Button, Interaction Mode- Direct, set to value 1
  • Modifier>Modifier #1; Modifier Condition- M1=1, Type of Controller-Button, Interaction Mode- Direct, set to value 0
  • Layout>Deck Focus Select; Modifier Condition- M1=0, Type of Controller-Button, Interaction Mode- Direct, set to Deck A
  • Layout>Deck Focus Select; Modifier Condition- M1=1, Type of Controller-Button, Interaction Mode- Direct, set to Deck B

Map all of the above to the same button.

duuuuude!!

WOW! Thank you so much. It might have taken me years to figure that out on my own. Plus, it has given me insight as to how the programming works on this interface. Much love.

I have uploaded the map on here now, but keep in mind that you need to follow the instructions here:

to get it to work. I’m using the MidiPipe program that they suggest, but ya’ll can do w/e.

My mapping works the same as theirs, except the top right button is toggle decks A & B, the button to the left of that is beat sync, and in the third row, the left most two buttons are trigger samples 3.1 & 3.2, and the right most buttons are trigger samples 4.1 & 4.2.

Thats what we call “Moving the goal posts”.

Nice mapping though and exactly what i was doing before i chose the toggle (on the original brief:wink:) Props.