let’s say I have 3 tracks:
Bells = fader @ -12
Synth = fader @ -13
Sine Lead = fader @ - 17
I like the level I have set between the 3 sounds, and I want automate them as they are… so I would use a VCA fader to link and begin automating etc… which is how VCA works etc…
but when I re-open my song… my 3 sounds are no longer set to their initial levels I had set.
their fader volumes are now set to the VCA faders level. sometimes 0db sometimes -45db…
its very annoying and makes VCAs useless to me. I need perfect recall…
There’s at least one long thread about it. It’s a bug that’s been around for long enough that it should have been fixed years ago.
The solution is to create an automation point anywhere on the timeline on the related tracks. As long as it’s there recall should be ok when reopening the pr
SOMEONE from Steinberg must have acknowledged and/or weighed in on this issue by now, right? VCA’s are a pretty fundamental component of a DAW. and to have them broken like this for years makes me think someone finds the current behavior to be “correct” somehow.
I might misremember, but didn’t they already, and the problem was that they kinda painted themselves in the corner with that bug, because the only way to fix it would break something else? I have a vague memory of something like that (but might be completely wrong…)
I recall someone saying someone from Steinberg said they changed VCA Implementation in Cubase to make it different from Nuendo due to user demand, and apparently believe that most users prefer it broken I guess?
Would be great to get an updated response on the issue.
I am not familiar with that conversation but could it possibly have been about something slightly different than this issue?
I don’t think it is intended design to have the project sound differently from the previous save.
Personally I think that is the worst thing that can happen after the program crashing => loss of data/work.
It’s not weird at all. Cubase applies the VCA value twice upon opening the project. But the volume automation on the audio tracks overrides the second application. Thus the bug is surpressed.
If you try to move the fader when there is volume automation, the fader will just snap back to its former position. It is the same effect.
The other workaround is to put the song position pointer (playhead cursor) to a spot where the VCA automation is at 0.0dB (like on your screenshot) and save the project.
Upon opening the project again as per the bug Cubase will apply the value of the VCA at the song position pointer. Since the value is 0.0dB = neutral, no change will occur.
