though this is right, he rather meant to record the cutoff-movement from the gui directly, which is an entirely different thing, as the resolution of a vsti automation is way higher than with the modwheel, where the resolution is 0-127 max ...codec_spurt wrote:Wrong again!Pepsito wrote:Hm it seems like that (for example) the filter cutoff can't be automated by the host?
What makes you say that?
Download (for example) this bank: 'C_S_Bank-02'
http://rekkerd.org/patches/plug-in/sq8lsq8x/
and find the patch called 'Mod-Wheely' - it modulates the filter
cutoff - now tweak your modwheel et voila! By now you should
be getting the picture...
however, i often prefer the controller method myself, as the play-performance is making the sound comeing alive often ... also, midi automation has more benefits, such as moving just a midipart/region/item wherever you want, remap the contoller and beeing able to easily use he same automation curve on whatever parameter on whatever trackparameter/synthparameter you want ...
depends on the host of course, but on cubase or logic (and some others), that way of controlling/handling automated parameters is way more intuitive than with a conventional track-based automation ...


