Hi Dan,
It may or may not be appropriate for your needs, but you could consider
using proportional spacing.
Add something like this and you obtain a much more nicely controlled
appearance.
== snip
\layout {
\context {
\Score
proportionalNotationDuration = #(ly:make-moment
> On May 11, 2017, at 1:40 PM, Knute Snortum wrote:
>
> I think you have to move the accidental to get the note to move. I don't
> really like the way the following looks, but at least it's an example of
> moving the accidental:
>
> rightTwo = \relative c' {
> c4
I think you have to move the accidental to get the note to move. I don't
really like the way the following looks, but at least it's an example of
moving the accidental:
rightTwo = \relative c' {
c4 \tuplet 3/2 { d4 \tweak Accidental.Y-offset -0.25 cis8 }
}
---
Knute Snortum
(via Gmail)
On
In the code below, the last eighth note in voice two of both the right and left
hand are too far to the right (even slightly more so in the piece from which
this excerpt is taken, shown in the attached image). I’ve fiddled with various
values using \once \override NoteColumn.force-hshift and
2008/12/11 Stefan Waler [EMAIL PROTECTED]:
I attach a sample script, please note the accidentials for 'ces' in the
second and for 'fes' in the forth bar. I tried to simplify the score very
much, but it seems as lilypond continues to calculate wrong spaces for every
further accidental of this
It seems that the accidentals that are not printed in the new measure
because of the tie,
are not removed completely, but just made invisible still taking space.
/Mats
Valentin Villenave wrote:
2008/12/11 Stefan Waler [EMAIL PROTECTED]:
I attach a sample script, please note the
Thanks for the analysis!
Do you think there is any workaround?
Any chance to get this fixed in 2.11?
Stefan
Mats Bengtsson wrote:
It seems that the accidentals that are not printed in the new measure
because of the tie,
are not removed completely, but just made invisible still taking space.
2008/12/11 Stefan Waler [EMAIL PROTECTED]:
Do you think there is any workaround?
There's a workaround mentioned here:
http://code.google.com/p/lilypond/issues/detail?id=612
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
2008/12/11 Neil Puttock n.putt...@gmail.com:
There's a workaround mentioned here:
http://code.google.com/p/lilypond/issues/detail?id=612
Oh, I thought this one looked familiar but i couldn't find it. Thanks Neil!
Cheers,
Valentin
___
lilypond-user