Re: [Lilypond-auto] Issue 3324 in lilypond: Avoid collision of voices

[lilypond]

Comment #2 on issue 3324 by address@hidden: Avoid collision of voices
http://code.google.com/p/lilypond/issues/detail?id=3324

The visuals for case 2 are a valid representation of two-voice music,  
namely when the voices are inversed.  LilyPond assumes a voice order iff  
implicit voices are separated by \\ but otherwise relies on the user's  
specification of \voiceOne/\voiceTwo etc.  It is more or less an accident  
that case 2 happens to work without collision: like the other cases the  
user input does not reflect an intent of voiced stem directions.

So LilyPond is working as expected, not trying to make sense of an input  
where the user is supposed to choose meaning.  Should LilyPond generally  
try to pick some voicing order as tie breaker?  That would be a feature  
request, but I am not really sympathetic to it.

My vote is on "invalid issue".

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