This bug has been around awhile now. After writing track automation, the undo function stops working. Automation points cannot be selected. The undo history can be seen but you cannot click anywhere in it to revert any actions. Only a restart solves the problem. Mac OS Ventura on Studio M1 Ultra. Cubase 13.
Hi,
If I understand your description, it’s not about the Undo. The whole application freezes. Am I right?
Are you on Windows or Mac? Which version?
Which automation parameter did you write? How did you write it (from the GUI or any hardware controller; which one)?
The application behaves fine except for the undo ceasing to work and I’m unable to edit any automation. Nor does Cubase follow the automation any more.
Working on Mac Studio M1 Ultra with OS Ventura.
From what I can see with other users that have the same issue it’s been narrowed down to writing automation after switching between active projects.
It happens when I write with a modwheel on a keyboard EDIT: fader on an external surface (Avid Artist Mix) or for instance when I write by scrolling the mouse wheel over a send.
Restarting the app solves the problem.
Hi,
Could you link the other posts, please?
Do you record Modwheel MIDI data, or do you use Quick Controls to assign the Modwheel to any parameter?
Actually I meant to say writing automation with a fader on an external surface (in this case Avid Artist) or when writing it with a mouse wheel. NOT, Modwheel. Always has to do with track automation, not MIDI cc data.
Hi,
I tried these steps:
But it works for me as expected (I can Undo it) in Cubase 12.0.70 and Cubase 13.0.10.
That may not have been the correct post to link. In any event, I’m still having the above behavior. I will try and build a reproducible method and get back to you. But it’s been happening since 12.
Ok - so the way I can reproduce it is open a suitably large session. My session size is around 400+MB due to lots of Kontakt in the template. After that, any session you open afterward and write in automation will result in the undo function ceasing to work and the track won’t read any automation. Even if you create an empty session and record automation on a new blank track, undo stops working.
I have a screen recording but due to it being an active project I can’t post it publicly without blurring some stuff.
I could not trigger it with smaller session sizes. Only by opening a large session.
Yes you can undo it, but the volume value change remains. A newly created track always has its volume at 0. If you then draw the first automation point and drag it down to lets say -10, you can just undo the creation of the automation point, the volume will stay at -10 and there is no way it jumps back to 0.
Hi,
No, the value change is undone. See attached video, please.
There may have been a misunderstanding. You have to draw the first point and without letting the mouse go, drag it down or up. In that case the volume change cannot be undone in any way, as demonstrated in the video of my issue report here:
The idea behind this issue report is, that if you change the volume of a track by dragging down (or up) an automation point accidentally when moving through your project or wanting to select anything, you cannot undo it. You will never know what the previous value was and Cubase also doesn’t let you get back to the volume you once had.
No. You always klick, let go and then you drag the point. Please watch the video I posted.
You have to clickdrag in 1 go in order to reproduce the issue, the same mouse actions you would do when e.g. selecting events.
There is also an extended discussion of this issue in the thread here:
Undo does not work, when inserting first automation point - Cubase - Steinberg Forums
Hi,
Sorry, the video is not available.
I see, so you do it in one go. Just click and drag to set the value. OK, now I can reproduce it. From Cubase point of view, this is just one step.
Yes at the moment Cubase only sees it as one step, but in reality it is two steps:
- Creating Automation point
- Altering volume
But only “creating automation point” will be recognized as action, and the volume change is left out.
This can cause accidental volume changes in projects, which cannot be undone and are therefore an issue. To work around it, I lock every automation channel per default, but that cannot be the solution for a software like Cubase.
Hi,
Cubase is taking it as one step: “Create Automation Node of Value x”.
Yes and that is an issue. Because that way we have no chance to get back to the original value and potentially mess up the settings in our projects.
Or is there a solution to that?
Hi,
The original value is the one, you inserted. What would you expect as the original value, please?
The previous one.
Real life example:
You have a project with various different instruments and you put quite some effort into balancing out the levels. You found the bass group works best at the volume of -12,5dB.
Now you want to select all the bass audio tracks below to move them horizontally, but instead of click/selecting into a free area you accidentally clicked into the volume automation lane.
The bass group has now a volume of -32,3 dB. You noticed it immediately and want to jump back to the previous original value of the bass group, but when hitting undo only the automation point disappears.
Obviously you don’t remember the exact volume values of each track, so the only thing you can do is open an older .bak or project file and hope it is the correct value.
Hi,
You mean the value of the previous node, correct?
So you didn’t have any automation node in the Automation Track before, right? Why is the Automation Track expanded then?
Sorry, I really try to understand the use case.