Changes to Measure properties are not propagated between score and existing linked parts after save/reload
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project
Score with simple repeats (AKA repeat barlines) and linked parts.
Changing the 'Play count' property of the measure with the end repeat barline is score is not reflected in part and vice versa. Changing a volta's repeatlist though does propagate.
MuseScore 2.1, Windows 7
Fix version
3.6.0
Comments
Strange enough in 2.1, 2.2 and master the corresponding property's link type is set to true, for 2.2 see libmscore/property.cpp, line 202
Even stranger: I can't reproduce it, if I take an existing score without parts, generate the linked parts and then change the repeat count on either score or part.
I can reproduce though, when using an existing score with linked parts and then change the repeat count on either score or part.
?!?
In either case the scores had been created (or at least last saved) with 2.1
I have read through this thread, there is no example score comes with it. I am not sure if it’s the same scenario with this score I am editing, with which by changing “Play count” of the measure where the repeating sign is rooted would bring out strange unexpected playing behavior.
I am trying to get it play repeat three times correctly, it's just not achievable for the third loop via changing limited variable.
In reply to I have read through this… by Xianyue賢越
Your request is unrelated to this issue (no parts in your score)
To receive the desired result, you have to change the repeat list in Volta Properties.
So: right-click on the Volta 2 (measure 12) -> Volta Properties -> Set the number 1 (instead 2) in the Repeat list box.
See: 轻风 - 1Teresa Teng - Copy - Copy.mscz
In the future, it is recommended to use the Support Forum https://musescore.org/en/forum/6 for such questions.
Same with the 'Exclude from measure count' property
Still the case for at least some properties (see also "break multimeasure rests"). Arguably by design but worth reconsidering.
Looking at libmscore/property.cpp lines 199204 reveals that the repeat count and whether a measure is irregular is linked, but the measure number offset is not. Other properties like break multi measure rest and stretch are not linked and for IMHO valid reasons.
Even if reported earlier in this issue, repeat count and exclude from measure count is propagated. At least with scores whehe the parts are created afreash (and I guess that might have been the reason why I wasn't able to reproduce it at one point)
See https://github.com/musescore/MuseScore/pull/5316 for getting measure number offset linked
Fixed in branch master, commit e08f1e53b7
_fix #257581: measure number offset not linked between score and parts
plus some formatting_
Fixed in branch master, commit fee7af777e
_Merge pull request #5316 from Jojo-Schmitz/measure-number-offset
fix #257581: measure number offset not linked between score and parts_
Automatically closed -- issue fixed for 2 weeks with no activity.
There is a report of a case where this does not seem to be working after all, my initial investigation suggests it works at first but the link is somehow not re-established when the score is saved/reloaded. See https://musescore.org/en/node/64636#comment-995451. I went ahead and re-opened that issue rather than this one because it already has the sample score, but I'm fine with someone reopening this instead or opening a new issue.
This is definitely still active, I can reproduce easily from scratch:
1) default empty score
2) fill first few measures with whole notes to remove mmrests from the equation
3) go to format / style /measure numbers and set to display on all measure (interval = 1)
4) generate parts
5) exclude first measure from measure count
Result: as expected, measure is excluded from count in both score and part (you see the first two measures unnumbered, a "2" on the third measure)
Now, save & reload. Uncheck the exclude from measure count in the first measure. It works in the score (only first measure is unnumbered, "2" on second measure) but part still shows the first measure excluded.
Somehow the links are not being re-established correctly. Tested with 3.5 alpha
Indeed, although measures can be linked, this information is not written into the score file since in
Measure::write()Element::writeProperties()is not called at all. This latter method is responsible for writing the link information.PR is in on its way, right now I'm looking into 18 failed tests (which is expected since now the measure links are in the file too!).
https://github.com/musescore/MuseScore/pull/6124
This PR also solve #64636: "add to measure number" is not linked between score and parts after reload.
Fixed in branch 3.x, commit 2c7435b19e
_Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts after save/reload
Saving link information into the MSCX file. Since measure information is written for
every staff, make sure the link information is written for the first staff only._
Fixed in branch 3.x, commit a470fc3037
_Revert "Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts after save/reload"
This reverts commit 2c7435b19e4b774070985acfc8c25d8b356d30d3._
Change got reverted. This issue will then hopefully get fixed again in 3.6, but will not in 3.5.2
New PR, see https://github.com/musescore/MuseScore/pull/6743
This PR relinks all measures of a part to the corresponding measures of the master score.
Fixed in branch 3.x, commit 529fe7f5c3
_Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts
after save/reload
When reading a mscx file containing parts, link all measures of the part to the corresponding measure in the MasterScore._
Fixed in branch 3.x, commit 5431550f87
_Merge pull request #6743 from njvdberg/issue-257581-linking-measures
Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts_
Fixed in branch 3.6alpha, commit 529fe7f5c3
_Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts
after save/reload
When reading a mscx file containing parts, link all measures of the part to the corresponding measure in the MasterScore._
Fixed in branch 3.6alpha, commit 5431550f87
_Merge pull request #6743 from njvdberg/issue-257581-linking-measures
Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts_
Automatically closed -- issue fixed for 2 weeks with no activity.