bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [musicxml2ly] unwanted staves and voices [was: missing <voice>-eleme


From: Marek Klein
Subject: Re: [musicxml2ly] unwanted staves and voices [was: missing <voice>-element in chorded note leads to unwanted additional staff]
Date: Wed, 10 Oct 2012 22:40:25 +0200

Hello,
2012/10/3 pls <address@hidden>

>
> now the summaries and descriptions of the issues got mixed up. I suggest
> the following:
>
> Issue 2879: [musicxml2ly] spurious staff
> 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.
>
>
> Issue 2867: [musicxml2ly] unwanted voices
>
> if a <note> element contains a <chord/> element but no <voice> element
> musicxml2ly puts the chorded note without a <voice>-element in an own voice
> (PartPOneVoiceNone) instead of placing the notes in a chord construct (< a'
> c''>1) in the same voice.
>
> In this case musicxml2ly should be taught to be tolerant and automatically
> assign notes containing <chord/>-elements to the voice of the first note of
> the chord. (In MusicXML the first note of a chord does not contain a
> <chord/>-element.)
> Test file:
> https://www.dropbox.com/s/8bep4ly69xfwfmt/unwanted_voices.xml
>

Here the issues:
http://code.google.com/p/lilypond/issues/detail?id=2886
http://code.google.com/p/lilypond/issues/detail?id=2887

Marek
bug squad member


reply via email to

[Prev in Thread] Current Thread [Next in Thread]