Re: [Lilypond-auto] Issue 3902 in lilypond: the position of the initial \voiceOne rest is suboptimal

[lilypond]

Comment #20 on issue 3902 by address@hidden: the position of the  
initial \voiceOne rest is suboptimal
http://code.google.com/p/lilypond/issues/detail?id=3902

I tried the patch.
When the rests do not follow the line of music I would personally prefer  
that they stick out a bit for clarity, making it clear they apply to only  
one voice.  LilyPond's pitched rests, d''4\rest, are easy to use when we  
want to adjust from her automated placement.

Different people prefer different automated behavior.  The original request  
was for zero shift in absence of collisions (as if \once\oneVoice ) while I  
prefer the larger shifts so that the automated placement errs on the side  
of clarity.

I had more difficulty with full-measure rests colliding with cue notes, and  
the fix
 \once\override MultiMeasureRest #'staff-position = #-4 R1
is not so obvious for new users.

Looks like a new property is worthwhile.  Maybe "voiced-position", or maybe  
-offset; I first suggested -position because it is conveniently measured in  
staff-positions, where most things called -offset are in staff-spaces (two  
positions).

Then Urs can \override Rest.voiced-position = #0  and I can say \override  
MultiMeasureRest.voiced-position = #4.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings