Palette names are scrambled and nearly impossible to read (Windows 7)
Reported version
3.3
Type
Graphical (UI)
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
Steps to reproduce:
1) open musescore
(The bug immediately manifests itself at this point.)
Expected behavior:
The names of the palettes that appear on the left hand side of the window (ie "Clefs", "Key Signatures", "Time Signatures", etc) appear clearly and legibly.
Actual behavior:
The names of palettes appear garbled and range from being legible to almost indecipherable.
Version number:
3.3.0.8737
Revision number:
OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.3.0.8737, revision: 4761df6
OS version:
Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
running on a Lenovo Thinkpad X61 tablet
GPU: Mobile Intel(R) 965 Express Chipset Family
| Attachment | Size |
|---|---|
| full window.PNG | 135.57 KB |
| just the problem area.PNG | 19.07 KB |
Fix version
3.3.4
Comments
It is possible this is some sort of Windows 7 compatibility issue - and I assume you are well familiar the dire "update or else" warnings regarding Windows 7 so I won't bore you with that. But I believe other users have used the new palettes successfuly with Windows 7. Maybe you are missing one of the service packs or some other necessary update? I encourage you to ask on the Support forum, where many other users who have experience in such matters may be able to help.
It is definitly not a pure Windows 7 issue, as i don't have it
Came up again in https://musescore.org/en/node/296685
As a workaround, please try the instruction in this comment:
https://musescore.org/en/3.3#comment-956392
It seems to have helped another user who reported a similar issue on Windows 7.
I tryed the solution with batch file set QT_OPENGL=angle and now the palette names police is correct.
Now how I do to start MS3 without the batchfile ? Can I change something to start MS3 directly.
Thanks for your help
Pierre
Not for the time being, and it also is not clear yet whether (or when) it has to be 'angle' or 'software'
In reply to Not for the time being by Jojo-Schmitz
Ok, It doesn't matter. I continuing tu use the batch file.
Thanks a lot.
Came up again in #297107: Palette text problem with last two revisions of MuseScore 3 .
And again in #297226: Can't read the pallet in latest update
In reply to And again in #297226: Can't… by Jojo-Schmitz
I think the workaround batch file quoted in a couple of threads of this discussion was missing something
This is what I copied (and checked several times when it didn't work)
@echo off
QT_OPENGL=software
REM or
REM QT_OPENGL=angle
REM start "" "INSTALLPATH\MuseScore 3\bin\MuseScore3.exe"
should have read
SET QT_OPENGL=software (or angle)
The "Set" made all the difference
When I tried it that way it worked as hoped
https://musescore.org/en/3.3#comment-956392 has that "set"
@echo off
set QT_OPENGL=angle
REM or
REM set QT_OPENGL=software
start "" "C:\Program Files\MuseScore 3\bin\MuseScore3.exe"
In reply to I tryed the solution with… by Polop30
While it seems from other comments that we cannot currently use this workaround without using the batch file, you CAN change the icon of the batch file so that it looks the same as the regular icon that starts musescore 3. What I did was as follows.
1) Create a shortcut of the batch file.
2) Right click the shortcut and select "properties" from the drop down menu.
3) Under the "shortcut" tab, click the button that says "Change icon..." (it is in the middle of the window at the bottom ish area).
4) Click the "Browse..." button.
5) Navigate to C:\Program Files\MuseScore 3\bin
6) Select the file named "MuseScore3" and click "Open". It will have the normal musescore3 icon. This is actually the executable that would normally start the program, but in this case we are just using its icon.
7) Click "OK" in the "change icon" window.
8) Click "Apply" in the "properties" window.
9) Close the "properties" window. (You can hit "OK" or "cancel" or just close it from the "X" button at the top right of the window.
(Steps 10 and 11 are optional)
10) You can now move (but NOT delete) the original .bat file you created if you don't want it sitting on your desktop. It shouldn't matter where you move it to, just as long as you don't delete it. You can also delete the original shortcut to start Musescore 3 that was on your desktop as well.
11) You can right click the shortcut to your .bat file and click "rename" to change it to whatever you want (like "MuseScore 3" if you want it to look exactly like the original icon)
For those who have this issue, could you please test this build without the workaround script? Similarly to nightly builds, this build does not need installation, just extract that archive and execute
bin\nightly.exefile.See https://github.com/musescore/MuseScore/pull/5489
In reply to For those who have this… by dmitrio95
I tested the nightly build you linked and it worked great!
@ArchitectOfThought, thanks for testing! Unfortunately it still appears not to work in some cases (like in this comment) so what I have done in that build doesn't seem to be a universal solution to this issue.
Could you please test also the following build? This time it should work correctly for everyone affected by the issue.
32-bit version:
https://ci.appveyor.com/api/buildjobs/1oy33h4ofuan666c/artifacts/MuseSc…
64 bit-version:
https://ci.appveyor.com/api/buildjobs/1k2hcrm5u6h1mt47/artifacts/MuseSc…
Fix typo in issue title.
In reply to Could you please test also… by dmitrio95
That issues is resolved in this nightly build. Is there going to be an update for this or do I need to figure out how to install the nightly build over my last release?
If I understand correctly the change that is being tested will go into a future release if it works and doesn't cause new issues.
You can use the link dmitri gave above, unzip the file and use that one until the fix is released, probably in version 3.4. You will need to copy the paths from preferences in your current version of MuseScore to the version from the above link if you want to keep you current file locations.
Fixed in branch master, commit ed4949c72d
_fix #296682: disable desktop OpenGL for Windows 7
Native OpenGL implementation often leads to QtQuick-based views
(such as QML-based Palettes) render incorrectly on Windows 7._
The fix will be released in 3.3.4 version which should be available within the next few days. Thank you all for your help!
Automatically closed -- issue fixed for 2 weeks with no activity.