lilypond-user
[Top][All Lists]
Advanced

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

Re: Avoiding tie/prall collision


From: Helge Kruse
Subject: Re: Avoiding tie/prall collision
Date: Wed, 11 Apr 2012 08:32:02 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2

Am 10.04.2012 08:37, schrieb Janek Warchoł:
On Tue, Apr 10, 2012 at 6:31 AM, Helge Kruse<address@hidden>  wrote:
What is the benefit of the two voices approach and when should I avoid the
stem up/down?

It's not a matter of benefits - using stemUp/Down instead of
voiceOne/Two/.. simply produces typographically wrong results:
stemUp/Down only changes the direction of stems, while the direction
of ties, slurs, articulations, dots, positioning of rests etc. should
be changed, too.

I can't contradict this statement. But sometimes I don't find a way to place the notes without stemUp/Down like in this example:

\version "2.14.2"

\context PianoStaff <<
  \context Staff=right \relative c'' {
      \key g \major \time 3/4
      s2.
\times 4/6 {r16 b cis d[ cis b]} \times 4/6 {r16 cis d e[ d cis]} d a fis d | % 40
  }
  \context Staff=left \relative c' {
    \clef bass \key g \major \time 3/4
    c4 d e |
    \change Staff=right g4 a \change Staff=left fis | % 40
  }
>>

The left hand plays the two quavers (g and a). The semiquaver rests belong to the right hand's voice. Therefore I want to quavers shown below the rests. But the notes in the sextuplet should keep the stems down to avoid a high skyline.

I played around with voiceOne/Two but found no solution. Probably you have a one?

Threre was a change in the documentation to underline this difference,
but apparently it's not enough.  Maybe you could suggest what we
should do to make this issue clear for all users?

Honestly, I used the 2.13 documentation. Now I downloaded the 2.14 documentation. Searching for stemDown\Up\Neutral I didn't find any hint to favor voiceOne/Two/Three. But I did not read thorough 763 pages. Which section are you referring?

Regards,
Helge



reply via email to

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