So it would be about realtime movement of vca fader does not move the controlled tracks faders.
Tested Reaper 5.4 just recently, and testing this working as this tut - I did not fancy not getting visuals where you are, you could be well on overs and not see it. Or on infinite low - and you have no clue.
VCAs became all abstract, kind of - something is done but you only see on meters that something is happening.
You at least get some kind of reference to existing automation - this is way over or at infinite low.
Having no other reference to VCAs, I kind of prefer getting visuals.
- ok, here the sum of movement automation+vca went really low
Thinking if movement goes below infinite low, you won’t get back to same relative level moving same amount up later.
You have to do some gain staging for this not to happend.
But tut did not fully investigate automation. Example was all without existing automation of what you control with VCA.
And no running of it all to see what moves and is shown visually - he just wrote automation, and then left.
A pity tut did not show this. I think ProTools does it like Cubase - and you get ghost curves on top of existing automation.
So Reaper scored no points in VCA area for me. I felt left in the dark. Reaper did not allow nesting VCAs either so left it at that.
Especially when you come at gigantic projects, with a range of VCAs controlling other VCAs - I want visuals.
How many play throughs are you going to do - before knowing no overs anywhere.
That’s common sense for me.
A SOS review of PT implementation of VCA: