in both hosts, Studio One and Wavelab, our QA encountered severe problems with VSTGUI’s high-DPI implementation. Here is one example for Wavelab:
- Open Wavelab on a computer connected to two different monitors. The first one is scaled to 150 % (high-DPI) and the other one 100 % (non high-DPI).
- Instantiate a VSTGUI 4.6 based plugin and open the editor UI.
- Move the editor UI from one screen to the other.
-> Host crashes.
A similar problem occurs in Studio One, when moving a plugin UI on those two screens back and forth. We have reproduced this with our internal plugins and with Fuse Audio Labs’ products. All in all, Windows high-DPI support generally works well, but with a set-up of two different screens it can become instable. What do you suggest, Arne?
EDIT: I have to correct myself. In Studio One there is not a crash happening, so the problem is not as severe as it sounds in my initial post. It is more a mouse cursor inaccuracy and possible loss of control over the editor window.