How is that Automation-Mode called?

I have a question.

In Nuendo I am used to have everything set up in a way that parameters (faders, sends etc) automatically snap back to the previous value after I stopped writing automation. Either when just riding a fader (maybe it was at 0db - then I ride it to -10 db, release the fader - then the fader snaps back to 0db, drawing the automation back to 0db as well) or when using the pencil to “draw” automation.

Now I am messing around in Cubase and I am not able to re-create that setup - when I release the fader or stop drawing with the pencil the fader or the line just stays there… so when I was at 0db before and I stopped writing at -10 db the track now remains at -10 db and I have to manually edit the automation to go back to the initial value…

I compared how I set up Nuendo and Cubase and can’t find the culprit…


If I remember well, there has been a change in the early days when Cubase enherited the Nuendo automation.
Cubase users go so used to the way it used to be in the “old” automation.
To satisfy the users they removed one of the functions which made the Cubase automation act -more or less- as if “to end” was permanently activated. Don’t know if this is still the case today though …

I think you can solve the problem by executing a “set initial parameters”.

But I’m not 100% sure about this …


Mh… yes that “initial parameter” thing was my workaround (doing this by hand) in very old days… in combi with putting an automation dot in the very end… that way I was able to use wildest gain riding without messing with the mix.

I prefer the Nuendo way. The Cubase way just feels “incomplete” in my opinion.

It is so fast just hold down alt and then quickly draw a “tomfill” or a “snare hit”. Gainriding is so important.

I hope to find a solution here.

So there isn’t a"touch" automation in Cubase? :open_mouth:

Of course it is but After that the fader (of what else I am riding) is not snapping back to its initial value… Instead it stays were I released it.

Ain’t that “latch” or “write” automation?
I hope I’m not missing something here?

mh I tried everything - maybe I missed something here. I will check out again!

ITM I am mixing in N6.5 because it feels so “home-sweet-home” :slight_smile:

Touch automation works so that when you crap for example a fader it starts to write automation for your fader ride. When you let go of the fader it returns to previously written automation values.
Latch automation works so that when you crap a fader it starts to write automation as in touch mode. But when you let go the fader it stays where you left it writing straight line to automation until you stop playback and then snaps to previously written automation values.
Please someone correct me if needed :wink:

Yes - when I insert one single automation note somewhere in the end (Cubase) the automation behaves exactly like that. But when I use a new track - no automation yet - just enable “write” and crap the fader - then Cubase and Nuendo behave different - Nuendo always returns to the previous value… In Cubase it stays where I let the fader go.


Brandy, I don’t have Cubase, but does this section of the manual from N6 not apply to your Cubase ??

The initial value
An initial value is always used when “Use Virgin Territory” is disabled in the Automation Settings (see “Automation Preferences” on page 341).
When no automation data exists for a particular parameter, the starting point of an automation pass is saved as the initial value. When you punch out of the automation pass, it is this initial value to which the parameter will return.
This has one very important consequence: As soon as the initial value is set, the corresponding parameter is fully automated for the complete track, at any given timecode position of the project – even if your automation pass lasted only 2 seconds.
The straight line after the last automation event corresponds with the initial value.
When you release a control, it returns to the value defined by the automation curve – even when in Stop mode.

The Virgin Territory made some confusion when it arrived in Nuendo back in the days as well.