Hello,
I would like to report three small bugs I found:
- no. 1: when two parts contain manual beams and slurs at the same point
and one uses \partcombine, some warnings are outputs in the console:
"unterminated beam" and "unterminated slur". It does output the music
correctly though. I believe this wasn't present with 2.19.15, but I am
not completely sure about it.
\version "2.19.28"
{
\partcombine
{r4 c'8[( d' e' f' g' a'])}
{r4 c'8[( b c' d' e' f'])}
}
- no. 2: it's not possible to tie notes which have different types of
\partcombine. In the example below, the first staff has a normal tie,
while the bottom doesn't have one:
\version "2.19.28"
{
\partcombine
{r2 c' e' g'}
{r2 g2~ g1}
}
{
\partcombine
{r2 \partcombineChords c' \partcombineApart e' g'}
{r2 g2~ g1}
}
- no. 3: when using \crosStaff, one has to manually set \autoBeamOff
when crossing, as well as hiding any tuplet numbers and brackets.
Couldn't this be done automatically? If one wants to use \crossStaff for
a certain passage, then very likely he doesn't want beams and tuplets
displaying there. The reference mentions that one should use
\autoBeamOff but there are no mentions about tuplets.
\version "2.19.28"
\score{
\new PianoStaff <<
\new Staff {c'8 d' \tuplet 3/2 {e' f' g'}}
\new Staff {\clef bass \crossStaff{\stemUp c8 d \tuplet 3/2 {e f g}}}
>>
\layout{
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}
}
Please let me know if I can be of any help with these.
Best,
Gilberto
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
