Device Target not acting like it should

Either I'm misunderstanding something, or the Deck Focus isn't working as it should. If I get this right then if you assign a button that belongs to either left or right side of the deck, f.x. the hot cue buttons on Deck A/C, they should work on Deck A or Deck C, based on whether Deck A or Deck C has focus, selectable by the DECK C button in the top left.

Let's say I map hot cue button number one to kill the bass (Mixer > EQ > Low Kill), in the Mapping Details section, I have "assignment" set to "Device Target", and Global Settings > Deck Focus Selector is set to "Hardware". I would expect the button to function on the Deck that has focus at the moment. So if Deck A has focus, the button should work on Deck A, but if I change focus to Deck C by pressing the DECK C button, the button should work on Deck C. Instead the button works on the Deck that has "Software focus", as if no controller was connected, as if Global Settings > Deck Focus was set to "software". I've verified this by setting a shortcut button on the keyboard to the function Layout > Deck Focus Selector. So by pressing this shortcut, I can cycle through the Decks, and the button will affected the deck chosen by the shortcut. Similar to what happens if you hafe Global Settings > Deck Focus Selector set to "Software", where one can see what deck has focus by the fact that it gets marked with Orange.

This sounds like a flaw to me, but maybe it's just me disagreeing with the NI development team.

I've managed to get around this by assigning the DECK C button to Modifier#5, which cycles between 0 and 1, and created two mappings, one with Condition M5=0, which controls Deck A, and another one with Condition M5=1, which controls Deck B. So I've achieved this functionality, but with allot of overhead... this should be made simpler.

Anyone know if this is a flaw, or if there is another easier way around this?

regards
Frímann

 

I've had issues with my own mappings with deck focus and now hard code everything just to be sure. I would agree that focus always appears to be software focus.

 

Device target only works with software focus because hardware focus has 2 decks focussed at the same time and device target cannot know which one you mean.

 

If the button is on the left or right side of the controller it should be pretty obvious which deck it's supposed to be connected to... they should at least put this in as an option, would make things much easier.

 

Mapping doesn't work like that and it would add an extra layer of complexity if it did. I agree in some circumstances it would make things easier though.