This is not a bug but a side-effect of a general principle in Lilypond,
described at
http://lilypond.org/stable/Documentation/user/out-www/lilypond/Default-contexts.html
The solution in your case is to explicitly instantiate a Thread context
that will contain the first chord:
alto = \notes \relative c' {
\context Thread < d1 f, > ~ | < d2 f, > r |
}
or
alto = \context Thread \notes \relative c' {
< d1 f, > ~ | < d2 f, > r |
}
/Mats
Dr A V Le Blanc wrote:
The following sample has failed to work as I expect since
Lilypond 1.4.8, at least, and still causes a problem with 1.6.6.
I apologise for not having sent it in earlier.
-- Owen
[EMAIL PROTECTED]
The source file, tmp.ly:
alto = \notes \relative c' {
< d1 f, > ~ | < d2 f, > r |
}
\score {
\notes \context Staff = treble <
\key d \minor
\time 2/2
\clef violin
\alto
>
\paper {
}
\midi {
\tempo 2=40
}
}
The log file:
Running LilyPond...
GNU LilyPond 1.6.6
Now processing: `tmp.ly'
Parsing...
Interpreting music...[3]
Preprocessing elements...
Calculating column positions... warning: Too many clashing notecolumns. Ignoring them.
paper output to `tmp.tex'...
Interpreting music...
/tmp/tmp.ly:0:13: warning: No ties were created!:
< d1 f, > ~
| < d2 f, > r |
MIDI output to `tmp.midi'...
Track ...
Analyzing tmp.tex...
Running LaTeX...
DVI output to `tmp.dvi'...
MIDI output to `tmp.midi'...
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
