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.
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.
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.
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.
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?
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.
I honestly can’t believe we’re in Nuendo/Cubase 14, with all the updates, upgrades, and brilliant advancements this DAW has gone through (and yes, it’s the best out there), and yet we still can’t undo the first added automation point on an empty volume curve. This is seriously frustrating. Like, very very very annoying.
You create one point on an empty automation lane by mistake and drag it – and boom, that’s it. No undo. You’re stuck. Why? Why is this still a thing?
It’s such a basic, fundamental behavior you’d expect to be handled a decade ago. They can fix it so easily… if they are not being able to undo the curve position maybe Nuendo could create a virtual hidden point in the background at the beginning of every track. A point we can’t see and click on, just to allow the undo system to actually revert to a previous state of that particular point. That can’t be hard to implement, right?
Is there a way to directly contact the developers? Maybe they’re not even aware this is still a problem. It’s one of those small things that ruins workflow and adds unnecessary headaches in high-pressure situations.
For me, the problem is that I sometimes don’t notice the problem right away. If it’s sometime later before I notice, doing any undos won’t help.
I think problem is that it’s too easy to edit automation accidentally. I deal with this by keeping automation lanes locked except when I want to edit them.
I think there actually is. I haven’t seen it announced officially but I am able to undo a first set automation point and the parameter will revert to the previous no-automation-point-was-set-value. Version 15.0.30.
I did not test it extensively, though. No idea if it will work in all kinds of weather.
I suspect most people here are like me and used up their votes long ago. If you look at the top vote getting feature requests, they are all very old. Many of them are marked “Cubase 10”.
I agree with Johnny, undo works fine for me when I accidentally click on an unlocked automation lane.
As I mentioned though, IMHO undo is an ineffective fix since it requires that i notice it right away. What’s needed is a better way to prevent the accidental edits in the first place. For example, maybe the lane needs to be selected before any edits can be made?
But to be fair, there are a lot of topics regarding accidental set automation points.
From the back of my memories I think there was a solution for the origin problem, but can’t remember which setting it was. And there were other restrictions related to it.
But it’s good that the undo problem got a fix, somehow.
It does seem this feature request was finally implemented.
Many thanks to the OP who took the time to search out all the threads and amalgamate them into one to show and the convince the devs that this is worth considering and a problem encountered by many users.
I wish there was a thread that focused on nothing but these types of small things amalgamated into one place…
But perhaps this thread can now be marked [Achieved]