The DAW plugin interface is not high DPI aware with C10.5

[o_range]

Just updated to windows 4.4.6 64bit

When I launch the plugin in cubase 10.5 I get:

"the DAW plugin interface is not high DPI aware....etc"

This gives a "fixed window" but basically unusable.

works fine in Cubase 10 - odd

there is a hidpi setting in preferences for the whole of cubase but selecting it doesn't fix the issue.

Odd too that I was given the 4.4.6 update today as the release notes say this was october - but I've installed extra paks since then and haven't been offered it previously

Stuck now emailed support but I thought I'd try here

[jas_lan]

I have seen a lot of grumblings on the Cubase forums about the Hi DPI functionality in Cubase. They are even doing a survey about it right now. I use Cubase 10 and just have standard Full HD monitors so can't offer any help but I do recall seeing some users saying that it works if you select 100% scaling in Windows. Unfortunately, that means the GUI will be very small unless you have a large monitor (larger than 27" at least).

Sorry I can't be more helpful.

What size is your monitor? The reason I ask is because unless it is at least 32", I personally recommend just using standard full HD (1920x1080) because you will have less problems and the human eye can't really tell a difference between full HD and 4k on smaller screens.

[o_range]

I have seen a lot of grumblings on the Cubase forums about the Hi DPI functionality in Cubase. They are even doing a survey about it right now. I use Cubase 10 and just have standard Full HD monitors so can't offer any help but I do recall seeing some users saying that it works if you select 100% scaling in Windows. Unfortunately, that means the GUI will be very small unless you have a large monitor (larger than 27" at least).

Sorry I can't be more helpful.

What size is your monitor? The reason I ask is because unless it is at least 32", I personally recommend just using standard full HD (1920x1080) because you will have less problems and the human eye can't really tell a difference between full HD and 4k on smaller screens.

I don't have a HD monitor and it's nothing to do with the scaling setting per se, but thanks for the reply - this is new behaviour in V10.5

FWIW scaling is also broken in Cubase 10 if you use the HiDPI preference in Cubase on a 4k monitor at anything other than 100% but that doesn't affect me so I don't care - although others might ?
Ralph is being very helpful via email (thanks Ralph)

[jas_lan]

But can you select a resolution of Full HD (1920x1080) on your monitor?
Do you have a 4K monitor? What size is it?

[o_range]

But can you select a resolution of Full HD (1920x1080) on your monitor?
Do you have a 4K monitor? What size is it?

Yes I can select Full HD on my monitor but that's not really the point (or the issue)

I'm using 3 monitors none of which are 4k....and none of which are Full HD.

1920 x 1200 - 3840 x 1200 - 1920 x 1200

there is no HDPI involved at all - everything is pixel for pixel - 100% scaled

I have a 4k monitor on my laptop - but that's another story as I said.

I believe you are barking up the wrong tree

[Ralph @ Rayzoon]

What happens is that Jamstix is high-DPI aware, which means it tells Windows what it can do in regards to high DPI situations in its windows. Cubase 10.5 does the same but it says something to Windows that makes Windows throw an error when Jamstix tries to make its interface a child window of the wrapper window that Cubase provides for it because Windows says the two settings are not compatible.

You don't even have to have a high DPI environment for this to happen.

This problem does not happen with any other DAW and we're trying to find a work-around for it.

[o_range]

as a workaround - if you save your project AFTER you have added jamstix and then reopen it the plugin windows snaps back in place and the error disappears

[C_Holdz]

TBH, it sounds more like a Cubase issue. FWIW, I am running the same DAW and I haven’t had issues with Jamstix (win 10). And I checked with the Cubase guys and it seems the DAW is so, please allow me the term, “over programmed,” that it has some compatibility issues with VSTs, but it also is copy protected like a tank, so its anti piracy has been very strong for years.

Actually, I heard Cubase 10.5 Pro was “cracked” after years of pirates attempting to get it, but it crashes when given 3rd party plug ins with cracked license....

Many people said a fresh install of windows, cubase, and the legit/licensed software completely solves any crashes....

Again, i have cubase 10.5 pro for a couple of months, and no crashes to report (there is sometimes issues with loading 3rd party VST, but it usually takes a minute to clear if you let it run)

Did you ask Cubase guys for any help? They are great too .

[o_range]

TBH, it sounds more like a Cubase issue. FWIW, I am running the same DAW and I haven’t had issues with Jamstix (win 10).

of course it's possible but I have a lot (!) of plugins and no others have the problem... The warning message is from Jamstix. I'm 100% sure it's not a cubase security issue. You saw the message from Ralph earlier.

Others seem to use jamstix on cubase 10.5 without issue but I have multiple monitors and I think that's part of the issue (just guessing)