Admittedly, contacting the vendor is preferable to just not using the plugin, even if 99% of the time they will not be able to do anything. You got me there. This is the right thing to do, as gives them valuable feedback on how to improve, should they choose to listen. Heck, they might even have a workaround already discovered! Though, in a narrow view, that pretty much boils down to just not using the plugin. At least for me. Good luck getting a freeware’s vendor to respond! (Now, if this was caused by an NI or Waves plugin, then I would be all over them for sure!)
I know plenty well how difficult it is to design a good plugin system, having attempted to do so in the past. It is not easy, and Steinberg has done an excellent job implementing the plugin system for Cubase, not to mention designing the VST standard itself. I know fully well that a crash in a plugin is not the fault of the host. I’m not really here to blame anybody for anything. However, the frequent crashes are a problem for most of us users, regardless of who is responsible. (I’ll also just mention that part of a plugins stability is the design of the API itself, and while VST was excellent for it’s time, it might not be the most robust platform today. Not that I am a fan of the others.)
Pretending, for a moment, that there are absolutely no bugs in Cubase itself whatsoever…
Suppose I’ve got a massive project with hundreds of plugins loaded… and it is crashing randomly when in use, but with no particular action preceding the crash. We can assume, since we have decided from the start to rule out Cubase itself, that it is caused by a plugin. We now know we must either contact it’s vendor for a solution, or to just remove the plugin.
What ‘vendor’ do we contact? Which plugin was the cause?
This is where debug tools, or a log could help. It could help, but as far as I know, we don’t have them. So that’s not an option.
That’s why I mentioned isolating the issue by removing all plugins, reinstalling, then and adding them back. (After testing each.)
That’s about the only way to track down a faulty plugin without any other leads!
Unless you know of a better way?
If you do, thank god!