I think this FR needs more attention 'Properly Undo First Added Automation Point'

It just happened to me in a really annoying way, and in front of the client.

Sometimes you’re mousing around, and accidently click in an automation lane, or, you think you want to do some automation and then decide not to…

That first automation point will not return to the initial fader value if you undo it. And sometimes, mixer undo isn’t dependable in this instance if you’ve done mixer changes since the automation point went in.

Drawing automation and Undoing it doesn’t revert fader to original volume - Nuendo - Steinberg Forums

Unable to undo accidental automation change to a group volume - Cubase - Steinberg Forums

Undoing - - First - - Automation point should return fader/parameter back to previous position - Cubase - Steinberg Forums

Thanks dev team

I do agree, if you create an automation point, the undo of this should (no it must) lead to the last state before the creation.
Otherwise, it is not undoing something.

I don’t see this as a feature request, it is an issue, that needs fixing.

1 Like

Is it possible to undo accidental group track volume point and drag error? - Cubase - Steinberg Forums
@Nuieve

1vote
Undoing - - First - - Automation point should return fader/parameter back to previous position - Cubase - Steinberg Forums
@vncvr

2 votes
Urgent: Undo accidental change to empty volume automation curves! - Cubase - Steinberg Forums
@tonyreign

1vote
Accidental automation clicking is annoying! - Cubase - Steinberg Forums
@blamamate

Drawing automation and Undoing it doesn’t revert fader to original volume - Nuendo - Steinberg Forums
@snattack

Undo group or fx volume change automation bug
@Nuieve

2 votes
Unable to undo accidental automation change to a group volume - Cubase - Steinberg Forums
@Nuieve

6 votes total with many +1s

YES!!! It’s the most annoying thing in Cubase.

No matter how careful you are, it happens at some point.
Sometimes I do it and I don’t even realise until I hear that something is messed up, because it’s a section that I’m not listening to right now.

Unfortunately amount of points to give is extremely limited on this forum (my another complaint). Otherwise I would give it here.

Btw all those topics should be merged.

Yes not enough votes,

and they also should merge the votes when they merge the thread - I think @Romantique_Tp is a mod… maybe if we bring to their attention.

It’s a very annoying problem, even 0.5db can make a difference in the mix if you have some kind of OTT process or heavy compression on the master bus - that 0.5db makes a difference, so just putting the fader back to ballpark never feels like you’ve restored your mix.

Sometimes, the only way to get it back - is to save a new version if you’ve caught the mistake in time, and then re-open the previous cpr, or revert to an older one.

Very annoying.

@battleangel
you may also find this annoying if you use automation at all
Automation FR: Preference to resolve automation scaling creating unwanted nodes - Cubase - Steinberg Forums

1 Like

agreed, it’s annoying

1 Like

The other annoying issue is when you try to undo plugin changes from mixing history it gives that “if you do this, all automation data will be lost”. Like, all of it. Not just that one plugin. Even plugins not affected by the plugin being undone. Just nukes all the automation for that track.

What? Can’t undo automation data? What is it with Cubase and having this buggy crippled automation system?

Why such terrible programming? How can this be ok?

Sorry for the late reply.

I think attempting to merge all those topics at this point would create a huge mess, but I’ll see what can be done. We probably don’t need so many separate topics on the same subject.

That said, I’m fairly certain that Steinberg is aware that a few aspects of the Automation system could be improved upon, especially this, which is a common request as you’ve shown. Since Automation is such an important part of both Cubase and Nuendo, any changes to how it works have to be done carefully.