I don't think I've ever gotten Cubase to crash on me. I use it as a production DAW. I have gotten Studio One to crash on me... a lot. Just removing plug-ins sometimes would cause a crash. I haven't testsed 5.4 to see if that fixes these issues, as I only use it as a backup on my laptop.jancivil wrote: Sun Sep 12, 2021 4:08 pmthis is so true, really. 11 is not real stable, 11.1 less so, .2 and .3 less so still here.Scotty wrote: Sun Sep 12, 2021 10:20 amAs of late Steinberg has been releasing buggier updates with inadequate testing. They do a great job of eliminating major bugs and you can do professional work with it. Regardless it is a stunning achievement. They are slipping lately. 11 is still not solid for many people and it cant all be dismissed as user error.
I have eliminated one user error (leaving the OS to do automatic graphics switching) but still insane crashes.
(One li'l dude at their forum accuses everyone of having problems with their system, hardware faults ad naus. If I had that quality of problem I wouldn't have Resolve and FCPX rendering at superspeed and being 100% reliable, would I.)
Most of which are hit play and boom, there it goes. Which isn't about pushing the number crunching being impatient, it can be I haven't touched anything for a whole minute, spacebar-play and bam.
It's not from plugins in all probability, as I don't use it to host them mostly, and it's a couple of things inserted in audio channels, half of this is theirs (Frequency). I can't just take VE Pro out of the equation, and it's highly doubtful this is causal at all afaic. Instead of testing they do other things with their time.
But crossing over into another DAW, I can't afford it time-wise or justify the money. And there are features I absolutely rely upon which the others don't do or don't do it with the same ease.
But Cubase? I can't remember the last time that crashed on me, and I'm fairly certain Cubase 11 Pro has literally never crashed or frozen up on me... like, ever.
One thing that needs to be stated, is that DAW crashes are often caused more by things you bring to the table than the DAW itself. Bugs in plug-ins can seem like bugs in the DAW, because different DAWs will react to bugginess differently. This is why Bitwig has a jail for VST plug-ins. It's a newer DAW, and they understand just how much of an issue this is.
I tend to stick to "bigger" names when it comes to plug-ins and virtual instruments (iZotope, Softube, Native Instruments, East West, etc.), [largely] to avoid having to deal with bugginess introduced by plug-ins from smaller developers and/or the internet's chest of freebies (which are generally badly supported - or, at least, often have badly prioritized support strategies).
For example I stopped using all Waves plug-ins because WaveShell was a pretty universal source of problems across multiple DAWs.
I also tend to avoid VST2 whenever possible, hiding/disabling those versions and using VST3 instead (some DAWs will auto-hide [most] VST2 plug-ins when both are installed). For some reason - and this may be anecdotal - but I notice the VST2 plug-ins just seem to be more problematic than VST3 - except in a DAW like Samplitude Pro X, where the VST3 support is hogwash (so you should always default to VST2 in that software).
This is some of the most ignorant stuff I've ever read. There was a time when enabling SMT on a system would cause problems in MANY DAWs, while it was optimal to leave this enabled for Video Editing Software.If I had that quality of problem I wouldn't have Resolve and FCPX rendering at superspeed and being 100% reliable, would I.
These are two different classes of software - each with their own requirements, as well as with their own Achilles Heels. For example, having a weak GPU will destroy performance in DaVinci Resolve, while Cubase will happily run at full speed off of integrated graphics.
Beyond that, the type of complex routing that people do with DAWs is often not done with NLEs - especially by amateur video editors or content creators. The Computational and Compute power needed by NLEs has more to do with the kind of footage they work with, as well as the type of processing jobs plug-ins in that domain perform.
Editors aren't generally running video editing sessions with hundreds of instances of VST plug-ins form disparate manufacturers loaded, multi-timbral samplers, synths and virtual instruments, etc. However, the Noise Reduction Plug-ins alone use as much CPU (and RAM) as multiple synth VSTis combined...
There simply are more avenues for failure with a DAW. Many YouTubers can get by with using only 1st party effects, or solutions tested and designed to work in concert with their choice of NLE (i.e. Final Cut Pro + Motion + Compressor). Music Producers and other DAW users tend to get solutions from lots of different vendors, and this all complicates the issue.
There is a reason why the Fairlight Page has tended to be one of the buggiest parts of the Resolve application - with some of the hardest to resolve bugs - pun unintended...
