The real problem you experienced was that if you start a Staff context
with a << ... >>, then LilyPond will create a new Voice context for
each musical expression within << ... >>, i.e. what you wrote is
equivalent to
\new Staff{
<< \new Voice { c'1 } \new Voice { s2 s2-\> } >> ...
The simple solution is to explicitly instantiate a Voice context
from the beginning of the piece:
\score{
\new Voice {
<< ...
}
}
or
\score{
\new Staff {
\new Voice {
<< ...
}
}
}
/Mats
Alard de Boer wrote:
On 25/11/05, Erik Sandberg <[EMAIL PROTECTED]> wrote:
On Friday 25 November 2005 16.48, Alard de Boer wrote:
Hello list,
When using spacer notes to move the start of a descrescendo,
I found the following:
\version "2.7.18"
\score {
\new Staff {
% s1*0
<< c'1 { s2 s2-\> } >> | c'4-\! r4 r2 |
<< c'1 { s2 s2-\> } >> | c'4-\! r4 r2 |
}
}
The first decrescendo is not visible in the output, and there
are warnings (can't find start of (de)crescendo, unterminated
(de)crescendo). The second descrescendo is fine.
Try adding a \new Voice, i.e. use:
\new Staff \new Voice { ... }
Thank you, that works, and is a lot "cleaner" than the workaround
I used (the s1*0).
Incidentally, I re-read the manual to learn more about contexts,
and found that in 9.1.3 in the bottom example, both staves start
with an upbeat. In the manual for 2.6 the top staff simply contains
two 3/4 measures and the bottom one three 2/4 measures, which
is what I would expect. Bug?
URL:
http://lilypond.org/doc/v2.7/Documentation/user/out-www/lilypond/Modifying-context-plug_002dins.html
--
Groeten,
Alard.
Ceterum censeo MS Word esse delendam.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.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
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
