(new question is post 3)
good evening wonderful people of djtt.
got a quick one about the midi range on the LEDs of a vci 100.
just finished some epic remapping, and now have it so that my jogs have 4 different 'modes' a/b scratch, c/d scratch, browser control and a/b pitch control.
i'm planning to rewire the leds from a couple of buttons into the middle of the faceplate to show the 'jog mode'. using the two buttons directly above channel faders. i'll call them 'a' and 'b'
just want to check that the midi range is basically, 0 -off 1 - orange 2 - green?
(i'll be changing them to blue ones though)
output mapping will be based on modifier state
the states are;
a/b scratch - mod 2 = 0 / mod 5 = 0
c/d scratch - mod 2 = 0 / mod 5 = 1
browser = mod 2 = 2 / mod 5 = 2
a/b pitch - mod 2 = 1 / mod 5 = 0
at a guess for map....
(min / max)
a/b scratch - modifier 2, control range 0 / 1, midi range 1 / 0 [note a]
c/d scratch - modifier 5, control range 0 / 1, midi range 0 / 2 [note a]
if i'm right, this would turn one light on when mod 2 is '0 state' and the other when mod 5 is '1 state' and so other 2 would be
browse - mod 5, control range 0 / 2, midi range 0 / 1 [note b]
a/b pitch - mod 2, control range 1 / 0, midi range 2 / 0 [note b] mod 5 = 0 (would need mod 5 condition as the 'pitch mode' won't work in c/d scratch mode, and don't want the light on for no reason when hit shift (mod 2) button)
basing browse on mod 5 as mod 2 state can be changed after loading, but jog won't do anything, so technically still in browse mode, kinda
EDIT: 0 = orange, 1 upto 127 is green, so would need 4 buttons worth of leds, so just using 2, one for browse and one for c/d scratch. and that's on the ones that 2 leds, some only have one green, and found the transport ones don't seem to be mappable
Bookmarks