Yes, if you have your windows set to 150% at this moment in time there is no way to run cubase at 4k native (full resolution)
you have to drop down to 125% then log off and back on, right clicking the exe and choosing ignore dpi settings does nothing anymore…
If you want to use full 4K without the limitations “too small”, we need to use at least a 45- 50 inch monitor. Only then are all the pixels again at about 90 ppi as in the past with the usual screens. Otherwise, the graphics must be scaled, so that the benefits of 4K are partially lost again.
It unfortunately does not work in the same way as 9.5 when you disable HiDPI, it locks to 200% when you disable HiDPI (or presumably whatever you have your scale value to, and there is no way to disable this. (that i have found))
No, Windows 7 and Windows 10 have totally different HiDPI implementations. For example there no support for multiple displays with different DPI on Windows 7, but that’s only one of many things missing in Windows 7.
Most of Windows-API features are cumulative. So everything available in Windows 7 is also available in more recent Windows versions, so support in W7 and W10 cannot be totally different, it can be just extended in W10.
Per-Monitor DPI Awareness is not as important as support for HiDPI itself. For basic DPI awareness, all you need is:
determine pixel ratio by dividing GetDeviceCaps(GetDC(window), LOGPIXELSX) by default 96;
multiply all the UI-element’s sizes and coordinates by that ratio with proportional upscaling of bitmap graphics where needed;
declare DPI awareness: either via executable’s manifest (<dpiAware>true</dpiAware>) or by calling SetProcessDPIAware().
Or does Cubase 10 use Windows 10’s automatic scaling stuff like EnableNonClientDpiScaling() without actually supporting true HiDPI?
Fwiw, according to StatCounter, market share of Windows 7 is 70% of Windows 10’s market share (36.31% vs. 51.94%). According to NetMarketShare, the difference is even smaller: Windows 7’s market share is 84% of Windows 10’s one (35.27% vs. 41.82%).
There is nothing funny or wrong in telling you about HiDPI Windows APIs given how long it took to implement HiDPI support in Cubase and how unreasonably limited it still is.
I’m aware of those HiDPI improvements in Windows 10. Is there something less broad and more specific you could say? What exact W10-exclusive HiDPI feature you use that is a blocker for basic Windows 7 support I described in my previous message?
And what about the huge market share of Windows 7?
I think you’re vastly underestimating the complexity of the situation with Cubase. It’s clearly not that they don’t know the APIs. There’s a technical debt in Cubase that is very hard to reconcile with Microsoft’s forward-looking hiDPI strategy, as opposed to Apple’s more pragmatic one.
I do think it’s a management issue though. There’s no excuse that after all this time the Windows version is in this condition. Yes it likely requires a lot of gruelling redesign to support it properly, but it should have been done at this point if you want to advertise this as one of your main features.
Regarding Windows 7 support, I have to imagine people using a legacy OS with modern hardware is such a niche group that any extra work to support that combination makes no financial sense. Mainstream support is already gone and extended support is ending in 2020. It makes perfect sense to target Windows 10 only for this feature.