[MusicXML export] vertical offset of rest not exported correctly
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
When exporting a MS file containing rests of which the vertical position was manually modified, the elements display-step and display-octave are exported incorrectly as MusicXML (a fifth too low when above middle staff line, and a fifth too low when below, limited to either the highest or the lowest staff line).
Please see little demo file attached.
It would be great to have this corrected.
| Attachment | Size |
|---|---|
| de.mscz | 3.29 KB |
| de.musicxml | 6.64 KB |
Comments
relates to #270643: [EPIC] MusicXML import/export issues
Can't reproduce, the musicxml imports into 3.3.4 and loola identicat to the mscz (except for a slighly diffentl measure lentgh and hence horizontally different positions of those rests)
In reply to Can't reproduce, the… by Jojo-Schmitz
Thank you for your quick reply. My issue was on exporting musixXML from a MS file (not importing into MS) from 3.3.4. The example files should have eighth note rests on different pitches (vertical offset), but in the musixXML the vertical offset, as coded in display-step and display-octave is not correct. It should be for upper staff: oct=6, c; oct=5, a; oct=5, f, etc. and in lower staff: oct=5, e; oct=5, c; oct=4, a; ect.. The musicXML file has: oct=5, f; oct=5, d; etc.