lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: avoid merging stems


From: musicus
Subject: Re[2]: avoid merging stems
Date: Sun, 14 Jun 2015 23:43:37 +0000
User-agent: eM_Client/6.0.22344.0

Ok, this sounds indeed very interesting.
I understand your explenation regarding nesting of <<>> in following way:


<<
  {"layerOne"}
  \\
  <<
    {"layerOne"}
    \\
    {"layerTwo"}
  >>
>>

which leads to the problem:

\version "2.19.17"

<<
  {a' a' a' a'}
  \\
  {
    b b
    <<
      {c c}
      \\
      {a, a,}
    >>
  }
>>


I don't think that "a" and "c" should share a stem. Is there any reason to repeat the "layerOne" in nested "<<>>"? Following by default (without needing \new Voice) seems to be much more understandable.


<<
  {"layerOne}
  \\
  <<
    {"layerTwo"}
    \\
    {"layerThree"}
  >>
>>

Regards,
musicus


------ Originalnachricht ------
Von: "David Kastrup" <address@hidden>
An: "musicus" <address@hidden>
Cc: "Thomas Morley" <address@hidden>; "Simon Albrecht" <address@hidden>; "lilypond-user" <address@hidden>; "Trevor Daniels" <address@hidden>
Gesendet: 14.06.2015 23:36:29
Betreff: Re: avoid merging stems

musicus <address@hidden> writes:

 so \voiceXxx should work, or not?
 Why doesn't the stem of "\voiceOne g" go up as intended? Sure, it's a
 quite rare usecase, but i hope you can see my point.
I don't want to merge the \voiceOne and \voiceTwo stems and if you try
 to hide/ omit one of both stems, both disappear!
 That's why I'm asking...
 Anyway, in this case the chord syntax {<g g>4 bes g} does work
 perfectly.

 Thanks for help,
 musicus
 \version "2.19.17"


 {
       <<
             \clef bass \time 3/4
             \relative c' {\voiceOne g2.} \\
             <<
                   \relative c {\voiceTwo g4} \\
                   \relative c {\voiceFour g( bes g)}
             >>
       >>
 }

You are using << ... \\ ... >> at different layers.  At each layer,
Voice contexts are numbered starting from "1".  So your "\voiceOne" and
your "\voiceTwo" occur in the same Voice, and since they are executed at
the same musical point of time, the last override wins.  Apparently
\voiceTwo.

Try working with explicit voices.

{
  \new Staff
      <<
            \clef bass \time 3/4
            \relative c' {\voiceOne g2.}
            <<
                  \new Voice \relative c {\voiceThree g4}
                  \new Voice \relative c {\voiceFour g( bes g)}
            >>
      >>
}

--
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]