Re: synth automation vs. recording MIDI controller data
2014/06/30 12:17:45
(permalink)
I'd guess he's talking about automating exposed parameters versus MIDI-Learn. Any VST effect or instrument can expose parameters that then conveniently show up in the envelope context menu and may be easily automated just like a volume envelope.
However, synthesizers typically have a very large number of parameters, often too many to practically list them all. Some don't expose anything except volume. For those, you need to explicitly assign a MIDI controller. It's not terribly inconvenient but does require an extra step of linking the CC to a specific knob.
I always check first to see if the parameter is exposed for easy automation. So for Zebra, for example, I can automate the X/Y controllers by simply adding an envelope and choosing one of the X/Y parameters from a list. But if I want to automate an LFO's frequency, that's not one of the exposed parameters and therefore requires MIDI-Learn. Omnisphere, OTH, exposes nothing so any automation requires choosing a free CC number and assigning it to a knob.

All else is in doubt, so this is the truth I cling to.
My Stuff