So .. HiDPI was introduced in Cubase 10.0 - and its still not fully usable in the latest version. For me, personally, the one truly showstopping problem is the lack of 2x scaling for plugins not aware of HiDPI; something which competing DAWS does just fine. I don't really see any room for interpretation on Steinbergs behalf: it was a selling point in the marketing of Cubase 10, and here - a paid upgrade later, we're told that we'll have to pay even more, before its usable for production work even with the current 100%/200% limitations (that in fairness was mentioned at C10 launch).Matthias Quellmann wrote: ↑Thu Jun 04, 2020 7:55 pmPlease understand that this is not about fixing something. The support of high resolution displays is a development task that we can only achieve in iterations. The 100% and 200% support was the first step. After that we needed to work in the backend to prepare the framework in order to deal with uneven scalings like 150%. The next step will be the support of scaling of the main application. But it will be a topic for some more future Cubase versions until we will be able to fully support HiDPI in every corner and bitmap of the application.
I'm truly sorry to sound harsh, but this is an outright deceptive way of conducting business. Is this not obvious to Steinberg management or whoever is in charge of development priorities? I can assure you it's obvious to everybody else ..
FishCorp / Copenhagen