Opening 2.3.2 score reset correctly elements except in some places
⇒
Chord symbols with alternate style assigned should be reset to better default
Severity
S3 - Major
⇒
S4 - Minor
In general, it's not going to be reasonable to expect good results without reset, because the defaults are so different. Collisions of tupelts and fingers is a known limitation of the algorithms covered by another issue. So that aspect is not really worth repeating here.
But the chord symbol issue seems unique and worth making explicit here, so that's what I'd focus on here. Looks like you had set these to use the "text line" style so that is what we are using for the default, and I'm not sure what we are doing is objectively "wrong" given that, but probably we should consider remapping anything but the default chord symbol style to "Chord Symbol B" when importing. Can you re-attaching your score and relevant info here so we can keep the discussion focused in one place?
If you want to open another issue (also with sample score and information included) with a suggestion on how tweak the defaults for voltas and/or chord symbol so voltas don't have to be lifted so high to avoid them, that's also worth tracking separately.
Thanks Marc.
Here attached again the score.
The chord symbols with another style were so to be able to have them in italic (following your suggestion in https://musescore.org/en/node/267501).
Opening in V3, the italic is lost :-( and these chords are not positioned as other chords :-(
Chord symbols with alternate style assigned should be reset to better default
⇒
Chord symbols with alternate style assigned not assigned on import
Severity
S4 - Minor
⇒
S3 - Major
Priority
⇒
P1 - High
Well, I would say one problem here is with the specific method - a bad hack, really - you employed to get this alternate display of chord symbols. Had you created a custom style instead of trying to use the text line style, it would have worked better. But still not right - the new style would have come through fine, but the chord symbol would not have been given that assignment. Looks like the code that imports custom text styles doesn't get it right for chord symbols. So that seems to be the bug.
Attached is a simple example showing it works for staff text but not chord symbols.
Comments
In general, it's not going to be reasonable to expect good results without reset, because the defaults are so different. Collisions of tupelts and fingers is a known limitation of the algorithms covered by another issue. So that aspect is not really worth repeating here.
But the chord symbol issue seems unique and worth making explicit here, so that's what I'd focus on here. Looks like you had set these to use the "text line" style so that is what we are using for the default, and I'm not sure what we are doing is objectively "wrong" given that, but probably we should consider remapping anything but the default chord symbol style to "Chord Symbol B" when importing. Can you re-attaching your score and relevant info here so we can keep the discussion focused in one place?
If you want to open another issue (also with sample score and information included) with a suggestion on how tweak the defaults for voltas and/or chord symbol so voltas don't have to be lifted so high to avoid them, that's also worth tracking separately.
Thanks Marc.
Here attached again the score.
The chord symbols with another style were so to be able to have them in italic (following your suggestion in https://musescore.org/en/node/267501).
Opening in V3, the italic is lost :-( and these chords are not positioned as other chords :-(
Well, I would say one problem here is with the specific method - a bad hack, really - you employed to get this alternate display of chord symbols. Had you created a custom style instead of trying to use the text line style, it would have worked better. But still not right - the new style would have come through fine, but the chord symbol would not have been given that assignment. Looks like the code that imports custom text styles doesn't get it right for chord symbols. So that seems to be the bug.
Attached is a simple example showing it works for staff text but not chord symbols.