Any news on GUI cutoff on 4K monitors?

GreyLion · Post by **GreyLion** » Sat Feb 17, 2018 2:10 am

Hi, Ralph -- I'm just touching base to see if you have any further thoughts about fixes for the GUI for JS4 not working on 4K monitors?

http://rayzoon2.com/forum/viewtopic.php?t=7747

Looks like a probable cause has to do with screen resolution being set at something other than 100%. But I can't dial back to that, as everything becomes too small to be usable then.

I really want to give you some more money...

Post by **Ralph @ Rayzoon** » Sat Feb 17, 2018 9:55 am

Please use 'Email Tech Support' in the JS4 manager and send me the logs so I can advise you how to fix this.

GreyLion · Post by **GreyLion** » Thu Feb 22, 2018 2:58 am

I just now sent the log and a few notes about my system and symptoms.

Sorry about the delay -- I've come down with the 2018 DeathFlu, and this is the smartest I've been this week.

Post by **Ralph @ Rayzoon** » Thu Feb 22, 2018 7:12 am

Are you getting better now? That flu this year is no joke

Please do this on JS4:

- open the manager tool and click 'Troubleshooting'
- check the DPI Override box and set it to 168

See if the GUI cut-off issue is gone now. If the GUI is too small for you, please use the GUI options in JS4 to set scaling to 150% or more.

GreyLion · Post by **GreyLion** » Thu Feb 22, 2018 9:46 pm

Success! But there's an additional step.

Sequencing the changes seems to make all of the difference. When I did the Troubleshooting change above, nothing happened, even after reboot, etc.

However -- I reset my Windows display scaling to 100%, rebooted, and the entire JS4 GUI then was visible -- no cut-off. This is in line with what andy_camb reported in the other thread. (Thanks, Andy!)

But it was unusably small, as were any other non-scaling VSTs I brought up. I could then once more re-set Windows scaling to 175% -- with DPI Override set to 168, as you suggested -- and the GUI was not cut off. Still too small, so I increased the JS4 GUI to 200%, it increased the VST window size in Reaper, and it seems to be perfectly functional.

So -- the fix, for me, at least, is to set to Windows' default size display first, then I can successfully make all needed adjustments. These changes still work after removing JS4 from the instrument track, restarting Reaper, and reloading JS4.

I'm going to fool around with this a bit more to make sure there aren't any subtle gotchas that I haven't spotted yet, but I think all is good. And I'll be purchasing tomorrow if so. Happy dance!

Thanks, Ralph!!!