I’m trying to create a system where the bottom row of leds indicate the current function of the performance pads (Mixtrack Pro 2). The bottom row function is not changable and therefore remains unchainged. However, the overall function of the pads is changeable. With the 3 leds I want to indicate which overall function is selected by having one of the 3 (or none) flashing. This is all working at the moment.
What isn’t working is that when the modifier responsible for the overall setting changes and the blinking led is on at that moment, it will stay on solid. I’ve tried curing this with Send Monitor State for the buttons that change the modifiers, but it stays on regardless. even when pressing a Send Monitor State button multiple times.
Am I using the Send Monitor State in a wrong way, did I miss something else, or is this even fixable at all?
Not sure how you have it mapped, but you need to map every state of the modifier to each LED.
For example if you have 3 LEDs, and you want the first one to turn on when the modifier=1, the second to turn on when the modifier=2 (and the first one turns off), etc., and you want them all off when the modifier=0. You will need to map the all the LEDs 4 times
LED #1
modifier=0 (LED off) (this is the all off state)
modifier=1 (LED on)
modifier=2 (LED off)
modifier=3 (LED off)
I’m afraid that’s not possible. The bottom row of performace pads has 3 layers, each with their own note. The led will change accordingly. This is hardware controlled and not possible to monitor with a modifier. I’m also using beat phase instead of just a led that’s on or off.
Are your modifier output commands assigned by any modifier conditions?
Do you select active modifier by holding hardware shift or a modifier?
Why do you create another Mixtrack Pro 2 related thread?
I know this is related to my project of increasing performance pad usablility, but it’s a general mapping problem. The modifier is changed by pressing shift plus a button. The beat phase has of course modifier conditions or else all 3 would blink at any given moment.
A random thought: Try to duplicate your beat phase but this time change it’s condition of overall modifier to zero. Then set 0 - 0 at midi range which should prevent LED to stay lite.
Good idea. I tried it and it totally works for the blinking leds. But now the solid leds don’t stay on either, they will only be lit when I press shift+pad again. After that I get the state that I want. I don’t think there’s a workaround for this inside Traktor since you can’t monitor the solid led state. Or would it work with a program like midipipe? I have no experience with those programs yet. I’m also on windows, so midipipe is not available.
I think you can do this in traktor by using the same principal on your modifier outputs. Can you take a screen shot of your modifier setup or share a .tsi?
I don’t think one screenshot would be enough xD Here’s the tsi of what I’ve got so far. The problem is that I don’t know of a way to create a modifier for the solid led state as the solid led is triggered by the hardware. Trying to capture it only sends the shift button to the software.
My Mixtrack isn’t here to test this but I should give it a try in a few days. By looking in the tsi it currently looks that your modifiers 3 and 4 are your preset mods? If so I can’t even see the outputs for this commands.
Modifiers 3 and 4 is for the allocation of the pads, yes. It uses all 8 values; 0-3 for the modes with 4-7 as an extra layer when shift is pressed. This way I can still use the remix decks without needing 3 conditions. The outputs are simply the beat phase ones with loop, sample or cue blink in the comments. The value 3 has no output as that is the mode where there are no leds blinking (mode 4 if you will). This mode is mapped and available, but it has no functions allocated to it yet.
Ok, I should have included more info, my bad. What you do to change modes is press the opposing shift to one of the four buttons under the jogwheel. For instance pressing the right shift plus sync changes m3 to 0. Then the top row represents the effects and the bottom row contains loops of 1/16 to 1/2. Changing pad modes like it was intended still works as well. Changing from loop to sample changes the bottom row to loops of 1, 2, 4 and 16. The cue mode switches the bottom row to manual loops. All this time the top row keeps the effects. Changing the modes also changes the function of the rotaries on top. In sample mode it controls the volume and filters. I hope you understand my mapping now.
