As a user but also a VST developer that is totally tired of crappy plugins not working in perfectly well behaving hosts (not to mention software in general crashing randomly), I must disagree, at least when it comes to the serious, widely used hosts.Shy wrote:Actually it's not just VST plugins' fault. Hosts are causing major problems to VSTs that VST developers have to work around or wait for host developers to fix.
Honestly, every time I've seen my own plugins crash or otherwise misbehave in some host, I've been able to trace it down to a bug my own plugins. Every damn single time, no matter how much it looked like a host issue. Not just crash bugs, but automation bugs, project recall failure, timing issues, you name it. As long as some other plugin doesn't have an issue in the same host, doing the same thing, you probably have a plugin bug (or a "developer" that cares more about the RightThing(tm) than trying to live in the real world).
There sure might be some set of VST plugins that simply need functionality that some hosts can't provide, and there sure might be some set of hosts that are so buggy themselves that even well behaving plugins won't work, but in most cases the differences in most hosts behavior are rather minor, and a well designed plugin should be able to live with almost all of 'em quite easily.
Honestly, as a plugin developer myself, please keep blaming the plugins!