as far as i'm aware, the only way to currently make automation tracks for parameters on non-native VSTs such as Kontakt and Massive is to click the little arrow in the corner, then clicking "browse parameters" which opens a list of all parameters in the VST automatically linking to the latest parameter you tweaked.
this way of doing it isn't particularly friendly to workflow, at least not to me.
i would like to suggest having a little knob or box directly present on the top wrapper bar of the VST (next to the settings cog and plugin options arrow) which when clicked would bring up the same menu as you would get if you were to right click the parameter in the list, for the latest one you tweaked.
that way it would be quick to do automations as well as binding the parameter to a midi device, without interfering with potential right-click options in the VST.
any thoughts?
Easier automation for non-native VSTs
[You can only see part of this thread as you are not logged in to the forums]
Re: Easier automation for non-native VSTs
Last tweaked is already a thing, under the tool...
Re: Easier automation for non-native VSTs
Yea!, and also an option to enable slides and l...
Re: Easier automation for non-native VSTs
Adone wrote:Yea!, and also an option to enable ...
Re: Easier automation for non-native VSTs
Please remember that FLS has no control over 3r...
Re: Easier automation for non-native VSTs
m.letcher wrote:Please remember that FLS has no...
Re: Easier automation for non-native VSTs
Thanks for clarification. Not trying to be a tr...
Re: Easier automation for non-native VSTs
m.letcher wrote:Thanks for clarification. Not t...
Re: Easier automation for non-native VSTs
Right clicking the Multilink button does that i...
Re: Easier automation for non-native VSTs
nucleon wrote:Right clicking the Multilink butt...
Re: Easier automation for non-native VSTs
Its this one here:
multilink button.png
You do not have the required permissions to view the files attached to this post.
Re: Easier automation for non-native VSTs
nucleon wrote:Its this one here:
multilink but...
Re: Easier automation for non-native VSTs
By per key parameters, I'm guessing that you me...
Re: Easier automation for non-native VSTs
m.letcher wrote:By per key parameters, I'm gues...
Re: Easier automation for non-native VSTs
The updated Envelope controller in FL12 allows ...
Re: Easier automation for non-native VSTs
nucleon wrote:The updated Envelope controller i...
Re: Easier automation for non-native VSTs
So, do you need per note automation or just a g...
Re: Easier automation for non-native VSTs
Great, sounds like you've found a solution. Tho...