lilypond-user
[Top][All Lists]
Advanced

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

Re: Bad rest placements?


From: Thomas Morley
Subject: Re: Bad rest placements?
Date: Thu, 19 Jun 2014 19:43:13 +0200

2014-06-19 19:25 GMT+02:00  <address@hidden>:
>
>     Howdy?
>
>            So I have been working on an engraving and had 80% of it
>  finished  when I decided I needed another voice. I added it and it solved
> my voicing
>  issue, but it completely ruined ALL of my previous rests which were fine
>  before. I don't see why these rests should be so badly out of position???
>
>    http://www.gooeytar.com/projects/test/test4.pdf
>    http://www.gooeytar.com/projects/test/test4.ly
>
>        The rests in voicethree are way out! Sure I could use  "\rest"  for
>  each one but shouldnt  this just work??
>
>    Here is a minimal reduction of the problem.  Ideas?  thanx - steve
>
>  \version "2.18.0"
>
>   global = {
>      \time 3/4
>      \key e \major
>      \clef "G_8"
>   }
>
>   voiceone = \relative c' {
>      \repeat volta 1 {
>          \partial 4 { e'16_\p b gis' e } |
>          b'4 r gis,16 e b' gis |
>          e'4 r gis,,16 e b' gis |
>          < a fis' >4 < gis e' >
>      }
>   }
>
>   voicetwo = \relative c' {
>      s4
>      \repeat unfold 2 { s2. } s2
>   }
>
>   voicethree = \relative c {
>      \stemDown
>      \repeat volta 1 {
>      \partial 4 s4 |
>      r4 < e gis b > r | r4 < e, e' gis > r |
>      e2
>      }
>   }
>
>   guitar = << \voiceone \\ \voicetwo \\ \voicethree >>
>
>   \score {
>      \new Staff { << \global \guitar >> }
>      \layout { }
>   }
>
>
>
>
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Please reread
http://lilypond.org/doc/v2.18/Documentation/notation-big-page#single_002dstaff-polyphony

\stemUp is not the best command here, use \voiceTwo
or
guitar = << \voiceone \\ \voicethree \\ \voicetwo  >>


(Not very serious:) the << {…} \\ {…} >> construct causes a lot of
problems, sometimes I feel we should delete any hint to it in the
docs. ;)

Cheers,
  harm



reply via email to

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