Reproducible VCA Automation Bug Cubase 12.0.52

It is. Well, traffic’s slow this time of the year, I know what I’ll be doing at work tomorrow…

1 Like

This bug has been around for a bit I think and has been reported before…

3 Likes

That is exactly the issue I am facing too. And able to reproduce!

Cubase Pro 12.0.52 Build 393
Win 11 Pro 22H2
Windows Feature Experience Pack 1000.22638.1000.0


1 Like

Just an update here, from deep within the rabbit hole.

No solution in sight. I won’t bore you with which actions of mine had no effect, however I can now cause this from within Cubase, not only on a first boot-up, but any time, simply by switching between projects (activating them), and strategically placing my cursor between the switch. I can’t wait to get home to my unaffected system to see if I can trigger this.

I’ll write down my test right below, if anyone wants to give it a go, I won’t be able to test this for at least 4 hours.



Setup two projects

Project A

  1. Create 4 Audio Tracks Connected to a Single VCA Fader, all faders at unity gain.

  2. Create automation points on the VCA track as follows.
    Bar 0: 0.0
    Bar 1: +1.0
    Bar 2: +2.0
    Bar 3: +3.0
    Bar 4: +4.0
    Bar 5: +5.0
    Bar 6: +6.0

  3. Set the playback cursor to bar 0. Don’t close the project. Create a new project:

Project B

A completely blank project

perform this Repro sequence:

  1. Activate project B. Place the playback cursor at bar 3.
  2. Go to project A and activate it. Open the mixconsole.
  3. Observe if the VCA fader is at unity gain, but the audio faders are positioned at -3dB.


Edit: Just reproduced on my main system! @fese, can you give the test a go and see if this method causes it for you too?
Actually, anyone? @Thomas_127 , @jim_griff , @Pablin_Drummer

3 Likes

Yes, I can reproduce it with that sequence. Seriously weird.
If I create the new project and immediately activate project A, everything is fine. As soon as I move the playhead in project B or let it play, it starts reducing the fader level, and if I then switch back and forth between B and A, for every switch the level of the audio faders decreases more.
Brainfart!

2 Likes

Great! Well, not great, you understand what I mean. :grin:

I don’t know the exact order that the mixconsole loads the channels, but it seems to me that there’s some double dipping going on here. (Faders get a value assigned before the cursor locates, vca gets the correct value for THAT wrong position, then the cursor returns to the correct position for the project, but the faders are affected by the VCA, dropping by the amount specified by the automation curve.

I honestly don’t know how one can formulate this in a sentence that makes sense. :rofl: I hope that the reproduction sequence is true, because it’s much easier to understand when you see it.

@steve, I think we’ve got it.

2 Likes

@ggmanestraki
100% reproduced the bug using your Project A / Project B switching thing.

1 Like

@ggmanestraki
Confirmed. Exactly the same behaviour here.

1 Like

Excellent. Will report. (again?)
:carrot:

4 Likes
Side-effect

There are some side-effects stemming from this behaviour. One that has caught my eye is that some users were complaining that their mixconsole was “locked up”. It seems that when the offset between the VCA and the audio tracks causes the audio tracks to get fader level values over 6.02, the faders get pegged in that position, and you can’t just enter a value in the box by keyboard, entry is locked. You have to manually grab the fader with the mouse and lower it.

A workaround for the time being is to write automation for the audio tracks. Even just one value for a static mix.

1 Like