Closed craigsapp closed 1 year ago
Hmmm.... looks like this might be a music21 MusicXML export bug. There might be something I can do to work around it in converter21, or maybe I'll just need to propose a music21 pull request.
Yep. Under certain circumstances, music21 can drop a clef-octave-change during export to MusicXML. music21 issue #1333, to be fixed by music21 PR # 1334 which I am just finishing up. Should easily make it into music21 v8.
Thanks! Closing this issue, since it's being tracked by music21 PR # 1334.
It would be useful to implement the vocal tenor clef export from Humdrum to MusicXML:
Example: the first column contains
*clefGv2
which is a vocal tenor clef. The note 4c will be displayed an octave higher than the sounding pitch. A regular treble clef is given in the second column for comparision:https://verovio.humdrum.org?t=KiprZXJuCSoqa2VybgoqY2xlZkd2MgkqY2xlZkcyCj0JPQo0Ywk0Ywo0ZAk0ZAo0ZQk0ZQo0Zgk0Zgo9PQk9PQoqLQkqLQo=
Expected rendering (as in VHV):
Translated MusicXML Rendered n MuseScore:
Current MusicXML export:
Click to view MusicXML data
```xmlThe
<clef-octave-change>
element needs to be added to the vocal tenor clef: https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/clef-octave-change/Expected MusicXML conversion with that element added:
Expected MusicXML export
```xmlThis addition to the clef description will result in the expected rendering in Musescore: