musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.29k stars 2.66k forks source link

UI text garbled in some cases; all characters in bold font rendered off by one; making Hebrew look like Arab #24287

Open ran-dom-guy opened 2 months ago

ran-dom-guy commented 2 months ago

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

  1. Create a new score or check instruments
  2. Return

Supporting files, videos and screenshots

image image image

What is the latest version of MuseScore Studio where this issue is present?

4.4.0 revision 0fcd11b

Regression

No.

Operating system

Windows 11 x64

Additional context

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.0-242390800, revision: github-musescore-musescore-0fcd11b

Checklist

ShibuyaCyana commented 2 months ago

Also encountering this, do we have reliable steps to reproduce it? To me this only happens with Libertinus Serif (!), and if I change UI font or size in Preference, it would become back to normal. However reverting to previous problematic font size combination would mess it up again.

If I quit with a size that behaves normally, next time MU starts, it's the previously normal size that become messed up.

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.0-242390800, revision: github-musescore-musescore-0fcd11b

cbjeukendrup commented 2 months ago

Unfortunately we don't really know what's the root cause of this. Might even be something with graphics drivers. It looks like only the bold font, which is actually semi-bold, is affected.

However there are two builds that you can try to see if they fix the problem. Both were actually targeting other problems, but perhaps we're lucky and one of them fixes this problem too.

  1. https://github.com/musescore/MuseScore/pull/23925 - This is from 3 weeks ago so doesn't contain the latest fixes; and this build contains changes that create other new problems; but it switches to a new font engine (DirectWrite instead of FreeType), which might not have this issue. If that build indeed fixes the problem, we will try to fix the new problems caused by it, and then apply that as the fix.
  2. https://github.com/musescore/MuseScore/pull/24095 - This switches to a slightly newer version of Qt. Perhaps it was a Qt bug that they fixed in that version. This update also causes other problems, so can also not easily be integrated, but again, if it fixes this bug, then we'll do our best to integrate it asap.

See How to download test builds from pull requests for instructions about how to test these builds.

cbjeukendrup commented 1 month ago

@ran-dom-guy @ShibuyaCyana @Yanko64 It would be great if you could try out the solutions mentioned in my previous comment, to see if one of them helps!

ShibuyaCyana commented 1 month ago

Busy days, sry. Tested with Libertinus Serif, the DirectWrite version seems to be free of this problem, while it persists in the newer Qt 6 build. I wonder which font our OP is using and whether changing font (or font settings) will also solve his problem (or at least temporarily).

cbjeukendrup commented 1 month ago

Thanks for testing! Then we'll try to get the DirectWrite change over the line.

Jojo-Schmitz commented 1 month ago

Can't we give this issue a better title for better discoverability?

Esp. the connection to Hebrew/Arab seems entirely missing hre?

bkunda commented 1 month ago

I think we need to continue exploring options with this one as the proposed PRs introduce new problems that will affect everybody on Windows, which I'm not keen to implement.

I also understand there are workaround fixes for this (changing the UI font, or factory reset), which means we can take more time to address investigate better solution (I.e. utilising a different Qt version). Hence, re-allocating this to 4.5.

Jojo-Schmitz commented 4 days ago

Came up again in https://musescore.org/en/node/371234, there the workaround was to change the UI font away from Segoe UI (the default)