The most reasonable solution would be to move the slurs to
begin at the tip of the stem instead of starting close to the note head
in these situations.
The intuitive approach to handle these situations would be to set
the avoid-slur property on stems and note heads, but clearly it doesn't
work here. Slurs already avoid note heads and stems in their own voice,
but as your example shows, there is no collision avoidance between slurs
in one voice and note heads/stems in other voices.
In version 2.2 and earlier, we used to have a property called
attachment, so you
for example could specify
\override Slur #'attachment = #(stem . stem)
to make the slur start at the end of the stem. Then, the slur
implementation was
completely rewritten and the set of available properties was changed.
Your example illustrates that the attachment property might still be useful
(at least waiting for the ultimate collision avoidance algorithm to be
implemented).
Currently, what you can do is to manually set the absolute vertical
position of the
end points of the slur, for example
\once \override Slur #'positions = #'(2.5 . 4.0) g,2( e')
but this is a very tedious job.
/Mats
Zoltán Selyem wrote:
%% Though I have no idea where and how to place these slurs
%% according to classical typographical rules...
%% Slurs collide with polyphonic music
%% In the last measure the lower slur points to the wrong note
\version "2.11.21"
\paper{ ragged-right=##t }
\relative g' {
\voiceOne
<<
{
g2( e') | c( g) | e'( e,) | e'2.( e,4) |
}
\new Voice{ \voiceTwo
c'2( g) | g( c) | g4 a b c | g( g g g') |
}
>>
\oneVoice
}
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
