Kontakt has similar issues where it doesn’t render correctly in a DPI-unaware window - I spent a while trying to figure out what the issue is but no luck. In the AudioPluginHost it’s just a special case where we always open it in DPI-aware mode and live with the fact that it’ll render smaller. Guess I’ll need to add Massive to that check now too…
I’m not sure what NI are doing for their high-DPI scaling on Windows but it doesn’t play well with what we do in our hosting code unfortunately.
I know this is old but the situation has been reported to me again recently and this hasn’t been resolved.
Annoyingly, this does now work correctly with Kontakt so maybe there’s something different about Massive X.
They’ve also released the VST3 version of the plugin now and that also displays black when stretched.
Anyone got any ideas about how to fix this?
I also noticed while debugging that the editor doesn’t implement the IPlugViewContentScaleSupport interface, and instead seems to be querying the OS directly. My guess is that the plugin isn’t taking Windows’ automatic scaling into account when rendering in this mode. Maybe this is worth reporting as a bug to NI.
Finally, I tried resizing the window with auto-scaling both enabled and disabled. In both modes, the editor remained visible, in both the APH and REAPER.
Are you testing with the same version of Massive X as me? If so, perhaps this issue is OS-dependent (it looks like you’re testing on Windows 10).
I’ve installed the latest version of Massive X from Native Access, v.1.3.5.
It does sound like a bug in Massive X, it’s annoying it seems fixed in some of their other plugins though. I’ll try and report it to them. Cheers for taking a look.