I was displeased to find this bug had managed to carry itself across to the Apple Silicon port. A lot, if not the majority, of Cubase crashes, sudden exits, and failures to close, are related to buggy plugins. Many plugins aren’t the best in terms of coding practices. Often devs just tick the “export to VST3” option with JUCE etc and call it job done. They do NO proper testing inside of Cubase. So, if it’s happening often, you need to start looking at the plugins you use.And why does Cubase not let go of some audio when trying to quit the program, always having to 'end task'
If you leave plugins running for many days of uptime it also reveals just how many have issues. Wrapped plugins, and tickbox exporting to VST3, tends to do worse in terms of longer uptime stability. But even Steinberg’s own VST3 plugins are guilty - EG I’ve had Backbone bring down Cubase 13, and I’ve seen many complaints about Groove Agent 5 in their forums. Plus they’re in no position to tell devs to write to VST3 natively when even Steinberg wraps (Their AU plugins are really wrapped VST3’s).
Whilst you can blame the plugins, and be correct, the fault is really with Cubase IMO. It’s failing to properly isolate itself from plugins crashing and causing other weird bugs (like difficulty exiting, likely due to things like being unable to deallocate memory). This is my main gripe with the program, and I really don’t get why Steinberg haven’t made major changes already, instead of spending resources working on native Windows on ARM. You’d think fixing the basic stability of their host would be their top priority, but apparently not.
Most users will blame the host for any crashes. So, ultimately, it only makes Steinberg / Yamaha look bad.
Statistics: Posted by PAK — Sat Oct 26, 2024 6:43 am