Allow Window to Be Resized Issue

In C Pro 11 I have issues with the ‘Allow windows to be resized’ function. With my UAD plugins as well as Waves plugins they display quite small. If I use the resize function the plugin is resized but it is disabled. This is true for all UAD as well as Waves plugins. I haven’t tried it with Soundtoys or Plugin Alliance plugins. When I instantiated GA5 I got a huge window and yet the content of GA5 didn’t fill in the window. This happened just pulling up GA5 and there was no ‘resize’ option. I have attached screen shots. In the other two screen shots with the Waves CLA plugin you can see that there is signal passing through the plugin in the normal state and in the resized state there is no signal passing through as if it has been bypassed.
I am using Windows 10 with and Invidia GeForce video card and a Samsung 55" 4k monitor and have had no such issues with C10 or C 10.5 but I haven’t been resizing the plugins in those versions and they appear about 40% larger than in C Pro 11. Hope this is sorted out soon



I am experiencing the similar issue .
what made my system usable was to make sure you are in 125% scaling (not 150% which is recommended by Win10 at 4k resolution with my monitor))
it does make everything a bit smaller but on my 32 inch 4k monitor i find it OK.
Now, plugin wise. Once you resize it, you need to remove it from your insert and reapply. The new instance of your plugin will open already resized and it will be active (not acting as if it were bypassed).
It is especially painful when working with an older project. as you must first open your plugin, copy your settings, enlarge the window, remove the plugin, reopen plugin and paste the settings.
unfortunately it has to be done to all plugins that have the sizing issue.
good news is, once you do it once, it stays activated across all projects.
I would love to hear if anyone has found a better solution.
Good luck , happy resizing
Tom

1 Like

Well this just all seems like ridiculous bs to me. If Steinberg wants to offer resizing that’s great but work out the bugs first. It supposed to be about workflow and if one has twenty or thirty plugins in a project to jump through those hoops is ludicrous to me. Guess I’m goin back 10.5 for now

1 Like

This needs to be fixed. I had to revert to C10.5

1 Like

You can also try any Exponential Audio plugins too (PhoenixVerb, Nimbus, Excalibur, etc.)! Without the resize option the window opens cut in half every time … 1/2 then 1/4 until there’s nothing left! :smiley:

1 Like

That solves nothing. I have 4 UAD cards, tons of UA, Waves and Plugin
Alliance. Don’t offer a feature if it doesn’t work properly or there has to
be workarounds. I am not the only on affected by this and Steinberg needs to
step up to the plate and at least address the problem

Michael Hickman
Electric Eye Recorders
512-785-2132
Polish Hill
Pittsburgh, PA 15219

2 Likes

Is there any news about this? It looked like the recent update was supposed to address the problem, but it didn’t. Or if it was meant to, it failed to do so.

1 Like

This is true also for TDR and fabfilter plugins here. I installed the new update, need to check tomorrow if it works.

1 Like

I think nothing is to be expected from Steinberg …

2 Likes

It seems to be up to the various VST makers to address this – I’ve noticed individual brands’ improvements since last year, and new VST3s seem to be implementing scaling options in their own layout settings. Still it’s a shame that something that just worked fine in Cubase 10.5 had to be jettisoned like that.

It is a Windows OS issue really, not a Steinberg issue. It specifically did NOT work for me in 10.5, and 11 was actually a fix.

With Cubase 11 installed, go to Windows Settings Display and select Advanced scaling settings . Select 100%.

Or, if you have a video card installed such as NVidia, you can use it for Cubase just like you would for games. Then you probably would not need to worry about this at all.

I hope this helps.

Yeah I’m not going to switch my scaling setting to deal with this. It’s less annoying to go to the optician and get new ******* glasses.

But , but, but… what? 100 = 100

Mine’s set to 150. It’s a 32" desktop, not a laptop

Got it, so you already set it. Would 125 work for you, because I think that is where the cutoff is.

I think that fractions are worse than whole numbers, so 2 would be fine. My old screen (28") was set to 1.75. Maybe the new screen, at 150, works the math better, but more likely it’s just that it’s new, and so the various updated VSTs are better at scaling in general.

It’s 2023, I have the latest Cubase 12, and I’m still facing this issue. Updating Waves would cost me over 200 USD. Steinberg should just add an option to force fixed zoom (like 200%) on plugin window or the plugin. Here’s how it looks for me (normal vs resized waves plugin). For the record, disabling hidpi for Cubase is not an option.

1 Like

Hi @docencik

Thanks for your report. This problem should have been fixed in later versions of Waves plugins. The only option is to update so that Waves Plugins are HiDPI compatible. I am sorry about the sad news but we cannot be held responsible for Waves’ update policy either.

Cheers,
Armand

Hi Armand,
I would accept this explanation if it hadn’t been for the fact, that e.g. Bitwig Studio (and ableton) respect scaling for these older plugins out of the box, without any tweaking:


Which means that it’s doable and should have worked like that in the first place.

1 Like

Yeah, this whole situation is completely ridiculous. Hitting it with Cubase 13.0.21 as I type this. Oxford Dynamics is all screwed up, so down another dank rabbit hole I go, trying to figure out why. Gosh, I sure do love software. Yup. Love me some software!