On Wed, 2015-04-08 at 16:51 +0100, Richard Shann wrote: > On Tue, 2015-04-07 at 21:41 +0200, Andreas Schneider wrote: > > Deleting the extra staffs manually is surely quicker than writing a > > scheme script to do that. > > Of course - it is only if they keep on appearing in many scores that > you > would consider doing it. > > > More interesting would be the reason for the > > extra staffs (they don't appear when importing in MuseScore). > > No, but then MuseScore generated that musicXML so may expect the quirk > it (may have) introduced. The Denemo code makes a first parse through > the score to discover how many voices there are, declares storage for > them and then makes another parse to populate them with data.
Looking at what Musescore generated, it has <staff> </staff> elements from 1 to 4 and <voice></voice> elements numbered in the range 1 to 13, with gaps in the numbering. What it thinks it is doing I can't imagine... the set of examples that the creators of the format publish don't do that sort of thing. Without further evidence I would just presume it is a bug that Musescore may fix at some time. Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
