I've recently been trying to get to grips with ACT, it's about time
However, as I have discovered, while you can map the controls of a VST in the effects bin to your controllers,
you cannot map the controls of a VST in a ProChannel FX Chain. Is this correct? If so, it seems to be a ridiculous limitation. If like me you do everything in the ProChannel, it makes ACT absolutely useless in terms of mapping controllers to 3rd party effect parameters.
So next I figured OK, so I'll create an FX Chain control and assign it to the VST parameter in question. Okay, I was able to do this and the control showed up in ACT. However, when I turn the rotary on my controller past a certain speed (really not that fast), the corresponding knob on the VST turns in big jerks and not smoothly as you'd expect. It's therefore useless as a performance control. Why is this? If I assign a rotary to a synth knob with remote control (not using ACT), I can turn it as fast as I like and the synth knob follows my movements smoothly and faithfully. Is there something wrong with ACT in this respect?
Above all, you should be able to directly map the controls of ProChannel FX Chain VST's to a controller using ACT, just like you can with a VST in an effects bin. Is this a bug or is there some reasoning behind why you can't do this? Because I'm pretty sure the average user is going to think there should be no difference between effects bin plugins and FX Chain plugins with respect to ACT.
Would appreciate some feedback from anyone who's had more success with all of this