twelvetwelve:
VCAs by themselves are “okay”. As soon as you add automation into the mix then VCAs are broken and I wouldn’t recommend using them at all in their current state. Unless you are aware of all the pitfalls you can run into the situation where your mix is destroyed either when automating new elements, loading the session etc.
This bug (out of many) for example is still an issue:
Create a new project
Create an audio track
Set audio track to -10dB FS
Create a VCA which is connected to that audio track (VCA @ 0, audio track still @ -10)
Draw some automation on the VCA channel which goes from 0 to -oo (e.g. a few bars into the project)
Position the cursor on the VCA automation which is @ -oo and save the project
Close the project
Re-open the project
Position the cursor at the front of the project
→ Expected: Audio track would be @ -10dB FS at the front of the session with the VCA @ 0
→ Action: Audio track is now @ 0dB FS with the VCA @ 0
This is really bad. We can’t use VCA’s like this.
And BTW, technically they should be called DCA’s and not VCA’s, because the later was used for analogue circuitos.