Setting page number

[lemzwerg]

The page-number attribute of the <print> element has the following description.

Sets the number of a new page. It is ignored if new-page is not "yes".

Testing with Finale, however, this attribute is completely ignored – the program only reacts to <credit-type>page number</credit-type>.

So what is the page-number attribute of <print> good for? Is it only informative?

[infojunkie]

I see page-number mentioned in the MuseScore source code, so at least this software processes this attribute.

In general, I expect every element / attribute or MusicXML to be actionable by applications, not just informative. Otherwise, interpreting the spec would become even more ambiguous that it can be today.

[lemzwerg]

While I agree with your assessment in general, it doesn't really help in particular if, say, the vast majority of programs ignore it, using another MusicXML element instead for setting the page number.

I can imagine that MusicXML adds recommendations in favor of one particular solution if a certain action can be performed in multiple ways, based on some reality checks of what current programs do – this would greatly enhance interchange and simplify life for everyone.

[lemzwerg]

And congrats for being the new MusicXML maintainer 🙂

[infojunkie]

I can imagine that MusicXML adds recommendations in favor of one particular solution if a certain action can be performed in multiple ways, based on some reality checks of what current programs do

Testing with Finale, however, this attribute is completely ignored

I wholeheartedly agree on the principles of enhancing interchangeability and simplification. In fact, I am working on a vision / goals / values type document for MusicXML, and those principles figure prominently there. I will publicize this document in the March public meeting.

That said, looking at the current state of MusicXML support in existing software, completeness is very uneven. So, while taking current implementations as a yardstick of the adoption of MusicXML features is definitely a factor, I think we will want to substantiate individual cases with more evidence of adoption / non-adoption before drawing conclusions. Not to mention that Finale has now ceased to evolve and will remain frozen in time.

As per some previous discussions, I've been working on a support matrix for MusicXML features. I hope to include these kinds of support tools in upcoming revisions of the web site, which should give us better visibility into the real state of adoption of MusicXML elements.