Looking back at the section on Explicitly instantiating voices, I now
notice that
more or less the same idea is already used, but with different shapes of
the note
heads instead of using different colors. The example also shows the use of
explicit \voiceOne, \voiceTwo and \oneVoice commands.
Mark, what do you say? Is the current example in the manual too complex so
that the main points are not clear enough? Should we replace that example
by Kieren's?
(For the record, there are plenty of answers to similar questions in the
mailing list
archives, that show exactly the same construct. I'm surprised that you
didn't find
them.)
/Mats
Mats Bengtsson wrote:
Excellent idea! I will add something like this to the manual, extended
with
yet another example that shows how to manually specify \voiceOne and
so on.
/Mats
Kieren MacMillan wrote:
Hi Mark,
It looks like there is a solution to the problem
Glad it worked!
perhaps people in the past just didn't understand the questions of
the people asking properly . . .
Perhaps... that's why I kept trying to clarify what question you were
really asking, so that I could answer the question you were really
asking! =)
Graham: may I suggest one thing that might help the docs? In 6.3
(especially .4, Explicitly instantiating voices), maybe if the notes
in each Voice context were independently (i.e., differently)
coloured, the examples (and thus the constructs and internal Lilypond
mechanisms) would be even more clear immediately?
For an example, see the attached snippet.
Best regards,
Kieren.
_______________
\version "2.11.30"
\markup \wordwrap { At first it may be difficult to understand why
the three C notes are not tied in the following example: }
\score
{
\new Staff \relative c''
{
c ~ << { c ~ } \\ { a } >> c }
}
\markup \wordwrap { By colouring the main Voice red, the problem
becomes clear: }
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap
{
Within the \typewriter {"<< \\\ >>"} polyphony section, two
completely new Voice contexts, independent from the main Voice, have
been constructed automatically by Lilypond. There are several ways to
compensate for this instantiation, but the easiest is simply to avoid
the \typewriter { "\\\ " } construct entirely — within the "<< >>"
construct, any notes before an explicit \typewriter { "\\new Voice" }
command will belong to the main Voice context (i.e., the one
“outside” the polyphony):
}
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \new Voice { a } >> c
}
}
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=============================================
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
=============================================
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
