[Musicxml Export] - Defined measure number not exported
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
The attached score has measures counted from 101 on, but Musicxml still counts from measure 1. This is not convenient for import and braille transcription when meeting score of either an excerpt with numbered measures or part of a long score divided into several files (e.g., a long ballet with continuous measure numbering).
Haipeng
| Attachment | Size |
|---|---|
| MEASURE COUNT.mscz | 10.86 KB |
Fix version
4.0.0
Comments
Relates to #270643: [EPIC] MusicXML import/export issues
PR: https://github.com/musescore/MuseScore/pull/7617
For 3.x see https://github.com/musescore/MuseScore/pull/7870
Fixed in branch master, commit f90880acf9
_Fix #298147 MusicXML: Handle measure number offsets
Previously it was assumed that measure numbers always started at 1 and
increased by 1 for each regular measure. Now the actual measure numbers
given in the MusicXML are used within MuseScore during import to
calculate measure number offsets. During export, these offsets are
converted back into absolute numbers for use in the MusicXML._
Automatically closed -- issue fixed for 2 weeks with no activity.