LennarDigital

Omniphonix · Post by **Omniphonix** » Sun May 22, 2016 4:20 am

Omniphonix wrote:It's strange, after booting up and trying again today (having made no changes), I can't reproduce the issue. Anyway, will you post here when an update to 3.021 is released that fixes this issue?

Ah, spoke too soon, here it is...

And the version...

svenh · Post by **svenh** » Sun May 22, 2016 5:29 am

OK, so now the "nearly impossible" has happened to me too again. ;~)

Lennard · Post by **Lennard** » Sun May 22, 2016 1:11 pm

Well, thanks for clearing that up! So you get this bug only when high DPI mode in Studio One is enabled? Could you maybe send a screenshot of the Control Panel –> Appearance and Personalization –> Display setting in Windows?

And let me know what graphics card and drivers you're using?

svenh · Post by **svenh** » Sun May 22, 2016 5:27 pm

Since I thought that 3.020 would solve the problem, I enabled high DPI again so I have not really tested without high DPI. And it will take some time without high DPI to know the result, since the problem only occurs occasionally.

My graphics card is NVIDIA GeForce 9600 GT. I will e-mail you a screenshot.

4damind · Post by **4damind** » Sun May 22, 2016 5:39 pm

I have an Intel HD4000 (i7 on-board GPU) with this bug and it's on Cubase 8.5 (Win10 x84).
Maybe that other plugins modifying the graphic context so Sylenth is using a wrong scaling (point/pixel whatever) for rendering fonts? Or Microsoft changed something with GDI+ so there is now a different behaviour how the graphic context must be used in combination with truetype fonts.

Omniphonix · Post by **Omniphonix** » Sun May 22, 2016 9:19 pm

I do not have high DPI (dual 2560x1440 displays, but they are not scaling anything) and I am using a Radeon 4850HD with the drivers Windows 10 downloads itself from Windows Update.

4damind · Post by **4damind** » Sun May 29, 2016 11:57 am

Is there a fix available? It's still not working also with 3.020

Lennard · Post by **Lennard** » Sun May 29, 2016 5:39 pm

Sorry about that, the rendering was changed in v3.020 (instead of v3.021), so you should try running v3.010 instead (just contact us for a link).

I've already located the problem and a fix will be ready soon.