3.x Nightly AppImage 10/15

• Oct 15, 2020 - 12:17

Time signatures and clefs look blurry. Blur.png

Comments

• Oct 18, 2020 - 15:34

Do you mean on your screen, or in a PDF export, or in a print? Could be you need to toggle the setting of the anti-aliasing in Edit / Preferences / Canvas.

Reply

• Oct 18, 2020 - 19:02

Doesn't matter. If I'm right, it is nothing new, nothing connected to any specific change made, it's just that the nightly builds and the regular builds keep their preferences separate. So if you're saying you don't see this with the release build, that would be because that preference is set differently in that. Whatever preference setting you make in a release build, stays in all updates to that release build. What preference setting you make in a development built, stays in all updates to that development build. So you probably just need to make sure you are using the best setting for your particular OS, display, and device driver. Some do better with the anti-aliasing on, others with it off, and that's why we provide the preference.

Reply

• Oct 21, 2020 - 11:30

Because MuseScore renders at 100% itself, so it draws the vectorinformation of the musical symbols onto a pixelGrid (the ScoreView) as perfect as it can (with or without antialiasing as configured). This rasterized image is then sent to your graphic subsystem of your window manager to show it on screen.
This is where the 150% of your system settings come into play. It upscales the given image (no longer a vector format) to 150%. Each pixel in the original drawing gets mapped to 1 and a half pixel on your screen. This is where the artifacts come to life.

Reply

• Oct 21, 2020 - 16:33

a comma , is a separator on a command line so I don't think you can enter any number that uses a , in it. I'm not sure if local settings allow for , rather than the . in the US as a decimal. I've never seen a DPI any way but integers since you don't really expect 0,78 of a dot to be drawn.

Reply

• Oct 21, 2020 - 16:26

No, but the more exact it is, the more precisely 100% zoom will actual reflect the true size of the score. Rounding to the nearest integer or really even the nearest "round" number is fine. 100 DPI is standard, so no surprise a value only slightly different from that wouldn't have a noticeable effect. Seems the observations about your use of OS-level scaling are more to the point - your OPS is apparently no doing a very good job here. So if you generally are accustomed to 150% scaling done by the OS, instead try setting that back to 100%, but increase your DPI value by 150% (so, for instance, "-D 135". This should achieve the same thing but the scaling will be done by MuseScore.

Are you saying the standard AppImage behaves differently in this regard? Would be useful to trace through all of these things to understand what is different - whether they are running as different users, in different environments (and hence different environment variable settings), with different OS-level scaling options, different settings of the anti-alias option within MuseScore, etc.

Reply

• Oct 21, 2020 - 16:40

When I set it back to 100% it works finely, but everything looks too small in every window normally and I don't want everything in my OS to look so small... That's why I raise the scaling.
I run Manjaro KDE Plasma, probably latest Plasma version, I have only 1 user in this OS. Here is what I tried after I read your message, 150% global scaling, and it resulted in the same stuff as before:
Konsole.png

Reply

• Oct 21, 2020 - 17:06

Not sure what your images is supposed to be showing, that looks like normal console output. The question is, what difference did it make?

If you need the OS to scale things for you overall, fine, go ahead and do that, but then see if you find a way to force that off for MuseScore specifically, and let MuseScore do the scaling then by choosing the appropriate value for DPI. Things are tricky when scaling is involved, so instead of worrying about calculations, I recommend just using trial and error until the score viewed at 100% is actual life size (as in, literally hold up a piece of paper next t your score to see if the sizes match). You can also try setting or upsetting the environment variable QT_AUTO_SCREEN_SCALE_FACTOR (set it to 1, or completely unset it).

Unfortunately there are so many different variations in how different systems handle scaling it's virtually impossible for a single cross-platform application to always look perfect on every screen, but that's why there are so many controls available, to allow you to customize for your own unique system.

Reply

• Oct 21, 2020 - 18:54

Unfortunately I don't have any better advice than trial and error using different combinations of all of these variables: the system-wide OS scaling, application-specific-scaling by the OS, different values for the "-D" option to MuseScore, setting or upsetting the environment variable, setting or upsetting the anti-aliaising option.

As I said, if it's working in a different AppImage or other installed version, try to determine the settings for each of these in the working version, then compare to the non-working version, that might give clues. But if the only working version is an installed version as opposed to an AppImage (this would be rare), it won't be an apples-to-apples comparison, because they will be using different libraries, and maybe that will turn out to be the relevant difference.

Reply

Do you still have an unanswered question? Please log in first to post your question.