[Musicxml Export] - Better way to show and hide staff

[hhpmusic]

Issue type

Other type of issue

Bug description

No response

Steps to reproduce

When an orchestral score is set to hide empty staves, or when a piano score has temporary displayed Ossia staves, the exported Musicxml shows a confusing description of such staves. It only exports staff-distance, but in standard musicxml expression, it must be staff-details number=n print-object="yes" or"no". This is placed right at the show or hide point of the staff, either at the beginning of a system or the point a cutaway staff is show or hidden. The current way confuses not only the code reader like me, but also confuses braille music translation software.

Screenshots/Screen recordings

No response

MuseScore Version

4.0.24.0.2

Regression

No.

Operating system

All

Additional context

No response

[lvinken]

Simple example illustrating the issue including incorrect (current) and correct (to be) output:
issue_17398_example.zip

[Jojo-Schmitz]

Simple example illustrating the issue including incorrect (current) and correct (to be) output: issue_17398_example.zip

I'm affraid I don't see how the correct.musicxml is (fully) correct, on imporrt it looses a note in the voice staff, but indeed keeps the 'hide empty staves setting', the incorrect.musicxml just looses the 'hide empty staves' setting.

Loosing a note (on import) at the cost of keeping that 'hide empty staves' setting can't be the desired outcome, can it?

Mu3 keeps all notes, but looses the 'hide empty staves' setting, so is having the same problem this issue describes, but Mu4 seems to have an additional and much worse problem, in loosing notes. I guess the latter is worth a separate issue (and regression vs Mu3), isn't it? Or is that just a flaw in your sample files? Looking at the diff of the 2 musicxml files seem to indicate that it is not, both contain the same notes, just differ in the <staff-details print-object="..."/>setting

[hhpmusic]

The example may have something missing. It's not mine example, but the thing I'm hoping is correct, thus when the staff is hidden, either throughout the whole system(s) or as cut-away, the staff-details should be shown instead of showing only staff-distance. The latter is very confusing, and I suggest not to use it when the staves are hidden. Missing notes is not a result of hiding staves.

I'm affraid I don't see how the correct.musicxml is (fully) correct, on imporrt it looses a note in the voice staff, but indeed keeps the 'hide empty staves setting', the incorrect.musicxml just looses the 'hide empty staves' setting.

Loosing a note at the cost of keeping that 'hide empty staves' setting can't be the desired outcome, can it?

Mu3 keeps all notes, but looses the 'hide empty staves' setting, so is having the same problem this issue describes, but Mu4 seems to have an additional and much worse problem, in loosing notes. I guess the latter is worth a separate issue (and regression vs Mu3), isn't it? Or is that just a flaw in your sample files?

[Jojo-Schmitz]

Missing notes is not a result of hiding staves.

It of course shouldn't be, but is in that example though.
So on top of the export issue at hand here, there's also an import issue, that would get very apparent once the export issue got resolved, but exists already, just not with MusicXML exports from MuseScore

[hhpmusic]

Haha, he might mistakenly removed the note when manually editing the xml file.

[Jojo-Schmitz]

Apparently not, I checked the diff between the 2 musicxml files
Also Mu3 shows it, only Mu4 doesn't.

Isn't this related to #16135? Seems that is the broken import I'm talking about?

[hhpmusic]

So Ms actually doesn't correctly handle shoing/hiding staves in Musicxml at all. Staff-distance applies to the whole staff in a system, so using it for hiding staves is a wrong thought. Using staff-details number="x" print-object="yes"/"no" will handle staff appearance on-the-fly correctly, like a switch.

[its-not-nice]

Is this issue addressed by #17035?