Hi all,
I know two solutions to this problem. Tuplet brackets disappear when
the spacing gets tight, and seems to be a Lilypond "feature" rather
than a bug. The first solution is to manually increase the spacing
between notes in a tuplet:
\once \override Score.SeparationItem #'padding = #0.7
or something like that - you may need to increase the 0.7.
The second is an ugly hack, which prints the bracket under all
circumstances but doesn't look particularly good:
\once \override Score.TupletNumber #'X-extent = #'(0 . 0)
Because Lilypond uses the ratio between the TupletNumber X-extent and
the TupletBracket X-extent to decide whether to print the
TupletBracket, by setting the TupletNumber X-extent to ) you always
get a bracket, but the bracket runs into the number. (I'm sure you
gave that to me at some point, Mats.)
I would agree that this is a problem that should be resolved, at least
to give users the option of always having a bracket printed.
Hope this helps,
Vivian.
On Aug 30, 2007, at 7:26 PM, Nick Didkovsky wrote:
Hello Mats
Today I had the same problem appear on a piano part that I extracted
with default staff size. I got an 8th note followed by a qtr note,
with only the number "3" below them, with no bracket. Boo.
This is a real problem, and as I understand there may not be a fix,
how should I proceed to ensure that this issue is addressed in future
version of LilyPond?
Thank-you
Nick
Mats Bengtsson wrote:
Brackets that would be too short to print nicely are automatically
removed.
As far as I can remember, there is no possibility to specify the
minimum width
of a triplet and force LilyPond to modify the note spacing to get at
least this
width, but I may be wrong. There are such possibilities on some
other objects,
like slurs, for example.
/Mats
Nick Didkovsky wrote:
Hello,
I am using the following commands to get a short 6-measure, 9-staff
piece to fit on one page:
#(set-default-paper-size "letter" 'landscape)
#(set-global-staff-size 13)
At this size, I discovered some (not all) of by triplet brackets
disappear.
Has anyone experienced this? Is there a fix (other than using a
larger global staff size)?
Thank-you
Nick Didkovsky
_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user