There are other threads about the issues, and I’ve confirmed that one, at least, is definitely specific to my system for some reason. Even though I still won’t go back to C15 until a certain couple of issues it has are fixed (look for the threads, this one is not about that), I want to get this solved:
C15 is having an issue that it seems other users aren’t, who are also on the Mac (Sonoma or Sequoia…the issue persisted in both).
I’ve tried:
Opening C15 without plugins and/or preferences.
Re-installing C15.
Haven’t had any responses from Steinberg support, for this or a few other things. What’s left for me to try, aside from a clean-slate wipe of the Mac which I don’t have time for because of jobs in-progress?
You can call the office: They are actually very good at helping people. I don’t have the number handy, but if it is for your work, it is worth a try
Backup now: Please make a bootable clone of your system disk immediately using SuperDuper! or Carbon Copy Cloner
stick with Cubase 14: I am still using 14 because it is much more stable. Don’t let the YouTube videos for version 15 tempt you; updates often cause these issues. Many professional producers stay on old versions just because they work perfectly.
I really hope you can get this fixed soon!
I tried C15 and went back to C14, the first time I’ve done that in Cubase history. I didn’t have any crashes or anything like that, but a few of the issues get in the way in a significant way that it’s not worth the tradeoff until they’re fixed.
One thing I would do is give Cubase full disk access (Settings/Privacy & Security/Full Disk Access), then do a full restart.
I had wacky behaviour before I did that. Cubase has files strewn all over the disk. Really, when you get really deep, as I did when I was trying to figure out all the places that get used for preset saving, it’s shocking that the thing works at all. Mostly the result of decades of development of differing OS structures and approaches (not throwing rocks here or anything)
Another thing to do is create a new user (you can delete it after you figure out what’s going on) and try to launch Cubase and see what the effects are.
Don’t forget, poorly written plugins can have bizarre effects even when not enabled.
There are programs like OwlPlug, that scan all your various plug folders (more than you’d think) and lets’ you see and disable them.
I was quite excited about OwlPlug as it was something I was thinking of coding myself, but it’s kinda not really been great. Better than nothing tho.
I think there are a couple of other Apps that will do that on a Mac, but the coffee hasn’t really kicked in yet and brain work not good.
And, you can always try to temporarily disconnect any non-critical USB or Thunderbolt devices - they can do things you wouldn’t expect.
When editing multiple parts at the same time in the piano roll editor, some notes remain black that aren’t selected, which makes editing impossible in that situation. I use this all of the time in my scoring.
Yeah I bet that’s it, the plugin thing. Damn, it will take a long time to isolate. When these next jobs let up I’ll go through them. Thanks for the help!