Re: [Lilypond-auto] Issue 3307 in lilypond: Rest positions incorrect with non-standard line count

[lilypond]

Updates:
        Labels: -Patch-countdown Patch-review Needs-design

Comment #24 on issue 3307 by address@hidden: Rest positions incorrect with  
non-standard line count
http://code.google.com/p/lilypond/issues/detail?id=3307

Obviously "mix of good and bad" is not what I've been aiming for, and all  
changes _are_ deliberate.  Since I don't have _any_ music typesetting book  
available (well, apart from an old accordion-related text more concerned  
with orchestration than notation), I have to fly by gut feeling.

So here are the "principles" I have been using; please point out where the  
literature indicates either my approach or the results are wrong:

a) I don't distinguish the vertical position of multimeasure (wholebar)  
rests and ordinary rests.  That's a significant change to previously.   
There is one exception: church rests are positioned somewhat differently  
since they need to form a group.

b) only half-note rests or longer are placed in relation to bar lines.   
Most important use cases are drum staves with an even number of lines and  
tablature staves with full tablature.  There has been no satisfactory  
feedback on that decision so far; we might want to publish at least on user  
and developer list an explicit request.  Rationale: for tablature with its  
1.5 staff line distance, the existing rest glyphs don't fall into a proper  
pattern anyway.  We could create new glyphs or use a larger version of the  
existing glyphs (they look aenemic, but scaling them up in size will not  
just make their height match the staff better but also will make them fat,  
in contrast to the rather skinny tablature notes).  But at any rate,  
matching to a non-centric staff position looks more distracting than just  
centring irrespective of the lines.  Now tablature with its weird staff  
distance makes a weak case for staff alignment with existing glyphs.  Drum  
staves with even number of lines could make a stronger case, except that we  
are totally lacking relevant input again.  My own taste prefers centring.

c) whole and half note rests occupy the same staff space unless that makes  
one hang in the air.

d) There are some offsets gathering the vertical positioning of multi-voice  
rests, and then the wanted staff line is found from there.  We can tweak  
the rules and offsets to match the five-line cases spelt out in theory, but  
we still have to make a decision about what to do with other staves: aim  
for fixed offset, or aim for bottom placement?

At any rate, seems like we still need feedback on the visuals of this  
change.  Some things can get likely be sorted out with existing feedback,  
but some are really unclear and it makes no sense to stall indefinitely.

--
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