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

Reverse flat accidental overlaps with other accidentals #21895

Closed
looptailG opened this issue Mar 11, 2024 · 2 comments
Closed

Reverse flat accidental overlaps with other accidentals #21895

looptailG opened this issue Mar 11, 2024 · 2 comments
Assignees

Comments

@looptailG
Copy link

Issue type

Engraving bug (incorrect score rendering)

Bug description

The reverse flat accidental can overlap with other accidentals applied to neighbouring notes.

Musescore file containing a couple of examples.

Steps to reproduce

  1. Add a note to the score, and apply the reverse flat accidental to it.
  2. Add another note to the chord, above the previous note, close enough for the accidentals to potentially overlap (for example a 6th above).
  3. Add an accidental to this new note. Some accidentals, like the sharp, will overlap with the reverse flat applied to the first note.

Screenshots/Screen recordings

image

MuseScore Version

4.2.1-240230937

Regression

I don't know

Operating system

Windows 10

Additional context

No response

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Mar 11, 2024

Stems from https://musescore.org/en/node/361680

Seems to be a Leland problem, I guess it is about the glyphs' metadata, esp. their cut-outs.
As far as I can tell non of the other fonts has that overlap

So might need to get reported against https://github.com/MuseScoreFonts/Leland

@oktophonie
Copy link
Contributor

Just so, I did the cutouts wrong. Raised here

@oktophonie oktophonie closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants