Rehearsal Marks are Improperly Formatted in Display, and Don't Edit Properly
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
Occurs for me in all scores. The outline around rehearsal marks (if they are longer than a few characters) does not surround them properly in the display. (It prints okay.)
Also, when I try to edit those rehearsal marks with longer text, the cursor doesn't get placed where it appears to, so that the text is impossible to edit correctly.
I've attached a score that shows the problem, and also a screen capture that shows the on-screen display on my computer (in case it appears differently on yours).
64-bit Windows 10, current version of Musescore
| Attachment | Size |
|---|---|
| Rehearsal Mark Formatting and Editing Problem.mscz | 13.14 KB |
| Rehearsal Mark Formatting and Editing Problem.PNG | 7.91 KB |
Comments
It looks fine for me on screen, not like your picture at all. Your chord symbols look bad also, characters are overlapping each other, but that here too it's fine for me. And I am using 64-bit MuseScore 3 on Windows 10 as well. So I'm not sure what could be going on here. Best guess right now is that maybe you have some sort of bad version of the FreeSerif font installed on your computer. Can you check to see if you have that font installed and remove it if so? Also try changing from FreeSerif to another font for these rehearsal marks, using the Inspector. And also, try exporting PDF and/or printing and let us know if the results are any better. Could also be some sort of issue having to do with your monitor resolution and the OS scaling for that.
For the record, here is how it looks for me:
I'm seeing the same things a Marc, so it isn't specific to MuseScore 3.0.4 64 bit on Windows 10, which is what I'm also using. It's something about your machine.
In reply to It looks fine for me on… by Marc Sabatella
At some point -- likely a closing and re-opening of Musescore -- the problem disappeared without intervention from me. I'll let you know if it happens again (and if I can determine anything about what triggers it).
Thanks!