musescore / musescore/MuseScore
Weird behaviour when realizing a chord symbols in a multimeasure rest
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 (bad rendering)
Steps to reproduce
After #21672/#21975:
When realizing a chord symbol in a multimeasure rest, like this:
We end up with this:
Not really wrong, just pretty strange, without Format > Style > Score > Display note values across measure boundaries being set.
Also strange are the accidentals on the tied to chord.
Disabling multimeasure rests turns it into this:
Originally posted by @Jojo-Schmitz in https://github.com/musescore/MuseScore/issues/21975#issuecomment-2564820740
Screenshots/Screen recordings
see above
MuseScore Version
all, at least since #21672/#21975 (before MuseScore crashed in this), guess that means 4.3
Regression
I don't know (not a Mu3 regression for sure, it is suffering from a pretty similar issue, see https://github.com/Jojo-Schmitz/MuseScore/pull/395 (a backport of #21975)
Operating system
Windows 11
Additional context
No response
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.