musescore / musescore/MuseScore
Pedal lines can extend past selected endpoint when using voice > 1
@ajuncosa is already working on this.
Since Jul 16, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
If you are adding a pedal line to a passage involving multiple voices, and you select the start & end using Ctrl+click rather than a range selection, you can end up with a line that extends far past your selected endpoint. This happens if there is no note or rest in the selected voice immediately after the selected endpoint.
- Load attached score - pedal-voice.zip
- Click the voice 2 C in bar 1
- Ctrl+click the voice 2 B in bar 2
- Click a pedal line
Result: pedal line extends all the way through bar 4. That's because bar 5 is the next appearance of voice 2.
If you try the same test using the C & B in bars 5 & 6, the added pedal line goes to the end of the score, because there is no more voice 2.
The problem occurs only using list selection - range selection is fine. And even after the line is added incorrectly, you can still adjust it to the desired range - it's just the initial add that is incorrect. The problem appears to be unique to pedal lines - other lines work as expected.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/45ae1c54-8d2f-4256-9af5-973faa2b3d0b
In which versions of MuseScore Studio is this issue present?
4.7 nightly, 4.6.5, 3.6.2
Regression
No.
Operating system
Debian 12
Additional context
Appears to be broken in all versions of MU4 and MU3
I classified this as UX bug rather than engraving because when added such that it covers the desired range, it does render correctly. The bug seems to be in the calculation of the span, not in the rendering.
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.