musescore / musescore/MuseScore

Incorrect auto-positioning of the bowing marks

Open
#24,025 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P3
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

Bowing marks are placed not in accordance with established engraving rules for their placement in combination with other symbols, but in accordance with the order in which they were added by the user.
For example, the user first added the accent symbol to the note, and then up bow. In this case, the up bow will be placed above the accent. But if the user added up bow to the note first, and then the accent, then up bow will be placed under the accent.

Expected behaviour

It was expected that the bowing marks would be placed on top of all other markings (pause, string indication, fingering, open string/harmonic circle, articulation), regardless of the order in which the user adds them.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/41c1f630-2db9-41e1-aa4b-f9035a2186e2

What is the latest version of MuseScore Studio where this issue is present?

4.4.0-242260502, revision: github-musescore-musescore-75dc214

Regression

I was unable to check

Operating system

Windows 11

Additional context

I propose to merge the resolution of this issue together with #22797.

Also, please note that at the moment the bowing marks are automatically positioned under the pause symbols. However, in, for example, Dorico, the marks are placed above the pause symbols.
Снимок экрана (514)
Снимок экрана (513)

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.