musescore / musescore/MuseScore
"[2 or 4]-bar repetition": with octave (s) increase/decrease: can't see the dotted line
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
- Put it "[2 or 4]-bar repetition" in the score
- Put an octave(s) up/down above it
Actual result: there is no dotted line indicating the duration of the sign.
Expected result: this should not happen.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/b21b8a02-d7e1-4e68-a186-163d2626fbc9
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc
Regression
I was unable to check
Operating system
Windows 10
Additional context
Originally reported in #28697
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 issue in MuseScore Studio by placing a 2- or 4-bar repetition marking with an octave marking above or below it, using the attached example as reference. Trace the engraving and rendering path for these markings and verify the dotted duration line is visible when the octave marking is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100