[Musicxml export] - trill on rest not exported

• Dec 23, 2019 - 13:28
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project

This is extracted from an orchestral work, and the trill is strangely not exported. I looked into the mscx code, and found nothing which can stop exporting it. Other trill lines can be exported, but this one can't. Why? I just removed the Python script helping me to catch trill lines, and this again makes me afraid of missing trills in braille transcription, and I have to bring the script back.

Haipeng

Attachment Size
trill.mscz 7.93 KB

Comments

Hi Haipeng,

I think most developers would agree with me that we would love to release bug free software, or fix all bugs immediately. Unfortunately in practice we do not succeed in producing software without faults and the bug fix capacity is limited. At least for me, I have a full time paying job and can spend only limited time on MuseScore.

Regards, Leon.

I understand you are busy. It's just a question, in case it's neglected among tons of issues. I only remind some critical ones, not minor ones which doesn't do big harm on braille music transcription. Anyway, I believe one day these issues can all be solved.

Regards,
Haipeng

The explanation is that the trill line ends on a rest, which is not supported by the MusicXML exporter. I assume this was based on the assumption it would not matter, as it seems to make no musical sense. This breaks when hidden rests are used to position lines. As this practice is supported by MuseScore's GUI and the resulting MusicXML files are valid, I think this should be supported by the exporter.

Solving this issue will probably not be extremely hard, but also not entirely trivial, as it requires changing a number of functions and data structures currently supporting chords only into supporting chords and rests.

Example attached.

Attachment Size
trills_and_rests.mscz 4.38 KB
Fix version
3.5.0