Importing MusicXML causes numerous 'courtesy clefs', etc. for some reason

• Apr 17, 2022 - 18:35
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
MuseScore
  1. import attached MusicXML file
  2. Format -> Page Settings -> Scaling -> Staff space; change spacing to balance staves on the two pages

Numerous 'courtesy' clefs, key sigs, etc. appear (sometimes doubling the bar lines as well).

Able to workaround by selecting one of the clefs, right-click, select, select all similar, [DEL] but this corrects the clefs.

Attachment Size
920 Special.xml 171.46 KB

Comments

• Apr 18, 2022 - 05:15

A quick look at the MusicXML shows there are a whole bunch of what I think are unnecessary "barline" tags - a left one at the start of each measure, and a right one at the end. My understanding is that none of these are needed except where non-standard barlines are desired. It's possible that somehow this is what is triggering MuseScore to get confused about which measures are actually meant to have system headers.

Reply

• Apr 27, 2022 - 09:46
Status PR created ⇒ fixed

Fixed in branch master, commit 209ca94078

_Fix #331336: Importing MusicXML causes numerous 'courtesy clefs'

Ignore spurious regular barlines (left and right) on MusicXML import,
to prevent confusing the layout algorithms with respect to system start._

Reply

Fix version
4.0.0