I’m experiencing consistent “current-state memory loss” during sessions in Cubase that has now occurred across Cubase 13, 14, and 15, on three completely separate computers.
This is not project-specific and not related to CPU/RAM load. It happends in every project, always.
My system specifications are beyond what a “decent” system would be defined as.
examples:
VariAudio
The VariAudio editornever opens at the last viewed position
“Acoustic Feedback” is always reset to OFF, regardless of previous state
Editor does not retain its last-used context within the same session
Piano Roll
Modulation / Pitch Bend lane resets every time I leave and re-enter the editor
What makes this especially strange is that the behavior ** suddenly changes over long periods of time without any clear trigger**.
VariAudio example:
For a long time, VariAudio was consistently in the wrong state:
“Acoustic Feedback” always OFF
Editor opening at the wrong location
Required manual steps every single time (enable feedback, zoom out fully, relocate) - sometimes this works for a longer time though. It changes.
Then, for several months, VariAudio suddenly behaved correctly:
Acoustic Feedback stayed ON
Editor opened in the expected state
**Just a few days ago, it reverted back and →
Acoustic Feedback is OFF again every time
Editor state no longer persists
This happened:
Without changing projects
Without changing preferences
Without system or Cubase updates
Cubase 13, 14, and now 15
Across three different computers
The key issue:
It appears to drift or flip over time, independently of restarts or preference resets
Cubase behaves as if internal editor defaults are being silently re-selected
This makes the behavior:
Non-deterministic
Not reproducible via normal user actions
Extremely disruptive to my workflow (and sanity)
This cannot be narrowed down to issues with preferences / misconfiguration considering I’ve reset the preferences to “default” 200x times.
It feels more like internal editor state persistence breaking or being invalidated over time, with Cubase falling back to hidden defaults that the user cannot control.
Has anyone else experienced this long-term, drifting editor state behavior like this?
That’s insane, right? (I thought I was alone in this, lol! at last, a compadre)
Does Cubase actually remember editor settings during an active session?
For me, it very clearly does not.
Been using “Cubase Senile Issue” when talking to others — but at this point it’s less funny and more harmful to one’s sanity.
Working on a new template in 15, but encountering an old problem.
It’s a roll of the dice if your saved preset is going to show up in the list after you save your template. Sometimes a reboot brings it back. Sometimes you have to reinstall Media Bay to get it back. It’s been this for a few versions now, and infuriates me.
Generally there are two things that have an influence on the pervceived “memory loss”:
Silent crashes when quitting Cubase - as Cubase writes all changes to the preferences to disk during its quitting routine, such crashes can interrupt the process. Therefore your changes are not stored and thusly cannot be restored. Most often 3rd party components like plugins are causing the crashes.
Some settings are stored as part of the project and you might expect them to be stored as per workplace. Or vice versa.