[MusicXML Import] Beams are overridden

• Jan 21, 2020 - 19:05
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
fixed
Regression
No
Workaround
No
Project

When importing a MusicXML file, the beams are replaced using MuseScore's automatic beaming.
Is there a way to prevent automatic beaming when importing?

beams.musicxml should display as:
Screenshot from 2020-01-21 13-43-26.png

But instead displays as:
Screenshot from 2020-01-21 13-42-43.png


Comments

Note that the example file you provide does not specify

supports element="beam" type="yes"

so it might be argued that beams might then be set to "auto".

However, currently MuseScore would produce the same result even with that "supports" setting.
Moreover, it seems that beams should not be set to "auto" on import as soon as a single "beam" element is found in a document.

This issue actually combines two separate problems with beam importing:

  1. Notes without beams are not imported correctly (duplicate of #298438, for which I've created PR #7211)

  2. Beam endings are not imported correctly (notes at end of beam are assigned Auto beam mode instead of Mid). A simple repro score is attached - try to export it to MusicXML and then re-import it, and you'll see the last note is imported without a beam (on MuseScore 3.6). I've submitted PR #7213 to fix this.

Attachment Size
test_beam_end.mscx 6.78 KB

To solve this issue you need to merge both my PRs (linked in post above) and then you will get the desired result as posted in the original post. I've tested it.

Status PR created fixed

Fixed in branch 3.x, commit a8f37bad2b

_fix #299976: import MusicXML beam endings

Previously notes at the end of beams were imported with Auto beam mode.
They are now imported with the Mid mode instead (which means 'continue beam
from previous note')._

Fix version
3.6.1