I understand the hijacking, I apologize…that said, it is relevant as marc posted the dialog we are talking about
I will hijack his screen shot and add it to my previous thread
I understand the hijacking, I apologize…that said, it is relevant as marc posted the dialog we are talking about
I will hijack his screen shot and add it to my previous thread
Well, as long as Steinberg advertises this, I do expect VST3 plugins to work flawless without crashing the host application.
This is a regular topic of discussion on the Wavelab forum. Most of the time crashes caused by plugins are not due to the host application. 99% of the time the issues stem from a poorly written plugin. So, IMO it is worth doing the following when you discover an issue:
Advertising VST3 plugins support is perfectly legitimate. This doesn’t give any guarantee that the said plugins will function - that’s up to the plugin developer. SB cannot control what goes on inside the plugin. The Robert van der Helm FREE Spectral Compressor you mentioned above, for example, is likely to be the source of the issue. Did you write to the developer? If the developer is not willing to fix the issue, it might be better to use plugins from reputable, tried and tested developers.
Stingray’s comments are accurate from my experience. Seriously, I doubt the author of the FREE plugin has even heard of SL. And on that note, Steinberg allows the FREE use of their programs to plugin developers to help them fix their VST3 coding issues.
Bottom line, when the plugin developer can’t develop a VST3 plugin to work in a Steinberg program - and you have contacted him about this and he cannot/or will not offer a fix - then you know everything you need to know about the plugin and it’s author. Can you contact him, is he running a plugin business? Try not to align yourself to a plugin that will not work properly in a Steinberg program, that’s my best advice. Or, another option, avoid the Steinberg program if the plugin is that important to your process.
The plugins, who crushes SL here, do not crush Audacity or Wavelab.
A plugin might behave badly, but should imho not crush the host application.
The interface should have some firewalls (memory leaks, false addressing, whatever) in it, to protect the host, imho.
This is not the customers fault.
Any plugin can definitely crash any host application. SpectraLayers does a basic check when scanning VST plugins to see if it respond properly to early status informations, but if a crash happens deeper into the plugin, there’s unfortunately not much that can be done : the host and the plugin share the exact same execution space, so if one mess up, the whole stability is compromised.
That being said, I’ll check what happens with that Spectral Compressor plugin.
Thx for clarifying on this issue.
Crash with the Spectral Compressor plugin fixed, will be in 11.0.50.
Thx a lot.