BSmurf
Hi. I have a reloop beatmix 4, and have trouble gering leds to light in mode b.
Studying parameters in the mapping, shows that only pad led parameters are acessible in mode1(A) with and without shift.
The parameter to lit pad leds in mode B is missing in the internat midi definition file.
Is this. Going to be fixed? Or is it somehow possible to extract the built in definition data? And add the missing, making an external midi definition file for a fix?
Its sad not beeing able to use leds in all modes, just because og this :( please help)
Studying parameters in the mapping, shows that only pad led parameters are acessible in mode1(A) with and without shift.
The parameter to lit pad leds in mode B is missing in the internat midi definition file.
Is this. Going to be fixed? Or is it somehow possible to extract the built in definition data? And add the missing, making an external midi definition file for a fix?
Its sad not beeing able to use leds in all modes, just because og this :( please help)
Posted Tue 10 Nov 20 @ 8:43 pm
djdad
All available leds are defined. There is only one led for each Pad, regardless the Mode (A, B, AB)
Each led has 3 or 4 keys in definition which represent a color that the led can get.
Each time a mode is selected, the color key of the led in the default mapping is having an on/off
E.g. PAD 1 has 3 keys named as .. LED_PAD1_OFF, LED_PAD1_BLUE and LED_PAD1_RED.
If for example, you want to light the led of PAD 1 blue in mode A and red in mode B, you need something like..
LED_PAD1_BLUE :
LED_PAD1_RED :
and LED_PAD1_OFF (you need to enable this in case you want the led to be off - but in this example you dont want that, so needs to be off in all modes)
padmode 0 : Mode A
padmode 1 : Mode B
padmode 2 : Mode AB
Last but not least, for the weirdness of the above definition and mapping , blame Reloop firmware ;) . In order to go from one color to the other, you cant just pass the value of the available color, you need to send off first. Go figure :P
Anyways , if you want further assistance in mapping your Pads and leds, let us know.
Each led has 3 or 4 keys in definition which represent a color that the led can get.
Each time a mode is selected, the color key of the led in the default mapping is having an on/off
E.g. PAD 1 has 3 keys named as .. LED_PAD1_OFF, LED_PAD1_BLUE and LED_PAD1_RED.
If for example, you want to light the led of PAD 1 blue in mode A and red in mode B, you need something like..
LED_PAD1_BLUE :
var 'padmode' 0 ? on : var 'padmode' 2 ? off : off
LED_PAD1_RED :
var 'padmode' 0 ? off : var 'padmode' 2 ? off : on
and LED_PAD1_OFF (you need to enable this in case you want the led to be off - but in this example you dont want that, so needs to be off in all modes)
var 'padmode' 0 ? off : var 'padmode' 2 ? off : off
padmode 0 : Mode A
padmode 1 : Mode B
padmode 2 : Mode AB
Last but not least, for the weirdness of the above definition and mapping , blame Reloop firmware ;) . In order to go from one color to the other, you cant just pass the value of the available color, you need to send off first. Go figure :P
Anyways , if you want further assistance in mapping your Pads and leds, let us know.
Posted Wed 11 Nov 20 @ 11:43 pm