Parts do not match score - key and accidental errors

• May 11, 2020 - 18:00
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project

I have created a score for a trombone quartet (3 tenor trombones, 1 bass trombone) and found that the generated parts do not match the score in several aspects. A cut down version of the score demonstrating the issue is attached to this ticket - see BugReport.mscz.

The mismatches I've noticed are:
1) Trombone 2 and Trombone 3 parts have incorrect key signature. The key signature in the written (non concert pitch key) should be 1 sharp to match what's shown in the score, but it's shown as 1 flat, which is concert pitch. Accidentals seem to be applied by MuseScore in the parts to get the right notes, but it looks really weird and is fundamentally wrong.
2) In the Trombone 2 line the tied note across bars 4-5 changes accidental in bar 5 in the part. The score does not have such a change.
3) The cautionary accidental added in bar 9 in the Trombone 2 line is not provided in the part though it is in the score.

The Trombone 1 part was showing similar issues before I prepared this ticket, but regenerating that one part (from File->Parts) fixed the issue there.

Regenerating the Trombone 2 and 3 parts also resolved the issues with them. See confirmation in BugReport_regenParts.mcsv attached.

Attachment Size
BugReport.mscz 13.02 KB
BugReport_regenParts.mscz 13.09 KB

Comments

Status active needs info

I can confirm the problem in this score. There are two known bugs that can cause things like this to happens. One is if you used Tools / Transpose after generating the parts, the other is if you actually changed the transposition for the instrument after generating parts. In either case, regenerating the parts is indeed the workaround.

The former bug should be fixed for 3.5, but the fix won't correct scores that were broken by a transposition in a previous version, so the workaround will still be needed to correct them.

Does either of these scenarios seem likely to you?

See:

#286058: Changing Key Signature in Main Score (Via Transposition) Does Not Result in Changed Key Signature in Part
#62416: Changes to staff transposition (and other properties) not reflected in linked parts

In reply to by Marc Sabatella

Thanks for the rapid response.

The key signatures issue (my point 1) is almost certainly bug #286058. I recall that the score this issue was first observed in started in the key of concert Eb (i.e. 3 flats in concert pitch, so 1 flat in the tenor trombone parts), and transposition (Tools->Transpose) to concert F was a later thing. I definitely haven't changed the nature of the trombone instrument transposition etc.

I don't think either of bugs #286085 or #62416 explain my points 2 or 3 though, since even with wrong key signature, the actual notes that come through on the parts should always match the score.

Thanks

I suspect the same bug is at play there. The code that hooks up ties is kind of complex and could easily get confused if there are inherent problems with the key signatures it anything else. In order to say for sure, I'd need precise steps to reproduce the problem in a score that doesn't already have it, then I could try to do the same in 3.5. But if I take your regen score, transpose it downs to Eb concert, then back to F, I don't see any problems with the parts.

I see. Makes sense Marc. Sounds like this ticket is almost certainly a duplicate of #286085 then.

Please close my ticket, mark as duplicate, or whatever is the normal procedure for duplicate tickets in MuseScore development.

Thanks again for the prompt replies.

There is certainly some chance that the tie issue will turn out to be something else and not fixed by this, but we'd definitely need steps to reproduce that if it ever happens again. For now, though, I do think we're good.