musescore / musescore/MuseScore
Guitar string numbers/fingerings overlap with other elements
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
- Add a note
- Apply a string number marking and move it "inline" to the left or right of the note
Expected behaviour: Other elements (notes, rests, bar lines, ...) move if necessary to accommodate the string number.
Actual behaviour: The string number is drawn on top of everything else if there is little space.
Same behaviour occurs for right-hand fingerings but not for left-hand fingerings.
Supporting files, videos and screenshots
Here is a score that I created in MuseScore 3.6.2 for testing purposes: Guitar-String-Numbers-MS3.zip
The only non-empty bar looks like this:
Placing string numbers next to the note they refer to is very common in guitar music, especially with chords where only some strings are marked as in my example.
When I open the score in MuseScore 4.5.2, here is what I get:
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc
Regression
Yes, this used to work in MuseScore 3.x and now is broken. Same in all versions of 4.x
Operating system
Windows 10
Additional context
There is a workaround in MuseScore 4: define a user text style with circled numbers and the same font size. Those custom string numbers interact with other notes, rests etc. as expected.
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.