that makes sense
Hi,
Sorry to have taken such a long time to get back to you. It apperas there was a misunderstanding on my side. This option is not only available to VST 2 but to any plug-in that doesn’t implement the dedicated VST3 option that allows plug-in to be compatible with a HiDPI-Aware environment. My bad. The status quo remains the same: iZotope has so far not implemented this option for their Nectar 3 plug-in at least. This is where efforts should be made.
Cheers,
Armand
Seems like the option doesn’t work very well?
The window doubles in size every time it is opened.
Doesn’t Cubase manage the size of the window, not the plug-in?
Can confirm doubling of the window size. I’m having issues with different window size bugs since January. My issue thread: Cubase 11 / Win10 - FabFilter plugins automatically change window size when reopened - #21 by otro678
And yes, there are a lot of configurations, lot of systems, displays, videocards and other variables. But Steinberg has a politics where old version stop receiving support and there are paid upgrades for relatively minor changes. So pretty please, I would like my modern DAW to perform in a modern world where displays that have a resolution bigger than 1080p are a common thing.
The latest issue is demonstrated here:
https://drive.google.com/file/d/1zogjLVYT9sTSMcVOCxccfYYGnMB8Qtr1/view?usp=sharing
“Steinberg, please focus on stability and quality” includes efforts to validate, accommodate, or protect against problematic third-party plugins. And where they are from major vendors, maybe more outreach?
Hi,
The option works well in what it is supposed to do: declare the Plugin Window HiDPI-Unaware and see how the plugin and the OS plays together. I was confused earlier on because I assumed this option was only available for VST2 plugins but it is available to any plug-in not using the interface to deal with HiDPI.
I am investigating the double size issue. The window size is ultimately down to the plug-in. It could be Cubase sends a wrong information, or that the plug-in doesn’t read the information properly in this environment.
Cheers,
Armand
Hi,
There are workarounds in our application to accommodate and protect against problematic third-party plugins. The “Allow Windows to rescale” is an actual workaround to accommodate with problematic plugins.
As long as we are not developing “Steinberg OS” there is a limit to what is reasonable/feasible for us to fix. We cannot accommodate to all the specific ill-responding plug-ins in the world. They have to follow the VST standards, fix their GUI framework and how they deal with new features of the OS.
This is the current strategy I do every day. I check and answer the forum daily, I report and investigate issues, then either it’s on our side and we can schedule a fix, either it is not and we identify why and contact the vendors so that they can investigate (or ignore us). Last week we have sent 5 emails to 5 different vendors about different issues with HiDPI-Awareness with precise description of what seems to be a flaw on their side.
Cheers,
Armand
Thanks Armand. It’s great to have steinberg developers participating in the forums and to know that issues are being addressed.
Have a great day!
I do not know why iZotope is so stubborn! They are one of the worst developers to deal with it seems. They simple shine you on and keep doing their own thing, regardless of whether it is right or wrong!
Armand, some of the negativity and mob mentality surrounding these issues are due to the lack of communication like this in the past, which you are clearly rectifying. We appreciate you.
As someone who was using Studio One for several months, I believe you won’t be disappointed. Frankly I’m only using Cubase now for SMPTE and video support. Outside of that Studio One is very much like Cubase with additional UX features.
It’s been a while I’m using 11.0.41 and works fine for many of us now, totally replacing cubase 10.5 for me.
Thanks Steinberg for listening to you users and for your hard work, no doubt why so many professionals (usually simply caring about getting work done in a stable manner) continue to use that great piece of software.
Same, no problems here…
Two problems here: Using Win10, any version, Cubase cannot determine the latency compensation in the Ext Efx connection for the Motu M4 interface, and, the use of the Scissors tool on the #1 monitor in a two monitor system is a fail using any interface. Both issues have been acknowledged by Steinberg Support but no fix has arrived so I’m back to 10.5 where at least the Scissor Tool works as it was intended.
Wave Lab, BTW, has a different issue with the Motu M4 in regard to the Ext Efx connection. It turns out it can be routed in an odd way - not the correct way I discovered - and deliver the connection and the latency ping - but at the expense of the audio quality. When routed from the Line Out outputs 3 & 4 and returned to the Line In 3 & 4 inputs (the correct way), WL will immediately close when audio is played if not sooner.
I haven’t had a single freeze or crash on Cubase 11. Have been using it since Release Day.
I don’t understand what the scissors issue on 2 monitors is, any link?
As to your setup, are you PC or Mac? I ask because this doesn’t happen on a Mac from what I’ve heard. Also, are you on Win10 and do you run two monitors from the same video card? All of these things would duplicate my set up.
But you know what? I will post a video on YT and link it here either tomorrow or Thursday just so it’s out there.
I use mainly a Win10 PC, but still have quite a few projects on my mac.
I do not use multiple monitors at this time, only one 32" monitor, but I was thinking of adding a monitor or two , so that could happen to me later.
Thanks for sharing!
The scissors simply does not work on a 2nd monitor?
Windows 10. I’m using 4 monitors. NVIDIA GeForce 1050ti.
I can almost swear there has never been an issue, but will verify within a few days.
fwiw, 2 34-inch ultra-wides, 1 28 inch ultra wide, and a 21 inch 3x4.
The 2 34-inch ultra-wides are linked.
Import a track that is long enough to span 2 monitors, monitors that Win10 labels 1 and 2. Now take the scissor tool and make two cuts on the track section that is on monitor 1. Then click on the cut part - as if you are going to add gain to it or edit it in some way.
Does the cut part move to the start of the track? It does on my DAW. Now make two cuts on the part of the extended track that is on monitor 2. Click on the cut part. Does it move? It doesn’t move on my DAW.
None of this happens on C10.5 and any version of Cubase prior to C11.