Preventing final mark from removing final tuplet: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Due to [https://gitlab.com/lilypond/lilypond/-/issues/2362 issue #2362] the addition of a final <code>mark</code> can result in the loss of a final tuplet marking. This can be overcome by setting <code>TupletBracket.full-length-to-extent</code> to <code> | Due to [https://gitlab.com/lilypond/lilypond/-/issues/2362 issue #2362] the addition of a final <code>mark</code> can result in the loss of a final tuplet marking. This can be overcome by setting <code>TupletBracket.full-length-to-extent</code> to <code>#f</code>. | ||
<lilypond version="2.24"> | <lilypond version="2.24"> | ||
Latest revision as of 08:29, 8 December 2025
Due to issue #2362 the addition of a final mark can result in the loss of a final tuplet marking. This can be overcome by setting TupletBracket.full-length-to-extent to #f.
\version "2.24"
\new Staff {
\set tupletFullLength = ##t
\time 1/8
\tuplet 3/2 8 { c'16 c' c' c' c' c' c' c' c' }
\tweak direction #DOWN \textEndMark "1234"
}
\new Staff {
\set tupletFullLength = ##t
\override TupletBracket.full-length-to-extent = ##f
\time 1/8
\tuplet 3/2 8 { c'16 c' c' c' c' c' c' c' c' }
\tweak direction #DOWN \textEndMark "1234"
}
