This seems a great solution to me, it’s just my habit, I don’t wanna see the Read button turn Green when I don’t use it. Anyway I will follow your advice.
Thank you.
1 Like
Let’s say I’m working with vocal 2 vocal stems : dry vocal and vocal FX. I want to send the dry vocal to the stereo bus and the FX to an effet bus. If I use a group channel, I can’t really assign different outputs to each stems. Of course, you can always work out a send scheme, but it’s complicating the workflow. So VCA is the way to go.
And if it’s a pain in the ass in stereo, imagine in Atmos! Same exemple : if I use a group, I can’t for exemple sent the dry vocal to front Left-Right and the FX to Surround left and right. And managing the routing of a 100 tracks project with each or their send is just a complete nightmare.
The only way I got the VCA to work was to write a volume automation point on every track included in the VCA at the beginning of the track. That way, the balance isn’t ruined every time you load back the project. Hope this helps.
Curious. I just checked the behavior in C13 and it seem it has been fixed now? I can’t set the audio track back to zero anymore once the VCY is at a lower value. So it seems okay now.
As I can see the bug always remains.
- Write an automation with a VCA fader
- Activate “R” for the VCA fader
- Move the pointer to an location where the VCA fader is <> 0 and notice the value of the linked fader
- Press CMD-Q (Mac) and say “Save”
- Open the project again, the linked fader has another value then at 3.
My “solution” is to create for all VCA automationlanes a 0 at the start of the project and set the pointer to project start. After this I can save and quit.
Thats why I’m thinking the bug remains.
It’s never fixed since the new VCA function appear. They are thinking it is not a bug. I nearly forget that we have VCA track.
I just wish we still have traditional VCA track function which doesn’t create any additional volume line on the linked track.
The VCA-Fader Bug still exists in 13.0.40
They’re not even VCAs in the traditional sense. VCA Tracks in Cubase is basically linking tracks and adding a fader to the link group.
I too have chosen to forget about VCAs in Cubase. The benefits are not worth the headaches.
2 Likes
We still hope that sometimes it will be fixed. At this moment I use VCA only for controlling my volume of groups. Never used the automation on VCA…
The VCA-Fader Bug still exists in 13.0.50
I found some posts regarding to this bug six years ago 
1 Like
The VCA-Fader bug still exists in 14.0.5.
Why could this not be fixed?
3 Likes
It’s really bonkers that Steinberg allows this to go on year after year while charging for updates. No change in 14.0.10 as far as I could tell from the change log. Sessions MUST recall correctly after closing and reopening in a professional DAW. It is not an acceptable bug.
1 Like
I don’t know what’s going on at Steinberg. This bug is accepted by Steinberg, I called them via phone years ago and the guy told me, it’s fixed in the next maintenance update. As I wrote … years ago and nothing changed. Automated VCA faders are not usable since this feature was introduced. I like the new features in 14, but two points are ignored by Steinberg … this bug and the navigation in the MixConsole via mousewheel/trackpad. And the missing features for ARA, it’s not possible to drag an ARA event to a MIDI track which is standard in Logic and Studio One.
Out of ignorance, apologies: Why is the workaround of putting an automation point in each VCA- controlled track so onerous?
Thanks -
Wow, I actually just came here to check if anyone else is having the same problem as me, not the one mentioned in this thread…but now I’m a bit worried about what might be going on with all my tracks that are linked to VCAs, also grouped, and then sent to FX channels.
Anyway, the issue I came here for is this:
When I import tracks from another project — let’s say 6 tracks that were linked to a VCA — those tracks end up linked to an old VCA track in the new project, even if the VCA I’m importing has a completely different name. I don’t really understand why. Guessing a lot of people import tracks from old projects to compare. It doesn’t make sense.
Has anyone else seen this? Is there a reason this happens?
When I reopen my project in Cubase 14, all my audio track faders suddenly reset to -∞ dB (so not 0 dB, but completely down to silence).
I found VCA automation changing deliberately from 2017 describing something similar, but it makes me think I’m going crazy.
Setup details: Audio tracks are routed to groups. Each audio track is also linked to a VCA. Both the VCA and the audio tracks themselves have automation.
Everything worked fine until recently.
Now the strange part:
-
After one reopen, the faders were suddenly correct again.
-
But if I close and reopen the project again, all faders reset back to -∞ dB.
-
I’ve already rewritten the automation and reset the volumes about ten times by now.
Does anyone know what could have changed or caused this?
Well the fact is that if VCA are used in any capacity you need an automation point written on them lest fall victim to the dreaded suite of VCA bugs in Cubase. I’m sure that’s what you’re seeing there!
The better way is, Don’t use VCA….
3 Likes