I can no longer use Massive since 1.7.0 update - UI oversized

bhmcc

Yes, I've restarted multiple times since changing.

bhmcc

Should I do a full uninstall / reinstall of Massive?

Sunborn

https://community.native-instruments.com/discussion/comment/201087#Comment_201087

It should work for the plugin too.

Since you say it doesn't then i need you to check and confirm if there is some relic from older installations.

For example, if you have both VST2 and VST3 versions and, for some reason the VST2 is from an older version, or, if by any chance you have multiple .dll's on different folders.

By the way, i suggest you to completely remove the VST2 version unless if you have older projects that they use it.

Apart of that, i can not see any other reason, except that it might be a Reaper bug (perhaps somewhere in its database there is a value to force Massive to be small?). I also notice that in your image it writes "disable".

Unfortunately i do not use Reaper, so i don't know it.

But maybe, if you temporary remove (do not uninstall, just put on a different folder for a while) all Massive VSTs, do a full re-scan in Reaper, then put back Massive VSTs and re-scan again, it might initialize it and fix the problem.

CILA

I also use Reaper and no problem on my side

CILA

Do you run the plugin in the FX window or in a floating window:

FX window =

Floating window =

Because I think it's better to:

• run it in the FX window first
• check whether the HiDPi mode is off
  
• unload the plugin
  
• and reload it to refresh the configuration
  

bhmcc

OK - here's the latest:

Per CILA's recommendation I tried using Reaper's FX window rather than the floating window. Then made sure that HiDPi mode was off. Then took it offline and brought it back online. Still no luck.

Then per Sunborn's recommendation I tried removing the original VST2 instance of Massive, rescanning VSTs in Reaper (deleting cache and rescanning all)…no change. So I then removed the VST3 instance of Massive, rescanned VSTs in Reaper, replaced Massive VST3, rescanned and still no change.

So I fully uninstalled Massive using Native Access, rescanned VSTs in Reaper using delete cache option, checked the registry and Massive was still there so I deleted it there too. Restarted Windows, reinstalled Massive from Native Access, rescanned VSTs in Reaper using delete cache option and still no change.

Tried RegEdit to set the display size again but still no luck. I've also reverified that ALL other NI VSTs still work fine. I must be missing something.

Thank you for sticking with me this far.

bhmcc

CILA,

I recalled this video from when I was addressing the Reaper HiDPI issue with Windows (can't post links but here is the title).

FIXED Reaper's FX Window Resolution Resizing HACK High DPI Scaling Override

I changed from System Enhanced to System and now Massive loads fine. But this is not really good because I was using System Enhanced because it is much clearer than System…now everything is a bit blurry. Really starting to wonder why Massive is the only plugin giving me this issue…not had this issue with any other plugins of any brand.

CILA

thanks for the feedback. mmm… that's a bit annoying but now you are able to use Massive even if the GUI is a bit blurry

bhmcc

I can't really tolerate how blurry it is. Really a shame the Reaper developers can't address this HiDPI issue.

PoorFellow

https://community.native-instruments.com/discussion/comment/201161#Comment_201161

I can no longer use Massive since 1.7.0 update - UI oversized

Really a shame the Reaper developers can't address this HiDPI issue.

Perhaps the issue is related to your specific configuration or Windows settings such as screen resolution and 'scaling' set in Windows (so maybe try setting scaling to a lower percentage) , or perhaps you can influence behavior by tweaking the Windows High DPI settings for the DAW ?

bhmcc

PoorFellow,

Thank you for your reply! The issues between Reaper and Windows HiDPI are well documented. My system was working great for the last few years - no GUI issues with any plugins whatsoever (including Massive) until the 1.7.0 update. Plus, all other NI plugins load correctly whether VSTi or VSTi3 so I'm really wondering about this update…what is different about it that causes this singular issue with this one plugin?

Per our recommendation, I did try reducing my graphics scaling in Windows but it didn't seem to have any effect going down both 1 and 2 percentage settings.

I might could try tweaking some of the Windows High DPI settings for Reaper, but that will most likely cause GUI problems with most everything else. I'd honestly prefer if NI could let me have a copy of the previous install of Massive.

PoorFellow

https://community.native-instruments.com/discussion/comment/201316#Comment_201316

I'd honestly prefer if NI could let me have a copy of the previous install of Massive.

Why didn't you get that idea before ? 😁 Just ask support for it : please contact N.I.Native Access and Installation Support , explain the situation and ask politely for the previous version. Had Jeremy_NI been around then maybe he could have dug it up but he will not be around until January 6th or after and then he will most likely be very busy.

In case that you need guidance contacting support : How to contact NI Support and How to get in touch with our Customer Care

BIF

I don't have any help to offer here, but I thought it was important to commend the participants above on their hard work and especially THEIR PATIENCE with such an annoying issue. Yes, we should be using our ears to make music (I know some joker is out there thinking that!), but the UI is important, especially as some of us are stacking the years up higher and higher, making it more difficult to see things, not to mention the challenge brought about by today's high resolution monitors.

Working together. That's critical. Collaborating with each other, sharing our knowledge and understanding with each other, THAT is what makes these forums so so powerful. But it only works when we help each other.

Thank you all for setting such a good example!

Hopefully Jeremy will be able to assist once he's back from holiday break.

Happy New Year to all!

bhmcc

Agreed 110%!!! Thanks again to all those working to assist me with this issue!

Brendan_NI

Just a note - there should be no need to edit the registry directly. Just open Massive in Standalone and change the scaling from the menu.

Edit: of course if the menu is cutoff in standalone as well then the registry is the only option. I would be very interested in finding out what combination of windows version, number of monitors, their specs and windows scaling/HIDPI settings that cause this issue.