Chord symbol collisions not handled well

• Nov 26, 2018 - 23:25
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore

While I realize autoplacement can't be expected to produce perfect results, this particular case is common enough I'd like to see if we can improve it.

1) empty score
2) add chord symbol to a measure
3) add volta to same measure

Result: chord symbol is moved above volta. I believe in general the volta should be move above the chord symbol, although I'm willing to be convinced otherwise. More significantly, though, if I set the default vertical position of voltas to be high enough that there is no collision (eg, -6sp), then the chord symbol kind of randomly flips between above and below the volta as the score is edited.

Disabling automatic placement of voltas seems to be a possible workaround.

Comments

• Nov 29, 2018 - 16:21
Title Chord symbol / volta collision not handled well ⇒ Chord symbol collisions not handled well

It's not just voltas; chord symbol autoplacement is not working well in general. For example, default empty score, add staff text to first measure rest, then add chord symbol. While you are typing, the chord symbol appears above the staff text, which is fine. As soon as you complete entry, though, the chord symbol moves down and overlaps the staff text. Now enter a note into measure 2 and it moves back up.

Regarding best practice with voltas specifically, see [#27869] and #179221: automatically avoid collision between volta number with Chord Symbols.

Regarding autoplacement of chord smbols in general, see also #277759: Chord symbols sometimes add (much) too much space to measure.

FWIW, when I've looked over my own scores imported from MuseScore 2, it's issues with chord symbol placement that are the most problematic.

Reply