[Musicxml Export] - Customized instrument change not exported
Reported version
3.4
Type
Performance
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
Currently, instrument changes with default instrument names exports. But the attached example doesn't export any new names. Only transpositions are exported.
| Attachment | Size |
|---|---|
| Ravel examples.mscz | 22.44 KB |
Comments
Confirmed on OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.11614, revision: 1ee2fe3
Haipeng, are you expecting to find MusicXML part-name-display elements where the instruments change ? If you are referring to something else, please be specific.
Regards, Leon.
You're correct, I mean to put instrument changes to this kind of definitions, and this is the most standard way to describe instrument changes in Musicxml.
When I'm helping Sao Mai on their braille translator, I'm facing this again. Here I'm providing an example, in which I edited lots of instrument changes, so that you can see the result xml files in correct expression. This is also what I ask them to implement in braille translation.
Relates to #270643: [EPIC] MusicXML import/export issues
Also see #330480: [MusicXML] support part-name-display, which I would prefer to solve first. Note that I cannot find anything in the spec that states part-name-display must be used instead of part-name in an instrument change, which implies solving #330480 is technically not a precondition.
In reply to Also see #330480: [MusicXML]… by Leon Vinken
You are correct, but part-name-display is used by Michael Good for his Dolet plugins for Finale and Sibelius, and may contain many advanced formatting possibilities. The biggest advantage is to include accidental texts, which Musescore can just do with SMUFL texts. So it doesn't matter if you just use part-name and part-abbreviation for changed instrument.
In reply to You are correct, but part… by hhpmusic
For those accidentals used in instrument names no SMuFL is needed, sharp and flat are available in normal text fonts already
Checked, apparently it does matter if part-name and part-abbreviation are used for a changed instrument: this leads to invalid MusicXML as these element are not allowed as children of the print element.
In reply to Checked, apparently it does… by Leon Vinken
Thanks, then just use the valid pair.
Prototype implementation available in https://github.com/lvinken/MuseScore/tree/306120-instrument-change-3.x
This includes using the accidental-text element for accidentals, which in retrospect is indeed not required, as using the corresponding Unicode works just as well.