Odd handling of beams in certain MusicXML files
This problem arises when a MusicXML file is exported by Encore from a file having two or more voices active in a measure in which there are beams.
When the file is imported into MuseScore, at first the beams are not present. But applying Format>Reset Beam puts them in place.
A similar oddity does not take place with a MusicXML score from essentially the same score generated by Overture or MuseScore itself.
Testing suggest that the difference in behavior comes about because of a difference as to the sequence in which the notes of the two voices in a measure are encoded. In Encore, the encoding ziz-zags between the notes in the two voices, short <backup> elements being used frequently. In Overture and MuseScore, all the notes in the measure in one voice are encoded, following which there is a big <backup> element, and then all the notes in the measure in the other voice are encoded. I'm sure both schemes are "legitimate".
The attached MusicXML file, generated in Encore, should exhibit this oddity when imported into MuseScore.
This odd behavior is certainly not debilitating, as it is so easily corrected. But it is disconcerting.
|Beams and voices 1004M.xml||9.63 KB|