In my mind, it's not really a bug. Because of the way the automatic instantiation of
contexts works, your code is equivalent to

\new Staff \relative c''
{
 <<
   \new Voice { c16 e a g f e d c }
   \new Voice { s16( s) s-. s-. s( s) s-. s-. }
 >>
}

which means that the placement of the articulations will not in any way be coordinated
with the actual notes.

We could of course discuss if the current algorithm for automatic instantiation of the contexts is appropriate, but otherwise the only possible bug here is a lack of documentation.

As has already been pointed out, the proper solution is to explicitly make sure that both lines
of "music" go into the same Voice context:
\new Staff \relative c''
{
 \new Voice <<
    { c16 e a g f e d c }
    { s16( s) s-. s-. s( s) s-. s-. }
 >>
}

   /Mats


Jay Anderson wrote:
\version "2.11.49"

\new Staff \relative c''
{
  %\key c \major %Add a key to correct programming errors.
  <<
    { c16 e a g f e d c }
    { s16( s) s-. s-. s( s) s-. s-. }
  >>
}

I didn't find this one in the bug tracker. I'm swapping out the rhythm
on the same passage and this error is created for each staccato:

test.ly:8:15: warning: programming error: script direction not yet known
    { s16( s) s
               -. s-. s( s) s-. s-. }

No slurs are created it seems and the dots are placed strangely.
Adding a key signature fixes the errors.

-----Jay


_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

--
=============================================
        Mats Bengtsson
        Signal Processing
        School of Electrical Engineering
        Royal Institute of Technology (KTH)
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: [EMAIL PROTECTED]
        WWW: http://www.s3.kth.se/~mabe
=============================================



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to