Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Small Tempo Note Font #785

Open
rothersgit opened this issue Feb 2, 2025 · 9 comments
Open

Small Tempo Note Font #785

rothersgit opened this issue Feb 2, 2025 · 9 comments
Labels
bug regression Regression vs. 3.6.2 or an earlier 3.7 workaround A workaround is available

Comments

@rothersgit
Copy link

rothersgit commented Feb 2, 2025

Adding a tempo marking results in the note font being too small

Image

The workaround is to change to note (not the remaining text) font from Edwin to Leland

Image

OS: Windows 7 Version 6.1 (Build 7601: SP 1), Arch.: x86_64, MuseScore version (64-bit): 3.7.0.13003487230, revision: GitHub-Jojo-Schmitz-MuseScore-8feb7ab

@rothersgit
Copy link
Author

Image Musescore 3.6.2

Image Musescore 3.7

Image Musescore 4.4.4

@Jojo-Schmitz
Copy link
Owner

Jojo-Schmitz commented Feb 2, 2025

Thanks (stems from https://musescore.org/en/node/374612#comment-1278275 ff.)

Other workaround: In Inspector Press "Reset Custom Formatting" (which resets the font to Edwin, that is the default for tempo texts, not Leland, but for the entire string, see also below)

The relevant score snippet is:

          <Tempo>
            <tempo>2</tempo>
            <followText>1</followText>
            <text><sym>metNoteQuarterUp</sym> = 120</text>
            </Tempo>

Seems that <sym>metNoteQuarterUp</sym> gets interpreted differently, gets a different font assigned?

Resetting font or custom formatting, replaces that <sym>metNoteQuarterUp</sym> with a Unicode glyph.

@Jojo-Schmitz Jojo-Schmitz added bug regression Regression vs. 3.6.2 or an earlier 3.7 workaround A workaround is available labels Feb 2, 2025
@rothersgit
Copy link
Author

Seems to be a Windows 7 v Windows 10 issue here as well.

With "Reset Custom Formatting" in 3.7 and Windows 10 the workaround works fine however with 3.7 and Windows 7 I get this !

Image
Might give another clue as to what's going on.

@Jojo-Schmitz
Copy link
Owner

Should depend on the font it resets to

@rothersgit
Copy link
Author

In both cases it resets to Edwin.

@Jojo-Schmitz
Copy link
Owner

That is strange indeed, as it works fine here on Windows 11

@Jojo-Schmitz
Copy link
Owner

Jojo-Schmitz commented Feb 3, 2025

With that <sym>metNoteQuarterUp</sym> it follows the Musical Text Font from Format > Style > Score.

Leland Text is different between 3.6.2 (v 0.52) and 3.x (v 0.77), that might explain the difference, but is the same on 3.x and Mu4/master, which is rather strange, as it doesn't explain the difference at all.
Unless master uses the Musical Font rather than the Musical Text font here (or rather: derives the Musical Font to used from the setting for the Musical Text Font, as it changes with that setting)?
Mu4 does do similar things with dynamics (i.e. takes those from the Musical Font rather than the Musical Text Font, for their better centering, IIRC)

@Jojo-Schmitz
Copy link
Owner

Tada! It is not "ScoreFont", as I put it in

QFont::insertSubstitution("ScoreFont", "Leland Text"); // alias for current Musical Text Font
but "ScoreText" as it is referred to in multiple other places

@Jojo-Schmitz
Copy link
Owner

Hmm, no, it isn't :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug regression Regression vs. 3.6.2 or an earlier 3.7 workaround A workaround is available
Projects
None yet
Development

No branches or pull requests

2 participants