musescore / musescore/MuseScore
"Divide Measured Tremolo" collides with notehead
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
- Write a note on the second space of a staff (treble clef - A)
- Add "divide measured tremolo by 6"
- Dots are placed directly on notehead
The placement of these tremolo divisions are inconsistent based on note vertical placement, it would be ideal if they had more consistent placement as most articulations do
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
OS: macOS Sequoia (15.5), Arch.: arm64, MuseScore Studio version (64-bit): 4.6.0-251880327, revision: github-musescore-musescore-4965cf1
Regression
No.
Operating system
MacOS15
Additional context
Originally reported in https://github.com/musescore/MuseScore/issues/28651
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.
Research direction
Reproduce the engraving bug in MuseScore using a treble-clef A and a divide measured tremolo by 6. No source file or test is named; trace the tremolo division placement and verify that its dots no longer collide with the notehead and remain consistent across note positions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100