If joining scores via album, instruments/staves get lost.
If joining scores via album, instruments/staves get lost.
if the 1st score contains just one instrument/staff, but a subsequent one contains more, those additional instruments/staves are not in the joined score
data loss -> critical
self-built c13a719, Windows 7 (Enterprise, 64bit)
Comments
I believe this is a feature request. The album feature was never meant to join scores with different numbers of instruments since MuseScore doesn't support the creation of such a score.
Still it shouldn't crash but warn the user that the number of staves is different and that it will not work.
it doesn't crash, it just loses those staves, which is bad enough
It should add them and, if not done already, switch on 'hide empty staves' I think?
For me an album is a collections of related items, for e.g. fotos it could be b/w and color, landscape and portrait, loosing color and portrait, just because the 1st picture is b/w and landscape, is not good
But indeed at the very least it should emit a warning.
There's no data "loss", just data not copied into the album, because there is no place to put it.
This is basically supplanted by #40251: joining scores via album requires all scores to have the same number of parts and staves, right?
#40251: joining scores via album requires all scores to have the same number of parts and staves is a feature request, this here is a bug and it is data loss in the sense that you may not notice it. The feature request may inclove needed 2 passes, one to collect all staves needed, than a 2nd to copy all tha data.
This here may get away with just a warning message '"subsequent score has more staves than first, these 'excess' staves will get ignored on the merge" or some such
Makes sense.
Relates to #292005: [EPIC] ALBUMS issues.