Bug 9.16: Texts in controls of band 1 in MEqualizer are blurred

[Celphor]

Hi,

in 9.16 the texts in the controls of band 1 in MEqualizer are blurred in the upper half . Looks like a buffer overflow. I see this only in MEqualizer, not in MDynamicEQ etc. (Win 7, 64 bit, Intel Graphics + GPU). Didn't try without GPU, which never made problems in the past on my computer.

Can anybody confirm this?

[DarkStar]

Which Style(s)? Can you post a pic?

It looks OK here (Aluminion, 100%, 90%, Windows 7, 64-bit, NVIDIA graphics):

[Celphor]

Hi,

oh, it seems only to appear in Aluminion style when Y = 100%

[MeldaProduction]

Hmmm, now that's odd! It's not blurred, it's clipped. It looks like it lost one/two pixels on the top, which is just weird. I checked in Win 10 and newest Reaper and it all seems just fine. Note that Reaper doesn't support HiDPI apparently. Could you try another host? Could you try disabling GPU acceleration in Settings/Settings? (plus compatibility mode)

[Celphor]

Mh, it is not in every instance. Can you copy in these settings and try?

EDIT: It happens also in VSTHost, so it is not a Reaper problem

Code: Select all

78DAAD55616FDA3010FDDE5F11F97B8943124825A0A25DB3561A2D2AA8DD3E7AC410ABC64E6DA7D0FEFA9D9DA40B1DAD9006124AFC72F7EEDDE5D9199C6FD7DC7BA14A33298628E860E451B1901913AB212ACDF23441E7A393C1E4EAB9249CBD412035061E6AEF52724E0A4DB30B22323D2582F22182F477FC9EAD72D3C68551F00C28AE04F9CD69E6E09CF0E58A30E1160551644D0D55192D4C0E7A5A501DD4095BD84C2ECD8C985211E3F463341A7C57A4C84783423261BC3B6052430439CF36B78FFB01EE23CFBC167488AE41E094688DBC9FB6F51007B87B767616F77AC8FB55915D13B596822DB43F1AF88EB2616EF7B0877B4AC993E3ED76823809FADD24EE26C15179E3A4D78F22600D930378BFE20A3B3888C320EE63E8FE881AC34E148549D2078571F700DEFA6DF5F6B2FE909BF79705C4717C10B15FD9E164305694686F42B66C0D36BE971B6DEDE5DB2782F05770B637E6454E6C619841035EE64480832732030913B6457F9B0F9AFBC79C8A6B9665B432F14C966A01D120EC91894C6EE695DB8008444E155D320EDE854DE47D536403D78ADDB6307573483959E90BA810418DED476FFA9F85451FC3FC76315B5A2EA8D65261BB49254C1A633C0EA234DDED2A659CBB9B3B381814CB681D0D887DB56E70DE2C971B873F105ED20A9BE76CF1641BF15BC5822F8AE17D35F6B2748FC2121E8525FA1F9699147205C757E3B6602719025C9AAE4A6057C3FD5085040D923448B742D2D4EA7048689134B5FF1A8986C8AE1D627DD1B81BDCDF3A96ED66B895867E802625376CDA1CB915E4EEBCF1966910749AE0EC02B91588B9958282936FC4042ADD95C65E1E5966F2896DDE6E0DAF6DCBBA6BBF09818CA2341BBB9A3773B6BD55DD3C30CD605675D28D80D056542FFA346A435EE852AAF5BCB5CBDB736DA5FB8D889DFAD57C77996BAD0750D7F9B6D16A763044FFDF8FEAE8E40FF6EB4CC6

[MeldaProduction]

it does that with these settings!!!! Now that's something to fix!!

[Celphor]

Well, it shouldn't get boring

I'm pretty sure it didn't happen before 9.16

Happy hunting

[MeldaProduction]

Hehe thanks, found it . It was a little fix for an OSX bug, that got into Windows release as I didn't think it would mess anything and voila... it did .

[DarkStar]

I've been told that the most dangerous change to make to any code consists of 5-7 lines.

Below that and the probability of error diminishes. Above that and you tend to give it more attention and test it more thoroughly.

[Celphor]

#ifdef madness

[MeldaProduction]

hehe actually the worst bugs have exactly ONE character ... Like "," instead of ";". These are things one looks for for days ... Whis one was actually "+1" .

[Tagirijus]

hehe actually the worst bugs have exactly ONE character ... Like "," instead of ";". These are things one looks for for days ...

I just code as a hobby ... but yeah ... even me knows this situation, haha!

[Tagirijus]

I just found out that in MMultiBandLimiter the "Mode" and the "Character" text is also weird.

[MeldaProduction]

That's probably the same thing .

[Tagirijus]

Alright, thanks! (=