Score size is too big - Musescore 4 Linux
Have just recently downloaded and installed the AppImage on Debian 11. I'm using the MuseScore-4.0.2.230651545-x86_64.AppImage
When I open scores on my primary monitor (3440x1440), they are zoomed in way too far; even going to 5% I can barely see a whole note. I've also tried zooming to Page Width, which also stops at 5%. The UI is the normal size.
When I move the window over to my other monitor (1920x1080) (even without exiting), the zoom levels function how I would expect. If I move the window back to my big monitor, and try to zoom again, it gets all wonky again.
I've tried testing with a few of the items from "Sheet music sorted by Rating".
https://musescore.com/user/19710/scores/33816
https://musescore.com/user/12461571/scores/3291706
| Attachment | Size |
|---|---|
| Screenshot from 2023-05-01 20-16-22.png | 123.14 KB |
Comments
Getting things to scale correctly in the face of different display sizes and resolution and different OS behaviors is a bit of a crapshoot. It seems your OS (or window manager) must be presenting MuseScore with incorrect info regarding the scaling. See if you can find the scaling settings in your OS / window manager and play with them. You can also use the environment variable QT_SCALE_FACTOR to scale the UI if your OS-level settings end up making the UI itself too big or too small.
In reply to Getting things to scale… by Marc Sabatella
Thanks Marc,
Completely understandable--especially with Linux and random displays.
The scaling was set to 100% in GNOME, and the UI was fine, but with that advice, I found that if I drop the refresh rate on my widescreen to match the regular monitor (60), the issue is resolved. I see the smaller monitor is also being recognized as monitor 1 (even though the widescreen is primary display), so future searchers can test display order too.
Debian 11 GNOME 3.38.5 NVIDIA RTX 2070
In reply to Thanks Marc, Completely… by joshmfranklin
Glad you figured something out, but how strange that refresh rate affected anything about this! Seems like a bug somewhere, but I doubt MuseScore is dealing with anything so low level; I'm assuming an issue like that is either within Qt or - more likely, perhaps - in the window manager or somewhere lower level still.