Is it possible to get confirmation that the VCA bug when restarting sessions will be fixed soon?

I think it’s [CAN-10904] Issue, which has been acknowledged officially since Cubase 8 or so.

The issue is that faders which have an automated VCA controlling them often return to zero when you re-load your session. It doesn’t always happen, maybe about 75% of the time, and I have no idea what causes it. Faders linked to VCAs need to behave exactly as you had them set when you re-load a session.

This has been around/acknowledged as a bug years, and is crucial to fix. I don’t mean this in a rant-y voice, I just mean to underline how huge an issue it is, and that it makes automated VCAs not usable unless you “print” the VCA automation every single time you close Cubase which is of course not what one would want because it defeats the flexibility and ease of adjusting the VCA’d tracks every time you open up a session anew.

Can we please get a confirmation that this will be fixed soon?

Hi,

As far as I know, the fix is to add an initial node to the beginning of your project to every VCA Channel.

1 Like

Oh cool, I didn’t know about this workaround (until there’s a fix)! Do you mean add an automation node at the very beginning of the project for each automated VCA track?

Hi,

Yes. And add in other but the -oo value, please.

1 Like

Great, will do. Thank you! Hopefully this can get fixed but I’m guessing it’s a deep issue since it’s been so many years.