Thanks to @PG1 for the world-class audio production tool that is WaveLab 13.
One issue that continues in v13 involves plugin scaling on HiDPI monitors at resolutions such as 3840x2160 with 150% (default) scaling.
For example, the current plugin versions from Voxengo, MeldaProduction and United Plugins scale as expected in Steinberg Cubase, Blue Cat PatchWork, FL Studio, Ableton Live, Bitwig, etc.
But in Steinberg WaveLab 13, some weird things happen:
Many of these plugins open at gigantic sizes by default, extending across 2-4 monitors.
Many of these plugins open with lots of extra empty space surrounding the plugin interface:
When trying to correct these issues with various in-plugin settings and controls, in combination with WaveLab’s Fold/Unfold feature, bizarre things can happen like a plugin suddenly extending itself horizontally wide enough to cover 8 monitors (and crashing WaveLab).
There are known scaling workarounds (application compatibility settings, WaveLab scaling settings, etc.) but none of them fix scaling issues satisfactorily across the board, and none of them fix the specific issues mentioned here.
Because these issues only occur in WaveLab, the developers request that a fix be sought with Steinberg. But historically we are given the answer here that the plugin developers need to fix the issue.
But if such issues are only occurring in WaveLab and not dozens of other DAWs, what’s the underlying problem? Is there something that can be shared with the plugin developers about why these scaling issues are occurring with their plugins in WaveLab, to help them fix it? Can anything be improved in WaveLab itself to help fix it?
Do you have the problem with the Voxengo Curve EQ plugin that is included in WaveLab?
I don’t have a problem with this plugin. Thought it opens very large on a 150% scaling.
I have checked several of the plugins you mentioned. These plugins all have in common that they don’t respect one of the VST3 scaling procedures. Nevertheless, I found a way to correct their behavior. Therefore, in WaveLab 13.0.30, you should not see those gigantic UI.
Thank you for being willing to take a look and to implement a fix.
In addition, would you be willing to share a bit of the specifics of the underlying issue in the plugins (technical details)? Many of your users would be glad to provide this info to developers to help them respect the VST3 scaling procedures correctly, so workarounds like this aren’t needed in the future.
In VST3, there is a scaling interface. On windows, any plugin should support it. If a plugin does not support it, the scaling might be wrong. But this is not the case with the plugin you mentioned: they do support the scaling interface. The problem is elsewhere: When specifying a scaling to these plugins, these plugins return “false”. In that case, WaveLab does not do the scaling. In WaveLab 13.0.30, this “false” will be ignored and WaveLab will behave as if the scaling was accepted by the plugins. The vast majority of plugins do not return “false”. This is why the vast majority of plugins do not have this problem. Curiously, Curve EQ 3.14 does not return “false” while Curve EQ 3.16 does.
