First of all, thank you for v11, wonderful work! I just have a small concern.
The installer states that for future, compatibility mode should not be used.
So does that mean that in let's say v12, there will be no compatibility mode? Or does that just mean that the plugin parameter order/range will no longer be guaranteed to be consistent?
I am personally not a fan of having to bind anything before being allowed to use it for several reasons, a big one of them is removing the possibility to automate or even just change a parameter directly in the interface if I want to still automate it later. (quick learn is great, but)
Parameters are already placed in a place where you expect to find them, I do not wish to make a coherent easy screen each time I want to automate several parameters.
If indeed the compatibility mode is to be deprecated (the fact that it's either on or off for all plugins, not individually, makes me think that way), may I suggest that the option to make the mutliparameter follow the value of the first parameter it is bound to so that they can be controlled from the edit screen.
P.S. Midi note controller shift can be bound, but can not be learned buy multiparameters.
Concern about compatibility mode
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Thank you!
Actually it's not that bad. First, the automation compatibility mode will probably be there indefinitely, but you know, one never knows
. Anyways, most of the plugin parameters ARE still automatable. Only the stuff like modulators or MIDI has been removed as these are rarely used at all and every modulator has like 100 parameters
.
I'll check abou the learning!
Actually it's not that bad. First, the automation compatibility mode will probably be there indefinitely, but you know, one never knows
I'll check abou the learning!
