It works perfectly in Ableton Live, however, when I try to assign knobs or faders to different parameters in any VSTi within Live, the VST picks up signals as if there is only one knob/fader, not 8 of each.
Example:
If I assign a fader to a parameter within any VST (NI Massive, Zebra2, Albino), now the parameter is controlled by ANY of the faders, instead of just the fader I assigned it to. If I assign a second fader to a second parameter, now all faders control the second parameter.
It's as if the VSTs only pick up the difference between a knob, a fader and a pad, but not the difference between faders 1-8, pads 1-16, and knobs 1-8. There is no issue with the piano keys.
Any help would be appreciated, I know the midi-learn assignments I'm making should work, as the same process works fine with other (admittedly newer) midi controllers. And like I said, Ableton Live itself can tell the difference between faders 1-8, just not any VSTs running within it.
I guess I'm also asking if this is fixed in the firmware upgrade, which I am as-yet unable to install because I don't run Windows XP (I'm on 7). I'm trying to run virtual PC with XP, and upgrade it that way, but it's seriously time-consuming and I'm not sure if it'll do anything. The readme for the upgrade doesn't specifically mention this problem, and I can't find a similar complaint anywhere online.
Please respond if you have an idea, or a similar problem, or run a microKONTROL flawlessly with VSTs within Ableton Live.
Thanks in advance, I would love to use this controller to its full potential and truly decimate some saw-waves.
-Tom