How to map LEDs for loops in Traktor?

[zestoi]

Now how i can define outputs of loop active for each separate button...
I mean when i press in traktor select/set loop defined to 2, i want that on my controller, button assigned to this function will on as well. Any thoughts ?

you'll need to have the led's driven just by the loop states in traktor and not your modifers if you want to do that - in fact may not need any modifiers. should be able to add an out (per button/led) of "loop size selector" with "is in active loop"=1 as a condition and tweak the controller range for each button. you should then (i think) be able to get 4 different midi outs that toggle between on and off based on the loop size and loop status. i'm sure i remember something odd about trying to do this before in traktor tho - but that out *looks* like it would do the trick. used to be called "loop size set" in older versions of traktor i think and pretty sure that's what i've used. looks like i used to use "loop size" and "loop set" in some old configs of mine to do that kind of thing.

[Stewe]

Hey zestoi, I tried to set different controller range Loop set+size, Set, Selector and nothing happen in first place. Then I tried to overcome it with modifiers.

If you can set it like you said, would like to see that mapping.

[zestoi]

it's been a long time since i've tried to do something like that natively in traktor mapping (and actually a long time since i've even used traktor) but looking at my midimasher code it sends the "loop size set" and "loop active" controls to traktor when you press a button and listens to feedback from traktor for "loop size" and "loop active" to work out how to change the led colors on the actual controller.

i.e: it doesn't set local led colours on the controller just based on what it sends out but only on midi feedback. in theory if midimasher can get feedback for those events then it *should* be possible (maybe with some blood, sweat and tears ) to do it directly within traktor.

one gotcha is that traktor will just ignore the "loop size set" command if it's the current size and hence not send out any midi feedback for that.

i guess the "loop size selector" and "is in active loop" from 2.5 work the same way as the other two from previous versions. i do remember that when i was using midikatapult for my launchpad and doing the actual mapping within traktor this loops stuff was a total PITA but i thought it was possible.

ofc in midimasher the logic is easy to implement, on both of the "loop active" and "loop size" feedback from traktor it just stashes the values locally and then if it got a "loop active" off it turns off any pads that are on and if it got a "loop size" that is different to the current it checks changes the led's and ditto if it got a "loop active" of 'on' when it was off previously. should be possible directly within traktor but maybe not all that simple - or at least maybe more controls and conditions need mapping that i realise atm.

[zestoi]

one possible way (maybe) to emulate what i do in midimasher would be to:

* set a modifier like you do to store the loop size set from the controller like u already do
* map an 'out' for loop active and use the modifier value as a condition
* map an 'out' for loop size and use the loop active status as a modifier condition

but that still doesn't cover the case where the loop is active and you change the loop size from outside of the controller. it would be simple if either you could choose the loop length as a condition or you could route the loop size back into a modifier and to do that you'd need a midi loopback device so then may as well run middleware software to do the logic too anyway. you'd think it'd be easy

[Stewe]

Man that's why I said that it is not defined in newest versions. There should be output command named like "loop size preset" or something to do this stuff. I see no other way of doing it directly from traktor than this I've posted here. In this scenario you can't lite individual LED from screen to controller but why would you do that when you already got all the loops mappedd on your controller? See my point...

[zestoi]

Man that's why I said that it is not defined in newest versions.

what isn't defined in the latest version(s)? haven't just "loop active" and "loop size" basically been renamed? isn't basically "loop size" now called "loop size selector" and "loop active" called "is in active loop" ? we don't need any extra controls to that - tho not having a builtin condition we can add for the current loop length is a pain - but this isn't anything new in 2.5

There should be output command named like "loop size preset" or something to do this stuff. I see no other way of doing it directly from traktor than this I've posted here. In this scenario you can't lite individual LED from screen to controller but why would you do that when you already got all the loops mappedd on your controller? See my point...

ah - the "loop size selector" out is just the indicator that you've sent a "loop size selector" control in?

there's every reason to want to be able to do it *unless* you are only using one controller i guess and never control traktor via the gui and/or keyboard.

i'm not sure what the use case is tho for using too many other controls while a loop is active - but i'd still rather know the controllers are 100% in sync with the status in traktor.

[Stewe]

what isn't defined in the latest version(s)? haven't just "loop active" and "loop size" basically been renamed? isn't basically "loop size" now called "loop size selector" and "loop active" called "is in active loop" ? we don't need any extra controls to that - tho not having a builtin condition we can add for the current loop length is a pain - but this isn't anything new in 2.5

You are right, those commands has been renamed but still it can't be normally mapped to traktor with no midimasher and some other inmiddle software or routing to do such loop out behavior. That why I said about not to be defined. I don't have another controller to test it with but for now I'm pretty much sure the result could be the same.

[zestoi]

sure - you're probably right that it still can't be done without some other software or at least one virtual midi cable that just routes back into traktor. i do find it odd that something that *should* be common for people to want to do doesn't seem simple at all

[phawsea]

hey, did anybody find out how to read the actual loop size directly from traktor and then light up the corresponding led? i also have a row of 4 leds for loop sizes 4 to 32 and if i press a modifier it's 1/4 to 2. thanks

[Stewe]

/32 = 0
/16 = 1
/8 = 2
/4 = 3
/2 = 4
1 = 5
2 = 6
4 = 7
8 = 8
16 = 9
32 = 10