Automation!!!!!!

infuzion · 8 Jun 2005

urm, what exactly do they mean by "automation"? cheers

Ixox · 8 Jun 2005

infuzion wrote: urm, what exactly do they mean by "automation"? cheers

You can control the parameters of the pluggins from your host to make them change during the track.

RobR · 8 Jun 2005

Coincedence or what? I was just about to post a newbie question about not being able to automate parameters, when I saw the new release.

lalo · 8 Jun 2005

Ixox wrote: infuzion wrote: urm, what exactly do they mean by "automation"? cheers

You can control the parameters of the pluggins from your host to make them change during the track.

or i can modulate them with my midi controllers when doin' live with bidule 😉

infuzion · 8 Jun 2005

lalo wrote: or i can modulate them with my midi controllers when doin' live with bidule 😉

Oh, so we can read MIDI CV now? How do we do that exactly?

unkargherth · 8 Jun 2005

No. You should read directly midi input and select the controller you want.

For example, if you want controller 11 ( expression) control your filter cutoff, your filter submodule should have a midi input connected to a MIDI CC module. you especify 11 as input and divide the output by 127. then you got a nice 0..1 value to moodulate yout cutoff

Evidently, this could be a nightmare to do if you wanna control said 90 parameters. So i expect Finally an idea of hidden busses ( hidden in the sense of "to Parent" , "to Child" modules), but for all types will be implemented.

This way you have and inmediate access to midi stream in every module, making damned easy to build a correctly "automated" VSTi.

The support for RPN's/NRPN's could be a bit trickier, preferably solved by a native module.

And maybe somebody will develope some "MIDI Learn" system too...