About VstiAutomateDevice and built-in VST parameter editor:
You should call plug-ins string2parameter -routine (if it’s implemented in the plug-in) when user enters parameter by keyboard instead of using hard-coded [0, 100] range. This way you could easily map any parameter from string to float just like the plug-in author wanted.
Also there are evil gaps in the values when using MidiCCDevice (i.e. you can’t set some values). If you set the slider at 0, and press arrow right, it’ll jump over some values (f.ex 2 and 7). It’s not possible to set those values by using keyboard either.
Have you tried using keycombo’s like left-shift click or left-ctrl click to finetune the value-step of the parameters?
Also, doubleclicking the values themselves allows you to manually enter the precise value.
This is ofcourse not handy when testing different values in a lineairy way.
Clicking with Ctrl/Shift held down doesn’t affect it. And as I said, it’s not possible to enter the value using keyboard. If I click on the value, and enter 2, it’ll change to 3 (actually it seems to do nothing no matter what value I enter).
Actually, now that I tested it, it actually sends wrong values to the device also (tested with a simple VSTi plug-in), but also jumps over some values.
“0” sends 0, “1” sends 1, “3” sends 2 (gap in display), “4” sends 3, “5” sends 5 (jumped over 4), “6” sends 6, “8” sends 7 (gap in display), “9” sends 8, “10” sends 10 (jumped over 9), etc.
This is of course not critical, since not a lot of people need to tune MIDI controllers this precisely, but if a device uses some special controller values for specific stuff, it could become a problem. And of course it’d be a sign of professionality if the values that are displayed would actually be the values sent to the device
