> I'm not top posting.
\version "2.15.23" % also 2.14.2
\markup { Here is how beamed quaver tuplets look now; ugly, with some colliding
with the staff lines: }
\relative f' {
\times 2/3 { f8 f f }
\times 2/3 { e e e }
\times 2/3 { d d d }
\times 2/3 { c c c } % All lower notes are the same as this;
\times 2/3 { b b b } % the beam will go no lower
\override TupletBracket #'bracket-visibility = ##t
\times 2/3 { f' f f }
\times 2/3 { e e e }
\times 2/3 { d d d }
\times 2/3 { c c c }
\times 2/3 { b b b }
}
\markup { Here is somewhat more how they should look (dodging the staff lines):
}
\relative f' {
\times 2/3 { f8 f f }
\tweak #'padding #1.80 \times 2/3 { e e e }
\tweak #'padding #1.95 \times 2/3 { d d d }
% Well, actually, I'm not convinced about these last two.
\tweak #'padding #2.75 \times 2/3 { c c c }
\tweak #'padding #2.75 \times 2/3 { b b b }
\override TupletBracket #'bracket-visibility = ##t
\times 2/3 { f' f f }
\tweak #'padding #1.95 \times 2/3 { e e e }
\tweak #'padding #2.10 \times 2/3 { d d d }
\tweak #'padding #2.90 \times 2/3 { c c c }
\tweak #'padding #2.90 \times 2/3 { b b b }
}
\markup \column {
\line { Where there is no beam (e.g. crochets, "\autoBeamOff"), this issue
doesn't appear at all. }
\line { (Though the number alone with no TupletBracket is, in my opinion, too
high.) }
}
\relative f' {
\autoBeamOff
\override TupletBracket #'bracket-visibility = ##f
\times 2/3 { f8 f f }
\times 2/3 { e e e }
\times 2/3 { d d d }
\times 2/3 { c c c }
\times 2/3 { b b b }
\override TupletBracket #'bracket-visibility = ##t
\times 2/3 { f' f f }
\times 2/3 { e e e }
\times 2/3 { d d d }
\times 2/3 { c c c }
\times 2/3 { b b b }
}
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
