Output LEDs on Macshine- Some don't respond

I am mapping 8 of my sixteen pads on one page for "loop size select + set" so I have quick jumps to the desired loop. The buttons do their job without a hitch but when I try to set them up so that they light up whenever that particular loop is active there is no response. I can turn the button on or off using invert checkbox so I know I have the right channel. There is a "loop active on" output that works to turn on a led when a loop is active but it only tells you the whole loop process is active not which parameter thus lighting up the same button no matter what parameter you choose. It does not allow me to choose the parameter that is active thus making it useless. Is there something that I am missing, seems alot has changed in the way of mapping with the new 2.5. Thank you for your suggestions.

 

Consider using "Loop Size selector" as output with Modifier Condition "Is in Active Loop".

 

I will give that a try when I get back into town. Thanks for the tip!

 

No luck on the Loop size selector working for that. Seems that it is designed just for lighting up if the loop is active. It does not give me the ability to define which parameter is active, thus either one or all buttons will light up when loop is active instead of the actual button that is triggered. Seems that NI meant for it to work the way I need it to since they provided a "loop size select+ set output definition......I think it is just a bug that need to be fixed. Any input from NI would be appreciated.

 

Some tips on LED mapping.

The Controller Type and interaction mode are fixed to LED and Output, so the only parameters that matter are the Min/Max for Controller and MIDI, and the Invert and Blend options.

Here's the tricky part. How the Min/Max of the Controller relates to the MIDI depends on how the blend option is set.

1) With Blend option ON
The Min value, the Max value, and all the values in between of the Controller Range is smoothly translated to corresponding Min/Max and in-between values of the MIDI Range. For instance, if the Min/Max of the Controller is 0/5 and the MIDI is 0/127, MIDI (usually some note) velocity 0 is outputted when the Controller (the value of the specific function we are mapping here) is 0 and velocity 127 is outputted when the Controller is 5. And when the Controller value is in between these two, also, corresponding MIDI values (give or take a few) 26, 51, 77, 102 will be outputted.

2)With Blend option OFF
Here the behavior changes quite a bit. In this mode, Whenever the Controller Value enters the range specified by the Min and Max values, the Max value for MIDI will be outputted, and when it exits the range, the Min value for MIDI will be outputted. For instance, if you wanted to turn on an LED when (and only when) the deck is playing, the Controller Range should be 1 to 1 (is playing) and the MIDI Range should be 0 to 127, with the blend option OFF.

The invert option simply flips the Min and Max value of the MIDI range.

Now we're ready to tackle your mapping.

Since I don't know the notes of your pads, let's suppose they are Note 1, Note 2, ...Note 8. Let's also suppose that the LOOP lengths you want to map are 1/4, 1/2, 1, 2, 4, 8, 16 and 32.

The first mapping for the LED of the first button (LOOP length 1/4 beat):
Add Out > Loop Size Selector
Device Mapping > Note 1
Controller Range 3 to 3 (0 is 1/32, 1 is 1/16....and 10 is 32 beats)
MIDI Range 0 to 127 (Given that your LED lights at 127)

Since you only want the LED to light up when the loop is active, add a modifier condition "Is in Active Loop / 1 (=yes)"

Here we face a bit of a problem. Though we want the above modifier condition so that the LED only lights up when the loop is active, it also disables the function of the mapping when the Loop is not active - hence, the LED won't turn off when you deactivate the loop.

Thus, we need a second mapping for the same LED:
Add Out > Loop Size Selector
Device Mapping > Note 1
Controller Range 3 to 3 (0 is 1/32, 1 is 1/16....and 10 is 32 beats)
MIDI Range 0 to 0
Modifier Condition Is in Active Loop / 0 (=No)

With these two mappings, the first button will light up when the Loop size is 1/4 beat and the loop is active, but will turn off as soon as the loop size changes, or the loop is deactivated.

Do the same for the remaining 7 pads.

 

Wow! Thanks DJ Micl! That did it! Just got a crash course in advanced mapping! Works like a charm! Couldn't have done it without you! Thanks a million!

 

TL;DR: ALWAYS use Blend! it should be the default as of 2020.

Many thanks for this clear explanation! I've searched a lot for this info.
The manual is silent, and articles just mention its side-effects.
https://djtechtools.com/2010/05/30/how-to-map-leds-in-traktor/

In my view blend=off is only usefull for very old controllers that required exaclty 127.
Newer controllers light up on ">=1", so in my view there is no reason for not to use blend in all cases.

I will certainly make CMDR warn if blend=OFF.

Below a small test to understand the great explanation with a simple modifier counter.