How the VST host is implemented leaves some space for own ideas. Some DAWs (I know this about Bitwig) running plugins in a sandbox. So there is a good chance you will never see such a plugin crashing and if it crashed if will not crash the DAW... The exception handling seems also to be very different. Cubase seems to have a not so good exception handling so it's very easy to crash the complete DAW without giving the user some feedback or try to avoid the crash.chk071 wrote:I often read that. But imagine plugin XY crashes one host, but works perfectly on another. Is it really the plugin's fault then? I mean, obviously it seems the VST implementation, or something else about the DAW, maybe the way the graphical interface is done, seems to differ, otherwise one plugin wouldn't crash the one, but not the other? Really always the plugin's fault?4damind wrote: IMO 99% of all crashes are because of poor implemented plugins
We know that Reaper is well known to be very stable and people often say they can run more plugins on the same machine compared to other DAWs. It's closed source so nobody knows how stuff is implemented but IMO there must be something completely different compared to Cubase.
For the graphic stuff... there are some known problems with some plugins using opengl/Directx for rendering their controls in combination with some GPUs. Waves had such a problem sometimes back and there are still sometimes problems while moving the mouse over some Waves plugins (lots of dropouts) Afaik in combination with the Intel HD4000 (IMO some 3D functions are not hardware accelerated and emulated with software with some GPUs)
So yes, I would say it's most of the time because of not very good implemented plugins or that a plugin is using some very special features (eg. of the opengl/3d API).