Capella .capx import doesn't properly recognize hidden empty staves at start of score

• Feb 6, 2020 - 14:16
Reported version
3.4
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Tags

Issue came up in https://www.notensatzforum.net/t2129f2-Leerzeile-wird-nach-unten-versch…

Importing Cappela .capx scores that hide empty staves and do so in the first system too are not getting imported correctly, if the hidden staves are above the non-hidden ones, instead it reshuffles the staves.

Not the case with .cap import or with .mxl from Capella, just .capx.

Sample score attached. and an Image how it is supposed to look, taken from Capella 8 Reader:
Capella.png

Attachment Size
Schubert_Kunstlied.capx 18.21 KB

Comments

Cause of the issue: hidden staves are not present in the cape file, which breaks an assumption of the importer. Solution is to use a staff's layout attribute and match it with the layout's description attribute to find the staff position in the system.

Title Capelle .capx import doesn't properly recognize hidden empty staves at start of score Capella .capx import doesn't properly recognize hidden empty staves at start of score

Original reporter confirmed that the issue is fixed with this.
There are other, entirely unrelated and minor issues though, reg. a) the beaming (should mostly be unbeamed in that not shared score) and b) visibilty (where unison in that not shared score, Alto and Tenor are set to invisible in Capella) and jumps get lost too
Guess we'd need to enter new issues for those.
See #300955: Capella .capx import: beaming information not imported, #300956: Capella .capx import: invisible elements not imported as such , #300958: Capella .capx import: jump instructions and -markers not imported

Thanks for confirming the issue is fixed and for submitting new issues. Priority of solving these to be determined. I have no idea how often Capella import is used (would the telemetry provide that data ?). I would expect MusicXML import/export to be used more often than Capella import, so I would rank those as more important, but I may be slightly biased :-).

Fix version
3.5.0