I am having a problem with VSL’s “Vienna Suite Pro” plugins in Wavelab only. They work in all other programs but in Wavelab they are not working correctly. What is happening is when I start to interact with the plugin by moving my mouse over the interface, my mouse and keyboard no longer work to control Wavelab itself. I can click anywhere in the Wavelab window and nothing responds - but it isn’t frozen, if I have things playing they keep playing and I still see the interface moving around, it just doesn’t respond to any mouse or keyboard input. The only solution I found was by clicking on the system tray icon for Wavelab itself a few times it seems to minimize it and bring it up again. Then the Wavelab interface starts responding again, unless I move my mouse over the interface for the plugin (and the plugin starts to react to the input) and then it starts to do the same thing again.
I am using the plugins in other Steinberg programs such as Cubase and Dorico without these issues - this only seems to be impacting Wavelab. I do not seem to be having these issues with any other plugins in Wavelab.
I opened a ticket with VSL regarding issues with their Vienna Suite Pro plugins in Wavelab 12. They say they are unable to reproduce the issue.
I found one other user who had my problem before, from about one year ago:
It’s just a bundle of VSL’s plugins (EQ, imaging, panning, compression, exciter, reverb) sold by VSL.
I contacted their support and reported this issue and they said they weren’t able to reproduce it and asked if I talked to Wavelab support, and that’s why I’m here. Maybe they think the problem is on the Wavelab side? But I have a feeling even though this issue only happens in Wavelab that it is something weird the plugin is doing that doesn’t affect Cubase or Dorico. But I’m not sure why they can’t reproduce it then.
For what it’s worth, I’ve been demoing VSL’s “Vienna MIR Pro 3D” (their convolution reverb plug-in) for two weeks now with no issues. Controls and renders very well. Does the suite incorporate MIR Pro 3D; perhaps your issue relates to one of the other plug-ins in the suite?
MIR Pro 3D is a completely different product, which I also own. I haven’t tried it in Wavelab yet, and generally don’t have a need to use it in Wavelab, as it is primarily meant to be used on the mixing level rather than the mastering level. I could try it though to see if the problem affects it too on my side. Again, all of these things work fine in Cubase/Dorico.
On my new computer there is a slightly different behaviour. The plugins work fine as long as they are the smallest size (ex. I haven’t changed the size).
If I drag the bottom right corner of the plugin window to make it bigger, then it starts the problem chain I described in my first post.