Musicxml export does not included altered ontime values
Related Bug: #288687: Musicxml export does not include notehead specification when using custom notehead definitions
Similar to the notehead issue, where notehead shapes are not specified, exporting to musicxml also loses any "ontime" changes to notes. I believe the musicxml element missing is the "attack" attribute:
"The attack and release attributes are used to alter the starting and stopping time of the note from when it would otherwise occur based on the flow of durations - information that is specific to a performance. They are expressed in terms of divisions, either positive or negative. A note that starts a tie should not have a release attribute, and a note that stops a tie should not have an attack attribute. (https://usermanuals.musicxml.com/MusicXML/Content/AT-MusicXML-attack.htm)
To reproduce the bug, export score with altered ontimes to musicxml and reimport. It appears that the Musicxml support in Musescore 3 was never fully completed. Unlike the notehead issue, this issue is not a regression as Musescore 2 also did not support ontime changes when exporting to Musicxml.
My system: OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6715, revision: 526f80e
Comments
For the record, the MusicXML spec is huge, pretty much no one implements it "fully". We strive to get the semantics as right as possible. Things like layout, formatting, and playback customization are extremely secondary in importance. Not to say it won't be looked at, but it's important to have realistic expectations.
In reply to For the record, the MusicXML… by Marc Sabatella
Hopefully, supporting notehead shapes in musicxml, as in Musescore 2, is seen as an essential feature as non-standard noteheads are common in percussion notation. I agree that supporting altered ontime values is a lower priority. I haven't compared Musescore 2 and 3 in terms of musicxml support for altered note velocities and tunings. Hopefully, all these attributes are present in exported midi files.
While I appreciate that the focus of Musecore is visual notation, it's playback cabailities are important for education as it allows students to follow scores with more realism--for example, learning the samba swing feel which is more of a septuplet feel than a shuffle. Being able to export altered ontimes, velocities, tunings and notehead shapes to musicxml, allows the universal distribution of highly accurate scores created in Musescore into other platforms.
Shapes are indeed important semantic info and need to be supported. And from what I can tell, they are, if part of the drumset definition - I just did a simple test and got what I expected on both export and then on import. I'm responding in your other issue thread about that.
Playback info is more relevant for MIDI and should all be present, feel free to file issues if you see things missing.
relates to #270643: [EPIC] MusicXML import/export issues