[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1352 in lilypond: Polyphonic dots placement is inconsistent, conf
From: |
lilypond |
Subject: |
Issue 1352 in lilypond: Polyphonic dots placement is inconsistent, confusing and prone to collisions |
Date: |
Thu, 21 Oct 2010 10:13:16 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Collision Priority-Medium
New issue 1352 by v.villenave: Polyphonic dots placement is inconsistent,
confusing and prone to collisions
http://code.google.com/p/lilypond/issues/detail?id=1352
% Reported by Nick Payne on -user.
Dots may be placed differently, as demonstrated below:
\version "2.13.36"
\relative c' {
<< % This octave produces the nicest result.
{ e8. f16} \\
{ bes,,4 } \\
{ <g' d'>}
<< % One octave higher: the dot looks like it belongs to another note.
{ e''8. f16} \\
{ bes,,4 } \\
{ <g' d'> }
<< % Here's what it would look like if it did belong to the other note.
{ e'8*3/2 f16 } \\
{ bes,,4 } \\
{ <g' d'>4.*2/3 }
<< % Removing the chord to avoid Issue 1266; then an ugly collision occurs.
{ e'8. f16} \\
{ bes,,4 } \\
{ d' }
}
See also issue 51 and issue 339 (both are closed, so it's not a regression).
The << \\ >> construct is used here for clarity, but using \new Voice
\voiceTwo etc. also reproduces the problem.
Attachments:
ex.png 2.2 KB
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 1352 in lilypond: Polyphonic dots placement is inconsistent, confusing and prone to collisions,
lilypond <=