Intel Mac with Monterey here and I’m finding a heap of projects with varying plugins (UAD, Softube are my most used) are getting to a certain point in playback and crashing perfectly at that point every time in Cubase 12, (with the crash log mostly blaming a random/never the same plugin… however sometimes it blames the Cubase 12 app itself).
On the same machine I can open that project in Cubase 11 and it performs perfectly.
In Cubase 12, I’ve tried using ASIO switching on/off, both versions are using the same buffer settings (2048) … there are no spikes happening when the crash happens - the app just disappears with the crash notification popping up shortly after.
I’ve been sending the cash logs in to Steinberg with the feature included on the load up screen after a crash … but wonder how I can report this in a meaningful manner so that it can be resolved?
I don’t have any blacklisted or out of date plugins being used in the project … they’re all qualified for Monterey (and again working fine in Cubase 11 on the same machine).
I’ve also sent the logs to Softube (of which I’m using the latest Monterey approved version) when they are blamed (curious that they work flawlessly in Cubase 11 though) and Yamaha Australia are the ‘support’ option here … and they have way too many things to consider to be able to offer decent Steinberg support. Most of the time I post a request it just gets ignored completely.
The Cubase 12-2022-03-18-185804.ips comes from Cubase. Do you have any idea, what did you do in this case, please?
Because is developing. It might be, there was a bug in Cubase 11, which allowed to do something in the plug-in code, what was wrong. And this bug has been fixed in Cubase 12. This might be one explanation. Or Cubase added a feature, which is incompatible with some plug-ins code.
this is a nightmare my mastering chain is down addictive drums 2 wont work im not an it guru i just paid and want it to work its 22 this really is crap guys most unstable version since 9 your going backwards