LED Mapping Pads

Toltemic

Hello I am currently mapping a rane a-trak mixer for traktor

I have currently hit an issue that I cant seem to find a quick solution.

I have mapped quick loops where by you press a pad and it auto sets a loop division, the lighting corresponds by showing the pad as active with a light green when pressed, and if I press another pad it'll set the new pad as active whilst the previous pad being set to default inactive green. Also all the pads will turn inactive green when no loop is active.

I have done this by having 'pad master' as 2 states inactive green and active green, and all the 'Swap' options just being inactive green when any other pad is pressed as seen by the added modifier #8 - 0-7 being pad 1-8

so when any other pad is pressed (pad 1-7 or modifier#8 0-6)pad 8 will default to one of the swap rules instead of master.

My first question, is there an easier way to programme this or am I stuck with 64 'loop is active' rules. x2 (for deck b) or x4 if the issue below gets resolved

My second issue

I also would like to have it - when shift is held on quick loop- all the pad change to red with the same rules above for back looping, however when pressing shift the LEDs do not update even when the modifier is on the correct number unless the pad is pressed. Unlike when I press the pad layer buttons to change between hotcue/loop/slip roll.

A couple of notes:

The rane A trak send notes not CC

modifier m1=1 is the button to change the pads to the quick loop pads

modifier M3=2 is M1=1 whilst shift is pressed and it is mapped to shift button

I have discovered that natively the shift button changes the notes on the rane a trak and have mapped them accordingly

forgive my explanation as this is the first time I've mapped something/have worked with conditionals and rules

Stevan

It is hard to tell without looking at the TSI file itself.

Stevan

It is hard to tell without looking at the TSI file itself.

Toltemic

I figured it out, firstly should've used 'loop size selector' out with 'is loop active' modifier

and also learnt about the send monitor state command which fixed my second issue