[Musicxml Export] - Export unsupported symbols as "symbol"

• Dec 17, 2019 - 07:07
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

This is much like a feature request. When going through the palettes, I found lots of symbols and lines and articulations are not able to be exported into Musicxml. Some are not implemented, while some have no Musicxml equivalents. Fortunately, all of them are SMUFL glyphs, having the standard SMUFL names. So, to ease development, can we include these as a "symbol" element under "direction"? For example, when we input a l.v. symbol as either a line or an articulation, or a wide vibrato as an articulation, the former two are not implemented, while the latter are not available. If we just use the symbol or other-direction to attach them with the note, braille music transcription software can still be implemented to recognize and convert them correctly into braille, and the Musicxml file is much more complete. Is there a way to create a sheet or table for the mapping so that I can make the list myself, then submit to one of you to apply (I can try the symbols one by one and put them into the list, but as a non-programmer, I can't go into the complicated real programming code)? Thank you in advance!

Haipeng


Comments

I just went through the palette and the symbols list, and found the only place we should implement the "symbol" element is the symbol section where all SMUFL symbols are listed and categorized. This section is not available in the standard palette, so the first and the easiest thing is simply copying the symbol into Musicxml with the unchanged Bravura name. Some of these symbols can be implemented as standard articulations or technical elements, but this needs deeper implementation, and we can do the easiest way first, and then go step by step.

Haipeng