[Musicxml Export] - Incorrect hairpin ending placement
S3 - Major
Since I'm not able to create a short example due to the accessibility issue 336991, I have to include this example as a whole. At bar 5, the end of hairpin in voice 2, when exporting into Musicxml, should be placed at the end of voice 2. But the current export puts it at the end of voice 1 before the backup. It's important to place every direction object at its correct voice order, otherwise our braille music translation software will be heavily confused.
So related to #336991: [Accessibility] - Unable to create hairpin in voice 2 (and with that to #58031: Dynamics/hairpin range for Voice)
And to #270643: [EPIC] MusicXML import/export issues (and probably to #281511: [EPIC] Braille friendly musicxml export too)
Attached prelude 1 measure 5 only, to simplify discussion of the issue. Also attached is an example that shows apparently legal MusicXML generated from a normal MuseScore file where hairpin start and stop are in different voices and in different order.
Could you provide a more precise definition of what does and does not confuse the braille software ?