Because of that the buttons and the leds of the buttons have different midi nrs i have made a map/diagram with the midi nrs of the leds.
Its almost complete only missing 2 led midi nrs as far i can see.
I shortend the midi nrs, for example C#2 is NOTE C#2 (ch1), its all the same.
I hope not
Vestax should be give us all that info, but the f*ckers didnt do that, probably it because it supposed to be itch only…
Just did it in traktor, maybe their are apps to do that but i dont have that..
Well the “problem” with the vci-300 is that the midi nrs. of the buttons/knobs are different midi nrs. than the leds of the button/led, as far as i know with most controllers you dont have this, but correct me if im wrong? already tried it?
one button on the VCI-100 (the one in the center of the browser section) is different. the button is A#6 and the LED is B6. the rest are all the same AFAIK.
my ddm4000 mixer has also different numbers for his buttons / leds - as you describe - but there’s a “midi receive overview” on the behringer homepage you can download
had a crack at mapping the vci 300 and got some results, thought I’d share, vu meter leds tend to cause a lot of crackle, which i managed to reduce via raising the latency, some of the leds assigned dont seem to work if when their counter part is assigned, i.e i assigned the sync buttons as a test but only one works if the other is mapped to an led, looks like progress is slow, and hampered by these little setbacks, anyone tried this?