@Clarke I’m afraid that I’m still not seeing this, running Cubase 10.0.15 on Windows 10.0.17134. The main display is 3200x1800 at 150% scale and an additional display is connected above this with 1920x1080 resolution at 100% scale.
Alright @ed95, thanks for trying. You can’t do anything about it if you can’t reproduce it there. Really not sure what’s going on. I’m running that same build of Windows and version of Cubase. My main display is 3840x2160, which I think is the same aspect ratio as yours. I’ll be doing more investigation myself at some point, so I’ll post any relevant findings here.
Do you use different gpus maybe?
Nvidia / AMD / Intel?
GPU driver versions?
Using an Nvidia Quadro P400 here, with latest driver version 419.17.
Nvidia here as well: Nvidia GTX 960
So it would appear that this isn’t the fault of Juce, but rather of something in the way the old Windows builds handle scaling.
OK, shot in the dark but from reading this SO thread it might be due to the way that different drivers expect the
glViewport to be set up.
Can you try replacing line 284 of
juce_OpenGLContext.cpp with the following:
auto newScale = 1.0;
and see if that helps at all?
That ends up with this:
If you look carefully, the text (what you can see of it) appears to have scaling artifacts - as if it has been scaled down from a larger image.
I’m running in a similar issue. Our flagship product is exhibiting this behavior and our 4k Windows users are starting to send in requests to get this fixed.
I’m able to reproduce what I think is the issue with the AudioPluginDemo:
Visual Studio 2017, Windows 10, Cubase 10.0.15
- Set Windows Display Settings scaling to 125% (or anything larger than 100%)
- Enable HDPi in Cubase
- Download/clone JUCE repo develop branch
- Make sure to set global paths to that repo
- Open AudioPluginDemo, save and build
- Open in Cubase. It looks fine! Resizing works well too:
- Now in the editor class, add an OpenGLContext and attach it
- Open in Cubase and this is what I get:
Our product looks very similar, with the top portion push downward and mouse clicks not triggering in the correct areas, etc…
@ed95 are you able to reproduce this? I’m happy to offer help in any way. Thanks!
No, as I said above everything looks normal when using the OpenGL renderer with a hiDPI plug-in for me.
Is this only happening in Cubase 10? Have you tried any other DAWs? What GPU do you have on the machine that this is happening on? As mentioned above it could be a driver issue, I have an Intel HD 5500 on my machine but it seems like the issues are happening with Nvidia cards.
I checked on my MBP (Intel Iris Graphics 540) and it works! My main dev machine has an Nvidia GeForce GTX 1050 Ti, so it does look like the issue only happens on certain cards. I’ll try to see if I can get info on our user’s card.
EDIT: I totally goofed, I forgot to add the OpenGLContext when I tested on my MBP. When I add the context and attach it the issue occurs again. Also, the graphics card our user has is a non-Nvidia.
I tested in Studio One 4 and it seems to work well there with HDPi mode turned on scaling turned up.
I’ve done some more testing with this.
Regarding graphics cards, this occurs on 3 different machines with these graphics cards (all running latest Windows 10)
Intel Iris Graphics 540
Nvidia GeForce GTX 1050 Ti
2048MB ATI Matrox C420 LP
The scaling works fine in the following hosts (making sure to have HDPi enabled when the option is available):
• Studio One 4
• Ableton Live 10
In the hosts I tested it’s these hosts where the issue crops up:
• Cubase 10
• Nuendo 8
• Wavelab 9
In Cubase and Wavelab the issue manifests as rendering with everything rendering out of place (like in the previous screenshot I posted) with no way to resize. In Nuendo the plugins load the same way initially, but then you can drag the resizer corner and then they look/control fine!
So it looks like there’s something Steinberg related to the problem. Can any other JUCEers confirm this?
@ed95 I’ve just tried testing this again with the latest develop branch changes. This time I used VS2019 with the latest Windows 10 SDK. The issue still persists on the three graphics cards listed above.
Any chance you could test this on a couple other machines? It doesn’t take more than a few minutes.
I also have some developer contacts at Steinberg if you’d like me to put you all in touch.
I was able to test this out on a different Windows machine last week and could reproduce the issue. I’ve got a fix and it’ll be on develop soon after it’s passed our CI.
@ed95, builds are now failing when only building VST3 due to a missing definition of
Ah, I’ll get that fixed. Thanks for the heads up.
No longer seeing the issue here in Cubase 10 using the example PIP. Thanks @ed95!