When automation was written for the Chorus one automation point was written at the beginning of the timeline. That automation point is the same value as the first point written in the chorus - in this case -3dB. So when you started playback the second time it read that very first data point.
guess what, that’s because you didn’t wrote your volume change, you changed it before writing…
So it should actually be entirely predictable. If you move the fader outside of where automation exists, then it stays where you left it. Once you read automation though - in the chorus that you automated - it’ll stay at the last value of that written automation (-6dB). Here’s an example:
?? hum… so cubase must know what value is before the automation… what you doesn’t understand is that they made a good job : when you write the volume change (not setting it before writing, WRITING IT) cubase insert a volume info at the very begining of your project, so this behave as you wanted, the only thing that is wrong with your method, is that you don’t write your automation, you write a static volume for the chorus, which then apply from the begining to the moment you started writing. If you hade written a volume change which passes from -10 to -3 just at the moment of the chorus, you will have -10 on the verse, as you wanted… no problem at all…
VT: ON, automation -3dB at chorus.
Intro: You move the fader to -10dB and let go.
Verse: -10dB
Chorus: -3dB (automation read)
Verse: -3dB
Outro: You move the fader to -7dB where it remains until you press stop.
lol, yes when you press stop it jumps to -3 because you moved your fader in read mode… not writing… if you wrote automation your fader wouldn’t have jumped to -3… again, if you want your automation to repeat the volume changes (moves) you make, you have to “record” automation…
So as you can see the purpose of VT is not to make your levels 100% repeatable, for that you need to write automation either throughout all VT, or not use VT at all. Instead it’s so that you can avoid having to disable automation read every time you want to experiment with a section. So in the above example when you have already written the chorus automation, you end up with the same experience automating the verse. You can just move parameters around without them “snapping” to pre-recorded automation values. Then you punch that automation in for the verse and move on to the next section.
totally wrong !!