Palette too small!
I just updated to MuseScore 2.0.3 and now the palettes are too small and so is the play button and basically the whole panel at the top! I am running MuseScore on Windows 10.
I just updated to MuseScore 2.0.3 and now the palettes are too small and so is the play button and basically the whole panel at the top! I am running MuseScore on Windows 10.
Do you still have an unanswered question? Please log in first to post your question.
Comments
My guess is you have two monitors attached, and MuseScore is using the resolution of wrong one. Try disconnecting the one you aren't using. We are researching a better solution to this.
if that doesn't help, please post more details - tell us how big your monitor is, what resolution it is, and add a screenshot.
In reply to My guess is you have two by Marc Sabatella
I'm having Palette Text problems also! Also some of the tool bar text is too small. Any Help would be appreciated>
In reply to I'm having Palette Text by basssalad
See my response above. Do you have a non-standard monitor configuration? Normally MuseScore figures out your monitor resolution and does the right thing, but in a few rare cases it gets confused, and you may need to give MuseScore help understanding. Start MuseScore from the command line, and use the "-x" option to specify how much larger you need your icons (eg, "-x 2" to say you want them twice as large).
If that doesn't work around the problem, please provide more info - what version of MuseScore, what OS, as much info as you can about your monitor configuration, etc.
In reply to See my response above. Do by Marc Sabatella
I have a single screen 1920 x 1080. I fixed the tool bar from Preferences menu but not the Palette.
Windows 10. I'm not sure how to start from the command line.
In reply to I have a single screen 1920 x by basssalad
https://musescore.org/en/handbook/revert-factory-settings
Scroll down to the section marked "MuseScore 2.0 through 2.0.2".
This shows how to run from the command line. However it is for a reset to "factory settings" with the -F option. Instead of -F, key in -x "scale factor". I imagine "scale factor" should be a number such as 1.0 (for no change), 2.0 (to double the scale), 1.5 (to increaseby 50%), etc.
Also, see https://musescore.org/en/node/38301 for all the command line options.
In reply to https://musescore.org/en/hand by jim.weisgram
Hello, this is a big issue too on Ubuntu 18.04 LTS. It was working fine but suddenly all the toolbars show very small icons. I tried to reset to "factory defaults" with no luck, and also I lost some settings such as the list of recently opened files, and temporary scores. However, with the -x option I was able to see the toolbar with normal sizes again. Thanks.
I have no clue how this started but I have a HDMI 32 inch monitor which has the HD resolution of 1920x1080. I suspect this issue is due to NVIDIA drivers not working properly.
My Musescore version is 2.1.0
871c8ce
In reply to Hello, this is a big issue… by jgarciab80
Try also -D 69 (this the calculation for DPI of your screen)
In reply to I have a single screen 1920 x by basssalad
In order to help further, we still need you to provide the MuseScore version, as much details about your monitor configuration as you can come up with (eg, how is it connected, what is the actual size in inches so we calculate the dots per inch, etc).
Hello, I have this problem also after downloading the latest version today, although I am using a 43" TV as a monitor...
...Palette sizing would be great!
In reply to Hello, I have this problem by Joe Chiriaev
Yes, it seems to be a known issue with using a TV as a monitor that resolution information is not reported properly on some systems. Workaround is, as mentioned above, to use the "-x *(scale-factor)" command line option to scale things - like "-x 4" to make things 4 times bigger, etc.
In reply to Yes, it seems to be a known by Marc Sabatella
It's 2021 and ther problem still exists in 3.6 - is there any progress on fixing this without using a kluge?
In reply to It's 2021 and ther problem… by charlesfphill1
No, it appears some systems do still reporting this incorrectly, so far neither Windows, Linux, nor Qt have fixed whatever problems exist that cause this to happen. We just report the news, we don't make it, but at least we do provide those workarounds.