I’ve noticed this with certain plugins since WaveLab 9.5 but haven’t taken the time to report it until today.
In the scenario I’m describing, a VST3 plugin will instantiate and launch successfully. However, once the plugin interface is open, the only interactive items available are the elements within the plugin UI itself. The entire remainder of WaveLab’s UI becomes unresponsive; thus, in this state, the only way to proceed is to force-close WaveLab via Task Manager.
While SoundSpot may be a lesser-known development team, they produce quite advanced plugins; and I’ve noticed this issue with other developers’ plugins as well.
My larger concern isn’t even really the operation of the specific plugins, as much as it is that plugins can completely lock WaveLab’s interface.
Philippe, I’m actually hesitant sometimes to try new plugins out of concern that they might lock/crash WaveLab. Would you be able to architect a solution that better “sandboxes” plugins so that if a user instantiates a misbehaving plugin, the plugin doesn’t completely lock the user out of a session?