Thanks for the answer, that works for me.
Also, I understand the explanation why it is difficult to automatically
resolve the collisions with multi-measure-rests.
But I hope that it is at least a long time goal of the lilypond developers to
handle that case automatically.
~Michael
On Thursday 05 October 2006 08:23, Mats Bengtsson wrote:
> I would rather recommend to set the staff-position property:
> moveRestUp = \once \override MultiMeasureRest #'staff-position = #6
> moveRestDown = \once \override MultiMeasureRest #'staff-position = #-6
>
> The default in \voiceTwo (i.e. in the second voice of a <<{...} \\
> {...}>> construct)
> is that staff-position is set to -4 for MultiMeasureRest.
>
> Since these rests are typeset centered between the bar lines, it would
> require
> significant effort for LilyPond to figure out which other notes it might
> collide
> with (all the current collision handling between notes and between notes
> and rests, is only done for notes and rests that occur on the same beat).
>
> /Mats
>
> Kieren MacMillan wrote:
> > Hi, Michael:
> >
> > HTH,
> > Kieren.
> >
> > \version "2.8.6"
> >
> > moveRestUp = \once \override MultiMeasureRest #'Y-offset = #4
> > moveRestDown = \once \override MultiMeasureRest #'Y-offset = #-5
> > theMusic = \relative
> > {
> > << {c4 c c c} \\ { \moveRestUp R1 } >> \break
> > << {c4 c c c} \\ { \moveRestDown R1 } >> \break
> > }
> >
> > \score
> > {
> > \theMusic
> > }
> >
> >
> > _______________________________________________
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
--
"Mit Mathematikern ist kein heiteres Verhältnis zu gewinnen."
-Johann Wolfgang von Goethe
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
