C12.0 ignores single automation data point

After listening to my song many times with all tracks playing correctly, suddenly I noticed that I couldn’t hear a particular guitar track and the reason was that the volume fader was at .oo (off) although the automation point was still there to increase the volume to the correct level but it was being ignored (every time I played it).
So I had to add multiple automation points for Cubase not to ignore same then it works fine.

See the image that shows the first single data point (ignored) and the multiple points (not ignored).

Has anyone else experienced this please?

I’ve just boght C13 but will only install when I upgrade my PC in a few months time. I hope it’s sorted in C13 version.

Hi,

On the screenshot, I see the value -11.7, so it’s not -oo.

Why do you use the Virgin Territory?

Hi Martin,

Thanks for your quick response!

Sorry, I should have been more pro-active in choosing the screenshot. I’ve retaken it with a more useful transport position in between the singular data point and the multiple where you can see the fader is on -oo .
So now comparing the 2 screenshots you can see the issue more clearly.

Regarding virgin territory. To be honest I don’t really understand the difference in the on or off settings in the automation settings panel. I’ve read the manual but would love to see a working example of the difference, perhaps by Gregg Ondo in one of the live session videos if you happen to know of a link please? Otherwise I’ll search YouTube later for same.

Do you think my issue is a bug?
Or is it normal with ‘virgin territory’ ticked for it to ignore the single data point - I assume not as it’s been working fine until recently so maybe there’s something else I’ve changed that could cause that. I haven’t muted the read automation lane, obviously as it reads the multiple data points.

Happens to me every now and then when copying or moving stuff arround. But usually I just delete the point that “ends” the automation line and then it the line continues and the automation works.

That is super simple:
With Virgin Territory active
grafik
You create a single automation point. The value will be valid exactly only at that position, while left and right of it the value will be “nothing” (which on volume is -∞).

Without Virgin Territory active:
grafik
Left and right of automation nodes are also values.

Personally I would leave Virgin Territory switched off until you find a very good reason to use it.

Hi @Johnny_Moneto
Many thanks! That’s such a super clear answer.
Why can’t the Steinberg manual use such clear wording?
Maybe they do in German :slight_smile:

I seem to remember another thread a year or so ago that gave me a good reason to turn ‘virgin territory’ on but as I can’t remember what it was, I’ll leave it off now but I should check all tracks in my project for any adverse affects of the change I suppose. I was going to have to do this anyway as it wasn’t working correctly with it ticked :slight_smile: