Inconsistency in beams in MusicXML export / import
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
Description:
Re-import of an exported MusicXML score exhibits differences in the 'beaming' of eight notes.
How to trigger:
Load score test03.mscz (see screen shot [test03-mscz.png]) and export in MusicXML format. Loading MusicXML score test03.musicxml results in a different eight notes beaming (see [test03-MusicXML.png]).
| Attachment | Size |
|---|---|
| test03-mscz.png | 8.59 KB |
| test03-MusicXML.png | 8.66 KB |
| test03.mscz | 2.44 KB |
| test03.musicxml | 3.85 KB |
Comments
relates to #270643: [EPIC] MusicXML import/export issues
This behaviour changed between 2.1.0 and 2.3.2. Note that, due to differences in their data models, it is not always possible to save a score to MusicXML and import that score from MusicXML without a difference to the original. For beams this probably would be possible, but am not yet convinced it would be desired.