Voxengo VST3 PlugIn “SPAN” and “SPAN Plus” open windows larger than my 4K monitor. Only these two.
How can I make them smaller?
Hi, and welcome to the forum!
Have you asked the developer (Voxengo)?
Yes, I opened a ticket with Voxengo Support and the response was.
“Sorry, I have no idea why that may happen then. Please direct the issue to WaveLab developers.”
I just installed SPAN on my Windows 11 and it behaves normally in WaveLab 13.
How is CurveEQ being displayed on your machine? That is also from Voxengo but is part of the delivery of WaveLab 13.
The window sizes of other Voxengo VST3 plugins, such as CurveEQ, GlissEQ, and Elephant, are displayed at their usual size when opened in WaveLab Pro 13.
I also have Cubase 14 running on the same computer with all the same Voxengo VST3 plugins. The great thing is that in Cubase, the window sizes of all plugins can be set separately, even for “SPAN” and “SPAN Plus.”
Have you tried in SPAN settings to uncheck “Scale to screen”, set the scaling at 100% and then unload and reload the plugin?
Yes, I’ve tried everything. The window is smallest when scaling is set to 80%, but even then it still fills 95% of the screen width and is about twice as high as the screen (so you only see half of the window and nothing else).
I’ve also uninstalled and reinstalled the plugin, but nothing changes.
So it’s only SPAN and SPAN plus that display incorrectly, and only in WaveLab 13?
What OS, graphics hardware etc. do you have?
Are you using the VST3 versions of SPAN/SPAN Plus?
I don’t have SPAN Plus, but SPAN (the free one) is working OK in all hosts for me, on Windows 11 with an NVIDIA GPU.
I primarily need SPAN Plus, but SPAN behaves exactly the same way.
I think it has something to do with the “Plugin Window Hide” button. If I click it twice, the PlugIn window is compressed vertically and becomes about twice as wide as the screen, and this continues until I restart WaveLab.
I always use Windows 11 with WaveLab Pro and Cubase 14 on several other computers, but with lower screen resolutions, and I have the same problem with SCAN Plus on all of them. The error manifests itself differently depending on the screen resolution. It’s least severe with a resolution of 1920x1080.
Could you please press this hide button twice and check if you are still getting the same window size from the SPAN plugin as before, as it should?
Interesting, SPAN restores to only about half size.
Even more interesting, the same thing happens with CurveEQ!
When this happens, the only way to restore either of the Voxengo plug-ins is to remove them, and re-insert them.
This is 100% reproducible on my system (W11 25H2), I will use CurveEQ in this repro so everyone can do it:
- Open WaveLab 13, Create Empty
- Load CurveEQ in the Master Section – CurveEQ is displayed normally
- Click the Fold/Unfold button – the plug-in window is
- Click the Fold/Unfold button again – CurveEQ is restored, but only half-sized vertically
This only happens with the two Voxengo plug-ins I have, and only WaveLab has the “Fold/Unfold” feature. No other vendors’ plug-ins that I have (Soundtoys, NI, Izotope, zplane, Zynaptic, Arturia, UADx) exhibit this behaviour in WaveLab.
Thank you very much for your help.
Since WaveLab Pro 13 isn’t generally stable, I use presets and, when errors occur, reset the master section to my desired initial state with a preset after restarting WaveLab. Like in the picture:
My main problem, however, is that on my preferred computer with a 4K monitor, the SPAN and SPAN-Plus windows extend far beyond the screen when opened normally. This makes it impossible to work with.
Yes, it’s somewhat usable on PCs with 2K monitors, but even there the windows are annoyingly large.
The window size should be adjustable, just like in Cubase.
My workaround is to route the WaveLab output to Cubase and use SPAN-Plus there. This allows me to adjust the window size as needed.
Cubase is also from Steinberg, so why can’t they implement the same window resizing feature in WaveLab? It’s a bit hard to understand!
I think the issue with Fold/Unfold behaviour of the Voxengo plus-ins is perhaps something for @PG1 to have a look at.
What is your graphics card please?
Have you checked/updated the graphics driver etc.?
I use an NVIDIA 5060 Ti 16GB with one “2K” (2560x1440" and one “FHD” (1920x1080) but there is no difference in the behaviour of the Voxengo plugins across these monitors with different resolutions (both show the same fault).
You’re right, I meant that FHD (1920x1080) is the best setting for me; I don’t use 2K.
On the two PCs with 4K monitors, I use the CPU’s integrated graphics (Intel UHD Graphics 750), and on the other, a dedicated graphics card (NVIDIA Quadro P200). The problem occurs on both.
However, I’ve noticed that I use the recommended settings (3840x2160 and 150%) on both.
Interestingly, when the scaling is changed, WaveLab exhibits almost indescribable behavior in the plugin windows, depending on the settings. Only after restarting WaveLab is it somewhat okay again, and this also happens with their own plugins, especially the new MasterRig.
This doesn’t happen in Cubase!
I think the WaveLab developers generally have a problem handling the display settings in Windows 11. No wonder there are additional problems with third-party plugins.
FWIW, I use native resolutions only, and only 100% scaling, which is probably why I haven’t had any problems outside of the issue described above, only with the Voxengo plug-ins.
You are absolutely right. When I select your resolution (2560x1440 and 100% scaling), everything works correctly for me, just like with the FHD resolution where Microsoft automatically sets it to 100%, as well as with the 2K resolution. This isn’t the case with 4K; there, Microsoft suggests 150% for my 27" monitor, which I find comfortable and very sharp for reading. But at 100%, the text is too small for my eyes.
I think the WaveLab development team has two problems to solve:
-
The “Fold/Unfold Window” function, which isn’t working correctly.
-
Enabling display scaling other than 100%.
Do you know how to report this to the WaveLab development team?
In any case, I would like to thank you very much for your patient help.
You can log a support ticket via your MySteinberg account, however I’m not convinced the issue is with WaveLab, but we can agree to differ on that point. The symptoms occur on my system only with the Voxengo plug-ins.
Either way, there are many issues related to scaling in Windows 10/11, including in Cubase/Nuendo, HALion and Groove Agent, and it’s not just Steinberg products that are affected. That’s why I chose these monitors, so I could run them with native resolutions, with no scaling ad HiDPI off.