Tiny visuals in palette - SOLVED
Is there a way of increasing the minute graphics in the palettes? I'm using a 32" HDMI monitor (OSX) and they are pretty well illegible at this resolution.
OK so I had tried adjusting the palette size in preferences/advanced but did not know that one had to close the program and reopen in order for it to take effect./ After all, there is a button that says "apply" - and one would expect that to mean....apply!
Anyway sorted now
Attachment | Size |
---|---|
Screenshot 2021-07-28 at 12.38.38.png | 53.77 KB |
Comments
Click on the three dots, choose Palette Properties, adjust width and height. You can do this individually for different palettes.
https://musescore.org/en/handbook/3/palettes#palette-menu
In reply to Click on the three dots,… by underquark
Thanks but clicking on the three dots didn't give me that option - see png
In reply to Thanks but clicking on the… by [DELETED] 37205164
Click on the three dots for the individual palette.
In reply to Click on the three dots for… by underquark
Ah that's useful, thank you! I can scale up the entire palette generally and increase scale on frequently used.
FIW, if you were only seeing small palettes but everything else normal - toolbar icons seemed usable at the defaults, the score is same size as printed when viewed at 100%, all dialogs seem normally proportioned - then what you did is the correct fix.
But that is almost never the case. More often, everything is too small, because you OS is not communicating the resolution to MuseScore in the expected way. So the better solution is to use the "-D xxx" command line option when starting MuseScore, where "xxx" is the true resolution in DPI. Also some OS's such as Windows provide properties you can set on the executable file for the application to control how high DPI scaling works, and on any given system, a different setting there might solve the issue more generally.
In reply to FIW, if you were only seeing… by Marc Sabatella
Thanks Marc - I think this may be the case, but I'm on OSX Mojave - how do I start up in this way?
In reply to Thanks Mark - I think this… by [DELETED] 37205164
Same way. See https://musescore.org/en/handbook/3/revert-factory-settings#instruction… and instead of
-F
use-D xxx
In reply to Same way. See https:/… by Jojo-Schmitz
That says nothing about screen res, and states that it will reset ALL settings to factory, not what I want to do. I want to improve the resolution of the screen, if this is not possible without re-setting ALL my prefs then I'm not going to do it.
In reply to That says nothing about… by [DELETED] 37205164
That's why I wrote you should not use
-F
But the procedure for other commandline options is the very same, and this is the only place in the handbook where this is decribed.
The command line options are described at https://musescore.org/en/handbook/3/command-line-options
In reply to That's why I wrote you… by Jojo-Schmitz
Sorry Jojo - I'm sure you're trying to be helpful but I simply do not understand what you are saying......and as to it being the only place in the handbook where "this" is described - what exactly is "this"? it ain't the screen resolution. Sorry for being dumb.
In reply to Sorry Jojo - I'm sure you're… by [DELETED] 37205164
"This" is the description how to get to and use the command line. For the special purpose of reverting to factory settings, but if you replace the
-F
with any other option that descriptions is pretty genericIn reply to Sorry Jojo - I'm sure you're… by [DELETED] 37205164
The point of those instructions isn't to get you to revert to factory settings - it's just to teach you how to run MuseScore from the command line on macOS. If you omit the "-F", then it won't do the revert to factory settings, but you'll have learned how to launched MuseScore from the command line - that's the point of the article. Then you can add the -D xxx".
Regarding "apply" - it does apply those preferences that can be applied on the fly, but a few, like this one, are only applied on program startup.
In reply to Regarding "apply" - it does… by Marc Sabatella
Thanks for all your advice guys.
Well, I used to write hexadecimal in the 90s for midi stuff, MS-DOS was a daily distraction, so having to go back to command line status to simply adjust a screen res seems like a very odd thing to do. None of my other apps have this problem.
So I've tried starting from Terminal with various resolutions all the way down to 320 (!!) and I get nothing but a HUGE headerboard and everything on the left is fine, a sample of one res entered attached - something weird about this though because if I connect a 30 inch Cinema Display to my other graphic port the screen in Musescore on the HDMI shows correctly - ie - the top bar is at the same res as the rest of the program. Without the cinema connected and when I restart Musescore, it reverts to as second image.
So all in all a very odd state of affairs! OK so I know this is a free app so I'm not making a fuss out of this but it would be good to be able to use with this display without these headaches.
In reply to Thanks for all your advice… by [DELETED] 37205164
UPDATE - of course I was mixing up screen res with DPI - so I've brought it down to 100 and that appears pretty good - is there a way to save this in the actually start up of MS without having to got to Terminal every time?
And I see I have to keep Terminal open all the time otherwise it closes MS
Ta!
In reply to UPDATE - of course I was… by [DELETED] 37205164
Use an & at the end of the commandline to push the process into the background
If that doesn't keep it running when closung the terminal, prefix it by a
nohup
In reply to Use an & at the end of… by Jojo-Schmitz
Hmm neither of those commands did anything, never mind, I guess I can cope with Terminal open in the background
In reply to Hmm neither of those… by [DELETED] 37205164
nohup /Applications/MuseScore\ 3.app/Contents/MacOS/mscore -D xxx &
In reply to nohup /Applications… by Jojo-Schmitz
Genius! It was the spacing I left out after nohup, thank you JoJo
In reply to UPDATE - of course I was… by [DELETED] 37205164
Probably there is a way to tell macOS to use that option all the time. Both WIndows and Linux do, I'd be surprised if macOS decided to limit functionality in this way. Probably a general webs search for such info would turn up something. or it could be that, like I said, there is a property you can set directly, again like Windows does.
FWIW, I have about half a dozen different apps that have similar issues, some on Windows, some on Linux. The problem is there just aren't good standards for this, and MuseScore needs to work across three different OS's and across a huge range of different types of displays, so it's really not surprising not all combinations work perfectly out of the box. Any given app might happen to work well on most systems but will fail eventually when presented with the "right" system. Ideally, though, we'd have a better workaround than requiring the command line.