lilypond-user
[Top][All Lists]
Advanced

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

Re: note-collision in Schumann


From: philippe hezaine
Subject: Re: note-collision in Schumann
Date: Mon, 23 Jan 2006 21:23:08 +0100
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)

It's a reply from himself.
I want to cancel my first e-mail titled: note-collision in Schumann
My ly.file  and requests are confused, because i'm looking for in any way.
I'm trying to be clearer, step by step. I quite trust in lilypond.
I'm going to begin again. It's a thorny problem for me. Here is an extract of two measures in polyphonic model ( that's how I call: \voiceOne ... etc)
     upper = \relative c'' {
      \clef treble
      \key es \major
      \time 6/8

   \voiceOne
   << {s4. aes4 d,8
   es4.~ es8 r8 r8
   }
   \context Voice = "1" { \voiceTwo
   s4. s4 \once \override Stem #'transparent = ##t
   \once \override NoteHead #'extra-offset = #'(-1 . 0)
   bes8~
   \stemUp
   \once \override Stem #'extra-offset = #'(-1 . 0)
   \once \override NoteHead #'extra-offset = #'(-1 . 0)bes4. s4.
\oneVoice
   }
   >>


    }

    lower = \relative c {
      \clef bass
      \key es \major
      \time 6/8

   s4.
   \voiceOne
   << { \stemDown es,8 bes'16 f' \change Staff=upper aes8~
   aes4 \set followVoice = ##t \override Stem #'transparent = ##t g8 s4.
   }
   \context Voice = "1" { \voiceTwo
   s4. es,8 bes'16 es \change Staff=upper g8 bes8 g16
\change Staff=lower \stemUp es bes8 \oneVoice
   }
   >>
   }
_________________________________________________
I can't remove none command, otherwise it's ugly.
I prefer to keep bes8 in alto like a independant voice because,in coda which is a variation of this problem, soprano is a es2. and alto: bes4. des4. in the last measure. I arrange the end already. I have my pdf.file right in front of one. For a musician, it's a surprising graphic. Is there a tool for push far away (not too) the dots (only the dots) on the right (es4. in soprano and bes4. in alto)?
Is there anyone know more elegant way for process this case?
I think there's much to say on this example, or perhaps i am a scatterbrain.
Pardon me for my faulty English.
Regards





reply via email to

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