Yeah, don’t know what to tell you, really. It’s exactly what I did. I even re-did the test before when you said you could reproduce it. I just can’t. When I re-open the project with the cursor parked at -infinity the audio track is at -infinity as well, and when I move the playback head to the top of the timeline the VCA reads unity and the audio track -10dB. I’ll check a third time, but if that doesn’t produce the error I can’t really see that there’s a general problem.
It just seems to work on my end. No idea what the difference is between our setups.
I have the latest demo version of Nuendo 10, and I’m running Windows 10, build 17763.
Surely they’ve seen this thread and are aware of this and are just face palming themselves so hard they can’t reply.
I bet you it’s not a simple thing to fix, to not break compatibility with peoples previous projects… Like, it’'s the kind of thing you want to get right on first release…
“Track is now at 0, not -10.” Same as before. But also;
On punch-out there’s the ramp back up to the “first” value, which was -10. However, it’s as if that is written as if the fill option “to end” was enabled.
In contrast, with Virgin Territory turned ON and NO link to a VCA (still with no automation written to it) the behavior is as expected, with the last automation node being wherever the fader was when it was no longer touched, and AFTER that node there is again virgin territory.
To see the difference just execute the test as Hugh wrote it out with and without VT enabled and watch the result.