Why does Cubase act strangely for me sometimes. Like I was just playing a song and I soloed a track and then un-soloed the track. Even though I pressed the un-solo button, Cubase wouldn’t un-solo until I opened up the soloed track in the key editor and unchecked the “solo editor” button. Or I had this other time yesterday when I when I was working with variaudio data and a large spike (infinitely tall) in the inflexion curve occurred. When I moved the note where the spike was up and down, I could see a little orange curve that looked more like the real position where the curve was supposed to be, but when I settled the note back in the original position the huge spike remained. And sometimes Cubase forgets my workspaces, once it forgot all my settings, once it didn’t load the video player properly, it almost always forgets my vst connections when I switch interfaces, etc… Oh and when I monitor a track with the deesser plugin, why is there always a huge amount of latency, even with the plugin switched off, and only (as far as I can tell) when I monitor?
Once I had recorded a section of midi on a track, and when I pressed the play button and played my keyboard, the program behaved as if the sustain pedal was being held down, but when I paused it and played my keyboard, the program acted as it should. My question is, what the heck!!! And I just keep on getting these weird irreproducible bugs and problems. Is this something related to my program being run on a 32 bit system? If it is, Steinberg is biasing its developers to work on one version more than another, and this is not good.
I never had these sorts of problems with Pro Tools. Even though it was sort of inefficient, it never had this many terrible random bugs and problems. What do I do, what option do I have, other than to ditch Steinberg?
Any solutions or help?