Wrong measure number when starting with a multimeasure rest
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
I have a file that I start measure numbers at 168. It has six staves plus piano. steps to reproduce
1) File/Parts
2) select any stave part and you will see the measure numbers start at 335.
3)type M an the measure numbers return to start at 168.
| Attachment | Size |
|---|---|
| Test measure number error.mscz | 31.23 KB |
Comments
I noticed the same problem when I created parts. The issue seems to be with multimeasure rests. When they are turned off, the numbering is correct.
I guess we better close this as a duplicate of #283247: Wrong measure number when starting with a multimeasure rest
No, other way round
In reply to No, other way round by Jojo-Schmitz
Thanks for taking the time to look at this.
Came up again in: https://musescore.org/fr/node/284111
It seems to be a problem in LayoutContext::adjustMeasureNo which doesn't account for MMR.
See https://github.com/musescore/MuseScore/pull/4675.
Fixed in branch master, commit ed33c2f011
fix #282810: Wrong measure number when starting with a multimeasure rest
Fixed in branch master, commit 1705ba5e0e
_Merge pull request #4675 from mattmcclinch/282810-mmrest-offset
fix #282810: Wrong measure number when starting with a multimeasure rest_
Fixed in branch 3.0.5, commit f59130bac2
_Merge pull request #4675 from mattmcclinch/282810-mmrest-offset
fix #282810: Wrong measure number when starting with a multimeasure rest_
Automatically closed -- issue fixed for 2 weeks with no activity.