Comment #29 on issue 3902 by [email protected]: the position of
the initial \voiceOne rest is suboptimal
http://code.google.com/p/lilypond/issues/detail?id=3902
TBH Keith, I'm not convinced it's worth it. I'd try to do it myself, but I
think the comments on the patch have led me to the conclusion that, despite
the recommendations of Gould, this issue is invalid. Given that we already
have pitched rests, an option for "close voiced rests" or "spaced voice
rests" is an option too far, IMHO.
I do think it has flushed out some issues over rest collision avoidance,
though.
--
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
