Status: Accepted
Owner: ----
Labels: Type-Enhancement
New issue 2887 by [email protected]: [musicxml2ly] spurious staff
http://code.google.com/p/lilypond/issues/detail?id=2887
Reported by pls:
http://lists.gnu.org/archive/html/bug-lilypond/2012-10/msg00036.html
if an .xml file contains only <staff> elements with value "1" (i.e.
<staff>1</staff>) AND no <voice> element in a chorded note musicxml2ly
erroneously thinks that there are several staves. (I haven't tested what
happens when there are several <staff> elements with different values in an
.xml fle.
Test file:
https://www.dropbox.com/s/l9mt7iqd38lqqng/unwanted_staves.xml
The result is:
\new Staff <<
\context Staff ="1" <<
\context Voice = "PartPOneVoiceOne" { \voiceOne
\PartPOneVoiceOne }
\context Voice = "PartPOneVoiceNone" { \voiceTwo
\PartPOneVoiceNone }
This leads to a second unwanted empty staff.
Without any <staff> element in the .xml file the result is:
\new Staff <<
\context Staff <<
\context Voice = "PartPOneVoiceOne" { \voiceOne
\PartPOneVoiceOne }
\context Voice = "PartPOneVoiceNone" { \voiceTwo
\PartPOneVoiceNone }
and there is NO unwanted additional staff!
In this case musicxml2ly should be taught to ignore the <staff>-elements if
there is only one staff.
