Microscopic Tempo symbols

• Aug 29, 2018 - 06:48

I dreaded having to set a tempo again, but now I need to.
The problem is that there are 6 choices of Tempo, where this, that or the other is equal to 80. But there's no way to tell what is equal to 80 because the synbols are so small you need an electron scanning microscope to see them. No kidding, with my 3.5x reading glasses AND my 1.5x reading glasses stacked on top of each other I begin to notice that the 6 synbols are actually different, but I still can't see what they are.
The previous time I set tempo I was forced to try them one by one.
Maybe I if could find my big magnifying glass...
I have trouble enough seeing notes when the page fits the width of my screen, and these symbols, I kid you not, are about 1/4 the size of the notes in the screen at that zoom level...


In reply to by Jojo-Schmitz

That's useful, thanks; but I'm talking about the size of the icons to choose from; they are not text; they are graphical, and invisibly small. I'll try the zoom... No, the zoom acts on the edit window. What I'm talking about is the menu that pops under Tempo in the Palettes panel.

In reply to by cadiz1

I did exactly as you suggested.
The size of the symbols IN THE Pallettes MENU did not change.
It is graphical.
It is an issue.
It needs to be Fixed!

Is bug reporting here of any use?, or is this forum an organized brick wall?
It seems everything I report or suggest is either dismissed as irrelevant or argued down.

In reply to by danw58

Well, it just took a moment longer to understand your issue, no reason to get angry. Also please understand that almost all people here help on a volunteer basis, and that you are not at all and in no way entitled for receiving any support at all, this is the price to pay for free software...

Back to topic: Seems Musescore doesn't detect your screen resolution properly, you can force that by using the command line options -x or -D, see https://musescore.org/en/handbook/command-line-options

In reply to by Jojo-Schmitz

Sorry, I just don't have the time to go through such huge documentation for hacking the app in command line. Not to speak of the fact that the font they used for the command line options is so small that to read it I have to zoom the manual page to 200%...

I did solve my problem, using Gimp, so I'm not asking for
help; I am reporting an issue; period.
I stand on that this is an issue that needs to be fixed.
Not by me learning how to hack the app.
Needs to be solved by the developers making those icons larger.
Full stop.

In reply to by danw58

And you're not the first to report this particular issue. Thanks for reporting it again though.
It might be fixed already for the next major version of MuseScore, which uses a newer version of Qt, new enough to better detect high DPI devices and therefore getting the scaling right automatically.
Until then there's the command line options as a workaround, which you got told about within 30 minutes, which I'd call very fast and decent support, wouldn't you agree?

In reply to by Jojo-Schmitz

Yes, you're right. I just felt like you were discounting the importance of what I was reporting, I guess. Ok, never mind. I'm getting really tired. Too many nights I've been spending on MuseScore. Not enough sleep. I could do this when I was young, but at 60 it's a killer.

In reply to by danw58

Well, I AM considering "going PRO", buying the full version, or however it works. And I worked for years in an Open Source project, so I'm familiar with doing work for free. That doesn't mean there needs to be any concept of "indebtedness" to be paid for in subtle ways. And if there is, then it is NOT "free", exactly.
I'm taking time I do NOT have, to report issues. I just hope they are being received, just like I wholeheartedly welcomed bug reports when I was an Open Source developer, and never shamed anyone for the fact they were downloading my game for free. Even today I do a lot of work for free, though not software... All these Things I design and give away for free:

In reply to by danw58

Don't go PRO out of frustration, because there isn't a pro version of MuseScore (the program) and you'll just be frustrated again at having thrown away your money.

You get the full program, for free, always.

What you, as being an open source developer, are likely aware of is that software depends on other software and libraries. For MuseScore, anything graphical is built on top of the Qt-libraries allowing it to go cross-platform.
The 2.x branch is using a (by now) relatively old version of Qt (5.4) in which resolution detection, especially with multi-monitor or High-DPI (such as retina) displays is flawed. Sure "the devs should fix everything" and with MuseScore they do so at quite a decent pace.
But they don't often go into the underlying libraries (especially one as big and complex as Qt) to patch (or backport) stuff in there if it can be worked around in code using a command line parameter in a mere fraction of the time.

Meanwhile a bunch of that detection code has been improved in Qt and the next major version (3.0) indeed now links against that newer library. So your report has been heard and as far as within the capabilities and time of the developers already been addressed in the upcoming version.

In reply to by jeetee

Well put; yes, I am aware of libraries... That's probably why I'm not a developer anymore; I got sick of having to spend days and weeks learning a new library for every little new thing I wanted to do... The game engine I was working with depended on dozens upon dozens of libraries..
Got it. Thanks!

In reply to by danw58

It's hard to know the scale of your image, but on the surface, it looks pretty normal to me - that is, I think MuseScore is detecting your monitor resolution properly. If you prefer the icons on this palette to be larger, create a custom workspace using the "+" button at the bottom, then right-clicking the palette, Palette Properties, and setting a larger scale.

Realistically, though, there is no reason to bother with the palette at all for tempo markings. Just hit Alt+T to enter tempo as described in the Handbook, and the correct note value is filled in for you.

In reply to by Marc Sabatella

Well, it depends on monitor size, and age also. The Qt library probably doesn't take these two into consideration. However, the size of the symbols is out of proportion with the "= 80" next to them. I see that the heigth of the stem is as high as the numbers, as was probably intended; but intended doesn't mean right; the bodies of those notes are a lot smaller than the stems, and the stems too thin compared to the line width of the font. IOW, I insist: it is not right.ly proportioned.
But yeah, if the pallette is not needed that's fine, but if it is there no one will suspect it is not needed. I know a lot of developers try to provide as many ways to obtain the same command as possible: A menu item, then an icon, then a command windo, then a dialogue, then a mouse gesture, all to invoke the same function; but this doesn't add value; it subtracts and divides value. They end up with apps that have so many keyboard shortcuts you can't even breathe near the keyboard without something unintended happening. I'd remove the pallette thing if it isn't the preferred way.

In reply to by danw58

In theory, the resolution detection used in MuseScore results in the same physical size for the palettes no matter your screen resolution or monitor size. Same for the representation of the score. That is, the clef on the palette is exactly 8mm tall (or whatever, totally made that up) regardless of your monitor, if all is working correctly.

Anyhow, I would agree the notes in the tempo indications seem small in comparison to the text, not just on the the palette but on the score as well. But that's the size the font designer decided they should be for whatever reason. Here you might wish to use the custom palette facility described in the Handbook to create you own customized versions using larger font for the notes.

Anyhow, your question was about palette, and the process I gave originally was for dealing with that.

As for not providing both palette and shortcuts, this is contrary to how most people people expect and what most UI design guidelines call for. Palettes are there for discoverability, keyboard shortcuts for efficiency, and they both have value. If you are concerned that there are too many shortcuts, you can go to Edit / Preferences / Shortcuts and undefine as many as you like. Most other users complain there aren't enough shortcuts, though :-)

In reply to by Marc Sabatella

Gottcha. It's like people complaining about their water not being cold enough and their coffee not being hot enough, so the rest of us get our teeth frozen and our lips burnt. :-) No, I wasn't complaining about too many shortcuts in this app. I was thinking about Blender3D, specifically. I've been using Blender for about 15 years, and I still accidentally hit keys that do weird things that I'm totally lost as to what happened, and going into states I don't know how to get out of so I have to kill the app with ctrl-alt-del.

I agree, the icons are very small. The dotted ones are particularly troublesome, since the dot is almost invisible. My solution has been to memorize which is which.

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