Good evening everyone. I’d like to check if others are experiencing similar issues and if anyone has a solution or a workaround for this:
At some point (not always, it usually works fine after opening a project), fader movements stop being registered. I click cmd+Z and, instead of undoing my last fader movement (or some other operation) a plugin I inserted earlier is removed (many times I have a hard time keeping track of which plugin was removed). I click cmd+shift+Z to restore the removed plugin and its settings are lost (which sucks big time…).
I’ve seen old threads where people complained about similar things regarding mixer history. I think this was working fine (better, at least) when I was in Cubase 12.
Any suggestion is appreciated.
Running Cubase 15.0.30 on OSX 13.5.2 Ventura.
I’ve seen MixConsole history issues occasionally (on Windows 11 with Cubase 15.0.30 – I don’t recall if I saw it in earlier versions of Cubase or when I was still on Windows 10) – I’m not sure how frequently, but certainly more than once or twice, but also not in every session (or probably even once a week). Unfortunately, it seems to happen randomly enough, that I’ve never detected a pattern, unless it is simply that it tends to happen after the specific Cubase session has been going for a while. But I’m typically in the same session in Cubase for anywhere from two to six (sometimes even more) hours when I’m using it, even if there may be some interruptions along the way.
I’ve noticed it in many different contexts within the MixConsole history, probably including the fader scenario you mention, but also plugin setting changes, panner changes (both value changes and changes of panner type). The best guesses I have on potential for patterns would be amount of time in a session and/or making a lot of changes, such as auditioning lots of different plugins in the course of deciding on which ones to use in a particular context – something I tend to do quite a bit of when I get to the mixing stage of a project). Another possibility might be use of specific plugins (or perhaps families of plugins) as I’ve noticed some Q-Link changes that should percolate across multiple instances of plugins on selected tracks do not, though I don’t know if that behavior is consistent or only happens in some scenarios (I think the most recent time I noticed that sort of thing in Q-Link may have involved Waves Vocal Rider and/or Waves Tune Real Time, and maybe one did make the changes across the multiple instances while the other didn’t).
I have not used shortcut keys for MixConsole undo/redo (Alt-Z and Alt-Shift-Z on Windows). I always keep the MixConsole up on my second monitor and look at the history to roll back based on what is I see there as I otherwise wouldn’t know how many steps to go back (it’s rarely just one step I want to go back), and I often roll forward and backward as part of auditioning the differences.
Being able to see these also is sometimes what alerts me that the history is no longer collecting transactions (or at least has missed some I’ve done – maybe it does resume after a point).
Thank you for chiming in in such a detailed manner, rickpaul. Knowing about your experience gave me some ideas to work around this issue. I mix for a living, so yeah, I’m running projects for many hours and I notice mixconsole history to start acting weirdly after some time (hours, probably). Rebooting the project or Cubase itself probably gets it back to normal. I use undo/redo in the mixconsole extensively, as an AB tool most of the time, and I do use the default shortcuts. I prefer having the left zone in mymixconsole hiden, but I see keeping an eye on history may work as a warning.
Q-Link has many issues too, unfortunately. It worked flawlessly for me in Cubase 12, not anymore…