Quote:
Quote:
Found & fixed. VST is crazy... The behavior here was yet another weird way of doing things. I'll run a Windows-only build tonight for testing.
Damn, is there a word for something that's nonstandard but official? I'll keep an eye out.
To clarify why this is such a mess: We want a display of size 1440x768, assuming that the zoom factor in Windows is set to 100%. For 4K screens it's typically set to 150%, so we multiply these values by 1.5, resulting in 2160x1152.
So, here's how it works, when loading on a 4K screen:
Reaper: What size do you want, ideally?
Stereo Tool: 2160x1152
Reaper: Great, I've created a display for you, you're allowed to use 2160x1152 pixels. What size do you want?
Stereo Tool: 2160x1152
Reaper: Ok, you're allowed to use 2160x1152 pixels.
WaveLab: What size do you want, ideally?
Stereo Tool: 2160x1152
WaveLab: Great, I've created a display for you, you're allowed to use 1440x768 pixels. What size do you want?
Stereo Tool: Oh. Well in that case, I want to use that, 1440x768 pixels.
WaveLab: Ok, now you are allowed to use 960x512 pixels (1440x768 / 1.5).
The actual window is bigger than that (it's still 1440x768), but we cannot just draw in that - there are hosts that put buttons on the right or bottom of the area that we are allowed to use. So this explains why you got such a small usable area in WaveLab with a large border around it.
OBS: What size do you want, ideally?
Stereo Tool: 2160x1152
OBS: Ok, you probably didn't know that we're on a 4K screen, so I've automatically converted those values for you, and created a window of size 3240x1728. What size do you want?
Stereo Tool: Oh, more space! Great, then just give me that, 3240x1728.
OBS: Ok, you probably didn't know that we're on a 4K screen, so I've automatically converted those values for you ... (Continues to make the window bigger until it fills the entire screen.)
This DPI issue is actually just a minor issue compared to all the other issues with sizing.