musescore / musescore/MuseScore
Incorrect beaming in specific situation with tuplet
Open
Nobody has claimed this yet.
engraving
P2
- 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
Enter a quintuplet over the whole 4/4 bars and write 16th notes.
Expected: notes are beams in 5 groups of 4
Actual: notes are beamsn in 4 groups of 5
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
Main
Regression
No.
Operating system
Any
Additional context
No response
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.