bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2400 in lilypond: Dots no longer aligned between voices


From: lilypond
Subject: Re: Issue 2400 in lilypond: Dots no longer aligned between voices
Date: Fri, 16 Mar 2012 04:24:06 +0000

Updates:
        Labels: patch-new

Comment #1 on issue 2400 by address@hidden: Dots no longer aligned between voices
http://code.google.com/p/lilypond/issues/detail?id=2400

The original complaint was the misalignment marked by -- in the attached music. There was also a complaint that dots can be mistaken for staccato notes as in the situations marked by -. and this case is set in Stone's textbook with dots aligned. On the other hand, in the second of these examples with only the upper voice dotted, I think we would rather keep the dot close to the note than move the dot and upper note far to the right.

Looking more at dot situations, I noticed the tight configuration marked by the teardrop staccatissimo sign.

These upper-voice dots could be perfectly aligned by adding nearby lower-voice note-heads to the list of "support" grobs that determine the location of the upper voice's dots, and increasing the vertical range of the "support" if the supporting notehead has its own dot(s).

Other effects of having one Dot_column_engraver handle all voices, are that dots can move to make room for dots from other voices. The clusters marked with -2 and -3 get a dot for each notehead if the Dot_column_engraver works at Staff level.

Ideally, we would make Dot_column_engraver smart enough to do the things mentioned above, but still let dots align independently in chords such as the one marked by the trill, which is the example used in Ross' textbook to show why dots in different voices should be independently aligned.

Until we have the ideal, I intend to put the Dot_column_engraver back in Staff where it was in version 2.14 <http://codereview.appspot.com/5846043>, even though I will move it to Voice in my own scores.

Attachments:
        2400.png  4.7 KB
        2400.after.png  4.7 KB




reply via email to

[Prev in Thread] Current Thread [Next in Thread]