I updated to Cubase 12.0.0 lately and everything worked fine. Then I got the maintenance update today and suddenly both my “MAAT DR Meter” and my “Meterplugs Perception A/B” plugin windows are way too wide than is needed for the actual interface of the plugin. This results in grey chunks of nothingness at the left and right sides of the plugin, which is a pain in the b**t for my preconfigured monitor layout because parts of the plugin windows now block important stuff I want to see. I attached some exemplary pictures.
This is happening on a lot of my plugins, too. I’ve found that if you hit the QC button in the top right and then turn it back off, some plugins resize back to the way it supposed to be, but as soon as you close the plugin and open it again, it won’t remember. Hope Steinberg fixes this ASAP. It’s quite annoying.
Got the same issue. I’ve just gone through my whole collection of plugins.
Good news that it reproduces only with a small amount of plugins.
So, it’s reproducable with:
Audified MixChecker (QC button fix works)
kHz Transient Shaper (QC button fix still leaves padding on the sides of plugin UI)
NI Replika and Replika XT (QC button fix works)
NI RC24 and RC48 (QC button fix still leaves padding on the sides of plugin UI)
NI Raum (QC button fix works)
Izotope RX7 De-Click (QC button fix still leaves padding on the sides of plugin UI)
NI ones that are affected: Battery 4, Massive X.
Absynth 5, FM8, Reaktor 6, Kontakt 5 and original Massive are fine though.
For those plugins, where QC button fixes the blank borders - closing and opening plugin window resets the fix.
Yeah same issue here: Omnisphere, Massive, and Massive X are the ones I’ve noticed so far but there are bound to be more!
It’s a pretty annoying issue though, I’m contemplating reinstalling v12.0.0 for now unless there’s a fix on the way? Hitting the QC button a couple of times does seem to work though so it’s manageable for now.
How this wasn’t noticed in testing is really bizarre. I’m glad to have the controls that were missing previously, but it’s really inexcusable that something so majorly obvious is part of an update which is designed to ‘fix’ issues.
It doesn’t exactly fill you with confidence on how rigorous testing is, I must admit it. Also, not seen any kind of official response to it either, anyone else?