LilyPond wiki - User contributions [en]

Table of contents section command

2026-07-19T04:24:41Z

Lemzwerg:

If you have several pieces in several files, you might want to build a book from that. Assume you have a master file which includes the pieces:

\include "tune1.ly"
\include "tune2.ly"

In your piece-files you might have <code>\tocItem</code> commands to build the table of contents.

With the following snippet, you can replace those <code>\tocItem</code> commands with <code>#(set-toc-section! "''section''")</code> in the master file:

#(set-toc-section! "tunes")
\include "tune1.ly"
\include "tune2.ly"
#(set-toc-section! "parts")
\include "part1.ly"
\include "part2.ly"

Now every section is introduced with a section line in the table of contents only if the section title was set before. If you reorder the parts (includes), the sections will still appear in the right place. This is meant for compiling a collection of pieces, which also compile themselves. For a complete opus with pieces, see [[Ready-to-use LilyPond macros: advanced layout and titles, using a special stylesheet]].

<lilypond version="2.24" full>
% define toc-section commands
#(begin
(define-public (set-toc-section! text) #f)
(define-public (get-toc-section text) #f)
(let ((toc-section #f))
(set! set-toc-section! (lambda (text)(set! toc-section text)))
(set! get-toc-section (lambda ()(begin toc-section)))))

% define section-aware piece-toc-item-command
piece = #(define-music-function (text) (markup?)
(begin
(if (get-toc-section)
(add-toc-item! 'tocCollMarkup (get-toc-section)))
(set-toc-section! #f)
(add-toc-item! 'tocPartMarkup text)))

\paper {
% A small paper size for demonstration purposes.
#(set-paper-size '(cons (* 100 mm) (* 50 mm)))

% this will not know the page number!
tocCollMarkup = \markup { \fill-line {
\bold \fromproperty #'toc:text \vspace #1 \null } }
tocPartMarkup = \markup { \fill-line {
\concat { \hspace #2 \fromproperty #'toc:text }
\vspace #0 \fromproperty #'toc:page } }
}

% some music pieces ...
\bookpart {
\markuplist {
\override-lines #'(baseline-skip . 2.3)
\table-of-contents
}
}
#(set-toc-section! "section 1")
\bookpart {
\piece \markup { "piece 1" }
\score {
\relative c' {
c d e f g
}
}
}
\bookpart {
\piece \markup { "piece 2" }
\score {
\relative c' {
c d e f
}
}
}
#(set-toc-section! "section 2")
\bookpart {
\piece \markup { "piece 1" }
\score {
\relative c' {
c d e f
}
}
}
\bookpart {
\piece \markup { "piece 2" }
\score {
\relative c' {
c d e f
}
}
}
</lilypond>

[[Category:Titles]]
[[Category:Paper and layout]]
[[Category:Snippet]]

Figured bass centered horizontally on note heads

2026-07-13T15:49:35Z

Lemzwerg: Lemzwerg moved page Figured bass centered on whole notes to Figured bass centered horizontally on note heads without leaving a redirect

Due to [https://gitlab.com/lilypond/lilypond/-/work_items/3172 LilyPond issue #3172], the horizontal alignment of bass figures attached to whole notes is flawed. Below you can find a solution (contributed by [https://lists.gnu.org/archive/html/lilypond-user/2026-06/msg00250.html Tina Petzel]) that works around this problem,

* providing a replacement function <code>c-format-bass-figure</code> for the <code>figuredBassFormatter</code> property to center the base digit,
* creating a small engraver called <code>figures-to-note-column-engraver</code> that changes the X parent of bass figures to <code>NoteColumn</code> grobs, and
* setting some bass figure properties to center-align them with main note heads.

A convenience macro <code>\CenteredFiguredBass</code> is defined to do these tasks.

There are limitations, though. It is necessary that <code>figures-to-note-column-engraver</code> lives in a context that is an ancestor of both <code>Rhythmic_column_engraver</code> (typically part of <code>Voice</code>) and <code>Figured_bass_engraver</code>. Examples:

\new Staff \with { \CenteredFiguredBass }
<<
{ bass music }
\figuremode { figured bass }
>>

\new StaffGroup \with { \CenteredFiguredBass }
<<
\new Staff { ... }
\new FiguredBass { ... }
>>

In the rare case that you have multiple voices in the bass staff you might want to move the <code>Figured_bass_engraver</code> to <code>Voice</code>.

<lilypond version="2.26">
#(set-global-staff-size 26)

#(define-public (c-format-bass-figure figure event context)
(let* (;; User properties controlling the figured bass layout.
(figbass-alist
(ly:context-property context 'figuredBassPlusStrokedAlist))
(alt-dir
(ly:context-property context 'figuredBassAlterationDirection))
(plus-dir
(ly:context-property context 'figuredBassPlusDirection))
(augmented (ly:event-property event 'augmented))
(number-one (make-number-markup "1"))

;; The digit(s), horizontally positioned, or #f.
(fig-markup
(if (number? figure)
(make-center-align-markup
(cond
((eq? #t (ly:event-property event 'diminished))
(make-slashed-digit-markup figure))
((eq? #t (ly:event-property event 'augmented-slash))
;; Use specially stroked digit if available and wanted.
(or (and-let* (((<= 6 figure 9))
(glyph (assv-ref figbass-alist figure)))
(make-musicglyph-markup glyph))
(make-backslashed-digit-markup figure)))
((eq? #t augmented)
;; Use special digit with plus if available and wanted.
(or (and-let* (((>= 5 figure 2))
((eqv? plus-dir RIGHT))
(glyph (assv-ref figbass-alist figure)))
(set! augmented #f)
(make-musicglyph-markup glyph))
(make-number-markup (number->string figure 10))))
(else (make-number-markup (number->string figure 10)))))
#f))

(alt (ly:event-property event 'alteration))
(alt-bracket (ly:event-property event 'alteration-bracket #f))
;; The alteration, probably bracketed but not positioned yet,
;; or #f.
(alt-markup
(if (number? alt)
(let* ((acc (assoc-get alt (@@ (lily) figbass-accidental-alist)))
(acc-markup
(if acc
(make-number-markup (ly:wide-char->utf-8 acc))
(begin
(ly:warning
(G_ "no accidental glyph found for alteration ~a")
alt)
;; fallback
"?"))))
(if alt-bracket
(make-bracket-markup acc-markup)
acc-markup))
#f))

(plus-markup (if (eq? #t augmented)
(make-number-markup "+")
#f)))

(if (and (not alt-markup) alt-bracket)
(ly:programming-error
"Cannot put brackets around non-existent bass figure alteration."))

;; We treat a solitary alteration similarly to digits.
(if (and (not fig-markup) alt-markup)
(begin
(set! fig-markup
(make-center-align-markup alt-markup))
(set! alt-markup #f)))

;; We treat a solitary plus similarly to digits (but enlarged).
(if (and (not fig-markup) plus-markup)
(begin
(set! fig-markup
(make-align-on-other-markup
Y
CENTER number-one
CENTER
(make-center-align-markup
(make-fontsize-markup 3 plus-markup))))
(set! plus-markup #f)))

;; The alteration gets attached either to the left or the right of
;; the digit(s).
(if alt-markup
(set! fig-markup
(make-put-adjacent-markup
X (if (number? alt-dir)
alt-dir
LEFT)
fig-markup
(make-pad-x-markup 0.1 alt-markup))))

;; Ditto for the plus mark.
(if plus-markup
(set! fig-markup
(if fig-markup
(make-put-adjacent-markup
X (if (number? plus-dir)
plus-dir
LEFT)
fig-markup plus-markup)
plus-markup)))

(if (markup? fig-markup)
(make-fontsize-markup -5 fig-markup)
(make-null-markup))))

#(define (figures-to-note-column-engraver context)
(let ((figs '()) (nc #f))
(make-engraver
(acknowledgers
((bass-figure-interface engraver grob source)
(set! figs (cons grob figs)))
((note-column-interface engraver grob source)
(set! nc grob)))
((process-acknowledged engraver)
(if nc
(for-each
(lambda (g)
(ly:grob-set-parent! g X nc))
figs))
(set! nc #f)
(set! figs '())))))

CenteredFiguredBass = \with {
\consists #figures-to-note-column-engraver
\override BassFigure.X-align-on-main-noteheads = ##t
\override BassFigure.parent-alignment-X = #CENTER
\override BassFigure.X-offset =
#ly:self-alignment-interface::aligned-on-x-parent
figuredBassFormatter = #c-format-bass-figure
}

%%%%%%%%%%%%%%%%%%%%%%%%%%%

\new Staff \with { \CenteredFiguredBass }
<<
{ c'1 4 8 8 }
\figuremode {
\override Staff.BassFigureAlignment.stacking-dir = #DOWN
<15- 7+ 6/ 4\+ 3- _+ _\+>1 4 8 8
}
>>

\new StaffGroup \with { \CenteredFiguredBass }
<<
% To make the figured bass stuff appear in the source file
% before the music we have to initialize the `Staff` context
% first (and fill it later).
\new Staff = "mystaff"
\figuremode {
\override Staff.BassFigureAlignment.stacking-dir = #UP
% Work around issue #6552, fixing bracket positions.
\override Staff.BassFigureAlignmentPositioning
.outside-staff-priority = ##f
<3 [5 7]>8
<3\+ [5/] 7/ [9 11]>
<3+ 5- 7!>
<3 _! 5 _- 7>
<3 _\+ 5 _ 7>
<3 6/ >
<3 6\\ >
<6> |
<3 [5 7]>1
}
\context Staff = "mystaff" {
\clef bass
c4 c c'8 c c16 c c c | c1
}
>>

\new StaffGroup \with { \CenteredFiguredBass }
<<
\new Staff = "mystaff" {
\clef bass
c4 c f,8 c c16 c c c | c1
}
\figuremode {
\override Staff.BassFigureAlignment.stacking-dir = #UP
\override Staff.BassFigureAlignmentPositioning.direction = #DOWN
% Work around issue #6552, fixing bracket positions.
\override Staff.BassFigureAlignmentPositioning
.outside-staff-priority = ##f
<3 [5 7]>8
<3\+ [5/] 7/ [9 11]>
<3+ 5- 7!>
<3 _! 5 _- 7>
<3 _\+ 5 _ 7>
<3 6/ >
<3 6\\ >
<6> |
<3 [5 7]>1
}
>>
</lilypond>

[[Category:Ancient notation]]
[[Category:Chords]]
[[Category:Workaround]]
[[Category:Snippet]]

Figured bass centered horizontally on note heads

2026-07-13T15:48:49Z

Lemzwerg:

Figured bass centered horizontally on note heads

2026-07-12T19:14:20Z

Lemzwerg: Created page with "Due to [https://gitlab.com/lilypond/lilypond/-/work_items/3172 LilyPond issue #3172], bass figures are currently not centered automatically on whole notes. Below you can find a solution (contributed by [https://lists.gnu.org/archive/html/lilypond-user/2026-06/msg00250.html Tina Petzel]) that works around this issue by * providing a replacement function <code>c-format-bass-figure</code> for the <code>figuredBassFormatter</code> property to center the base digit, * creati..."

Due to [https://gitlab.com/lilypond/lilypond/-/work_items/3172 LilyPond issue #3172], bass figures are currently not centered automatically on whole notes. Below you can find a solution (contributed by [https://lists.gnu.org/archive/html/lilypond-user/2026-06/msg00250.html Tina Petzel]) that works around this issue by

* providing a replacement function <code>c-format-bass-figure</code> for the <code>figuredBassFormatter</code> property to center the base digit,
* creating a small engraver called <code>figures-to-note-column-engraver</code> that changes the X parent of bass figures to <code>NoteColumn</code> grobs, and
* setting some bass figure properties to center-align them with main note heads.

A convenience macro <code>\CenteredFiguredBass</code> is defined to do these tasks.

There are limitations, though. It is necessary that <code>figures-to-note-column-engraver</code> lives in a context that is an ancestor of both <code>Rhythmic_column_engraver</code> (typically part of <code>Voice</code>) and <code>Figured_bass_engraver</code>. Examples:

\new Staff \with { \CenteredFiguredBass }
<<
{ bass music }
\figuremode { figured bass }
>>

\new StaffGroup \with { \CenteredFiguredBass }
<<
\new Staff { ... }
\new FiguredBass { ... }
>>

In the rare case that you have multiple voices in the bass staff you might want to move the <code>Figured_bass_engraver</code> to <code>Voice</code>.

<lilypond version="2.26">
#(set-global-staff-size 26)

#(define-public (c-format-bass-figure figure event context)
(let* (;; User properties controlling the figured bass layout.
(figbass-alist
(ly:context-property context 'figuredBassPlusStrokedAlist))
(alt-dir
(ly:context-property context 'figuredBassAlterationDirection))
(plus-dir
(ly:context-property context 'figuredBassPlusDirection))
(augmented (ly:event-property event 'augmented))
(number-one (make-number-markup "1"))

;; The digit(s), horizontally positioned, or #f.
(fig-markup
(if (number? figure)
(make-center-align-markup
(cond
((eq? #t (ly:event-property event 'diminished))
(make-slashed-digit-markup figure))
((eq? #t (ly:event-property event 'augmented-slash))
;; Use specially stroked digit if available and wanted.
(or (and-let* (((<= 6 figure 9))
(glyph (assv-ref figbass-alist figure)))
(make-musicglyph-markup glyph))
(make-backslashed-digit-markup figure)))
((eq? #t augmented)
;; Use special digit with plus if available and wanted.
(or (and-let* (((>= 5 figure 2))
((eqv? plus-dir RIGHT))
(glyph (assv-ref figbass-alist figure)))
(set! augmented #f)
(make-musicglyph-markup glyph))
(make-number-markup (number->string figure 10))))
(else (make-number-markup (number->string figure 10)))))
#f))

(alt (ly:event-property event 'alteration))
(alt-bracket (ly:event-property event 'alteration-bracket #f))
;; The alteration, probably bracketed but not positioned yet,
;; or #f.
(alt-markup
(if (number? alt)
(let* ((acc (assoc-get alt (@@ (lily) figbass-accidental-alist)))
(acc-markup
(if acc
(make-number-markup (ly:wide-char->utf-8 acc))
(begin
(ly:warning
(G_ "no accidental glyph found for alteration ~a")
alt)
;; fallback
"?"))))
(if alt-bracket
(make-bracket-markup acc-markup)
acc-markup))
#f))

(plus-markup (if (eq? #t augmented)
(make-number-markup "+")
#f)))

(if (and (not alt-markup) alt-bracket)
(ly:programming-error
"Cannot put brackets around non-existent bass figure alteration."))

;; We treat a solitary alteration similarly to digits.
(if (and (not fig-markup) alt-markup)
(begin
(set! fig-markup
(make-center-align-markup alt-markup))
(set! alt-markup #f)))

;; We treat a solitary plus similarly to digits (but enlarged).
(if (and (not fig-markup) plus-markup)
(begin
(set! fig-markup
(make-align-on-other-markup
Y
CENTER number-one
CENTER
(make-center-align-markup
(make-fontsize-markup 3 plus-markup))))
(set! plus-markup #f)))

;; The alteration gets attached either to the left or the right of
;; the digit(s).
(if alt-markup
(set! fig-markup
(make-put-adjacent-markup
X (if (number? alt-dir)
alt-dir
LEFT)
fig-markup
(make-pad-x-markup 0.1 alt-markup))))

;; Ditto for the plus mark.
(if plus-markup
(set! fig-markup
(if fig-markup
(make-put-adjacent-markup
X (if (number? plus-dir)
plus-dir
LEFT)
fig-markup plus-markup)
plus-markup)))

(if (markup? fig-markup)
(make-fontsize-markup -5 fig-markup)
(make-null-markup))))

#(define (figures-to-note-column-engraver context)
(let ((figs '()) (nc #f))
(make-engraver
(acknowledgers
((bass-figure-interface engraver grob source)
(set! figs (cons grob figs)))
((note-column-interface engraver grob source)
(set! nc grob)))
((process-acknowledged engraver)
(if nc
(for-each
(lambda (g)
(ly:grob-set-parent! g X nc))
figs))
(set! nc #f)
(set! figs '())))))

CenteredFiguredBass = \with {
\consists #figures-to-note-column-engraver
\override BassFigure.X-align-on-main-noteheads = ##t
\override BassFigure.parent-alignment-X = #CENTER
\override BassFigure.X-offset =
#ly:self-alignment-interface::aligned-on-x-parent
figuredBassFormatter = #c-format-bass-figure
}

%%%%%%%%%%%%%%%%%%%%%%%%%%%

\new Staff \with { \CenteredFiguredBass }
<<
{ c'1 4 8 8 }
\figuremode {
\override Staff.BassFigureAlignment.stacking-dir = #DOWN
<15- 7+ 6/ 4\+ 3- _+ _\+>1 4 8 8
}
>>

\new StaffGroup \with { \CenteredFiguredBass }
<<
% To make the figured bass stuff appear in the source file
% before the music we have to initialize the `Staff` context
% first (and fill it later).
\new Staff = "mystaff"
\figuremode {
\override Staff.BassFigureAlignment.stacking-dir = #UP
% Work around issue #6552, fixing bracket positions.
\override Staff.BassFigureAlignmentPositioning
.outside-staff-priority = ##f
<3 [5 7]>8
<3\+ [5/] 7/ [9 11]>
<3+ 5- 7!>
<3 _! 5 _- 7>
<3 _\+ 5 _ 7>
<3 6/ >
<3 6\\ >
<6> |
<3 [5 7]>1
}
\context Staff = "mystaff" {
\clef bass
c4 c c'8 c c16 c c c | c1
}
>>

\new StaffGroup \with { \CenteredFiguredBass }
<<
\new Staff = "mystaff" {
\clef bass
c4 c f,8 c c16 c c c | c1
}
\figuremode {
\override Staff.BassFigureAlignment.stacking-dir = #UP
\override Staff.BassFigureAlignmentPositioning.direction = #DOWN
% Work around issue #6552, fixing bracket positions.
\override Staff.BassFigureAlignmentPositioning
.outside-staff-priority = ##f
<3 [5 7]>8
<3\+ [5/] 7/ [9 11]>
<3+ 5- 7!>
<3 _! 5 _- 7>
<3 _\+ 5 _ 7>
<3 6/ >
<3 6\\ >
<6> |
<3 [5 7]>1
}
>>
</lilypond>

[[Category:Ancient notation]]
[[Category:Chords]]
[[Category:Workaround]]
[[Category:Snippet]]

Basic Roman numeral and figured bass analysis

2026-07-12T11:58:18Z

Lemzwerg:

If you need to create some basic roman numeral and figured bass analysis within the body of a score, you can create a staff with the standard engravers removed and add markup to spaces.

<lilypond version="2.24">
<<
\new Staff \relative c' {
<c e g>2 <c f a> | <c e g> <b d g> | <c e g>1 |
}

\new Staff \with {
\remove "Staff_symbol_engraver"
\remove "Time_signature_engraver"
\remove "Clef_engraver"
} {
s2^\markup { \halign #2 C: I }
s^\markup { \super \column { 6 \vspace #-0.4 4 } } |
s^\markup { \super \column { 5 \vspace #-0.4 3 } }
s^\markup { \lower #1 "V" \super \column { 6 \vspace #-0.5 3 } } |
s1^\markup "I"
}
>>
</lilypond>

[[Category:Text]]
[[Category:Specific notation]]
[[Category:Chords]]
[[Category:Snippet]]

Figured bass with alternate baroque notation

2026-07-12T11:51:39Z

Lemzwerg:

Most renaissance and baroque scores use specific symbols for bass figures, particularly for augmented sixths with a backslash striking only the upper part of the number six (or sometimes the number nine), and “plus” symbols integrated with the number four (and sometimes the numbers two or five as well; this notation may also be used for integrating flat and natural accidentals).

Here is a way to obtain such symbols in the printed output whilst keeping the usual syntax for figured bass entry. This is done not with native MetaFont glyphs, but by combining PostScript code (using Scheme syntax so that SVG output is supported) and additional stencils in markup definitions.

Note that LilyPond version 2.24 natively supports the first five symbols (i.e., the ones with an added slash); see snippet [[Adjusting figured bass alteration glyphs]].

<lilypond version="2.24">
%% Glyph definitions:

openedSix = \markup
\scale #'(.0045 . .0045)
\override #'(filled . #t) \path #0
#'(
(moveto 117.5 192)
(curveto 82.25 192 80 164.25 80 126)
(lineto 80 85.5)
(curveto 80 47.25 82.25 19.5 117.5 19.5)
(curveto 159.5 19.5 161 57 161 105.75)
(curveto 161 154.5 159.5 192 117.5 192)
(closepath)
(moveto 80 201.75)
(curveto 92 207 104 211.5 117.5 211.5)
(curveto 194.75 211.5 247.25 177.75 247.25 105.75)
(curveto 247.25 33.75 194.75 0 117.5 0)
(curveto 75.125 0 42.688 23.25 20.844 58.312)
(curveto -16.164 111.789 -2.754 186.469 52.051 249.164)
(curveto 79.453 280.512 117.207 308.863 164.184 330.07)
(curveto 211.156 351.281 266.695 381.359 285.328 352.68)
(curveto 225.148 344.094 166.652 307.07 129.25 276.117)
(curveto 91.852 245.164 79.973 217.148 80 201.75)
(closepath))

elongatedTwo = \markup \combine
\scale #'(.0045 . .0045)
\override #'(filled . #t) \path #0
#'(
(moveto 19.5 6.879)
(curveto 19.5 6.879 4.566 -11.469 0 10.5)
(curveto 13.371 124.34 175.5 132.75 175.5 266.25)
(curveto 175.5 309.75 163.5 355.5 126 355.5)
(curveto 105 355.5 84.75 345.75 84.75 327)
(curveto 84.75 306.75 111 297 111 276.75)
(curveto 111 249 87.75 226.5 60 226.5)
(curveto 32.25 226.5 9.75 249 9.75 276.75)
(curveto 9.75 334.5 64.5 375 126 375)
(curveto 198.75 375 269.289 332.98 267.75 266.25)
(curveto 265.629 174.344 163.785 139.562 93.676 91.652)
(curveto 55.66 65.676 19.5 6.879 19.5 6.879)
(closepath))
\translate #'(.12 . 0) \override #'(thickness . 2.2) \draw-line #'(1.6 . 0)

elongatedFive = \markup \combine
\scale #'(.0045 . .0045)
\override #'(filled . #t) \path #0
#'(
(moveto 48 361.164)
(lineto 48 210.75)
(curveto 69 231.75 97.5 240.75 126.75 240.75)
(curveto 213.75 240.75 267 202.5 267 120)
(curveto 267 48.75 198 0 122.25 0)
(curveto 60 0 0 31.5 0 87)
(curveto 0 113.25 21.75 135 48 135)
(curveto 74.25 135 96 113.25 96 87)
(curveto 96 69 66.75 65.25 66.75 47.25)
(curveto 66.75 24 95.25 19.5 122.25 19.5)
(curveto 164.25 19.5 175.5 71.25 175.5 120)
(curveto 175.5 165.75 166.5 216.75 126.75 216.75)
(curveto 95.25 216.75 63.75 210 45.75 185.25)
(curveto 43.5 181.5 39.75 180 36 180)
(curveto 30 180 23.25 184.5 23.25 192)
(lineto 23.25 361.5)
(curveto 23.25 374.117 47.941 375.473 48 361.164)
(closepath))
\translate #'(.22 . 1.58) \override #'(thickness . 2) \draw-line #'(1.6 . 0)

%% Some notations defined as markup/glyph combinations:

plusTwo = \markup \combine \elongatedTwo
\translate #'(1.35 . .35) \override #'(thickness . 1.8) \draw-line #'(0 . -.7)

dimTwo = \markup \combine \elongatedTwo
\translate #'(1.3 . -.8) \scale #'(.7 . .7) \flat

natTwo = \markup \combine \combine \elongatedTwo
\translate #'(1.34 . .35) \override #'(thickness . 1.4) \draw-line #'(0 . -1.75)
\translate #'(1.3 . -.9) \scale #'(.7 . .7) \natural

elongatedFour = \markup \combine
\scale #'(.8 . .8) \number 4
\translate #'(.08 . .48) \override #'(thickness . 1.8) \draw-line #'(2 . 0)

plusFour = \markup \combine \elongatedFour
\translate #'(1.7 . .84) \override #'(thickness . 1.8) \draw-line #'(0 . -.7)

dimFour = \markup \combine \elongatedFour
\translate #'(1.7 . -.4) \scale #'(.7 . .7) \flat

natFour = \markup \combine \combine \elongatedFour
\translate #'(1.73 . .84) \override #'(thickness . 1.4) \draw-line #'(0 . -1.75)
\translate #'(1.7 . -.4) \scale #'(.7 . .7) \natural

plusFive = \markup \combine \elongatedFive
\translate #'(1.45 . 1.94) \override #'(thickness . 1.8) \draw-line #'(0 . -.7)

dimFive = \markup \combine \elongatedFive
\translate #'(1.4 . .9) \scale #'(.6 . .6) \flat

natFive = \markup \combine \combine \elongatedFive
\translate #'(1.43 . 1.94) \override #'(thickness . 1.4) \draw-line #'(0 . -1.55)
\translate #'(1.4 . .8) \scale #'(.6 . .6) \natural

slashedSix = \markup \combine \openedSix
\translate #'(.5 . 1.6) \override #'(thickness . 1.2) \draw-line #'(.8 . -0.35)

elongatedSix = \markup \combine \openedSix
\translate #'(1.1 . 1.6) \override #'(thickness . .8) \draw-line #'(.6 . .13)

dimSix = \markup \combine \elongatedSix
\translate #'(1.4 . .9) \scale #'(.6 . .6) \flat

natSix = \markup \combine \combine \elongatedSix
\translate #'(1.42 . 2.1) \override #'(thickness . 1.4) \draw-line #'(0 . -1.6)
\translate #'(1.4 . .9) \scale #'(.6 . .6) \natural

slashedNine = \markup \rotate #180 \slashedSix

%% Formatter function:

#(define-public (vv-format-bass-figure figure event context)
(let ((fig (ly:event-property event 'figure))
(slash (eq? #t (ly:event-property event 'augmented-slash)))
(aug (eq? #t (ly:event-property event 'augmented)))
(alt (ly:event-property event 'alteration)))
(cond
(slash (case figure
((6) slashedSix)
((9) slashedNine)
(else (format-bass-figure figure event context))))
; limitation: numbers that are both slashed _and_ augmented
; will be disregarded. (From a musical point of view,
; this shouldn’t be much of a problem.)
((and aug
(eq? (ly:context-property context 'figuredBassPlusDirection)
RIGHT))
(case figure
((2) plusTwo)
((4) plusFour)
((5) plusFive)
(else (format-bass-figure figure event context))))
; This could be made optional.
((and (not (null? alt))
(eq? (ly:context-property context 'figuredBassAlterationDirection)
RIGHT))
(cond
((= alt FLAT)
(case figure
((2) dimTwo)
((4) dimFour)
((5) dimFive)
((6) dimSix)
(else (format-bass-figure figure event context))))
((= alt NATURAL)
(case figure
((2) natTwo)
((4) natFour)
((5) natFive)
((6) natSix)
(else (format-bass-figure figure event context))))
(else (format-bass-figure figure event context))))
; anything that is not explicitely being looked for
; will be handled by the default existing formatter.
(else (format-bass-figure figure event context)))))

%% Inclusion of the new formatter:

\layout {
\context {
\Score
figuredBassFormatter = #vv-format-bass-figure
}
}

%% A simple example:

\figures {
<6\\> <9\\>
% Modified glyphs are used only when
% plus signs are printed on the right.
\set figuredBassPlusDirection = #RIGHT
<2\+> <4\+> <5\+>
\set figuredBassAlterationDirection = #RIGHT
<2-> <4-> <5-> <6->
<2!> <4!> <5!> <6!>
}
</lilypond>

[[Category:Ancient notation]]
[[Category:Chords]]
[[Category:Ancient notation]]
[[Category:Workaround]]
[[Category:Symbols and glyphs]]
[[Category:Snippet]]

Colored arrows (2)

2026-07-09T04:54:32Z

Lemzwerg:

This snippet demonstrates drawing colored arrows in a score, e.g., for analysis purposes. These arrows adapt to layout changes, because they are made of spanners between (invisible) note heads. If you need arrows with a fixed length and angle, you might prefer the snippet [[Colored arrows]].

<lilypond version="2.24">
forwardArrow =
#(define-music-function (color) (color?)
#{
% Cross-staff arrows are made using the VoiceFollower. To have
% the arrow behind the staff, choose a value below 0 for the
% layer. If you want the arrows to cover the notes, choose a
% value of 2 or more.
\once \override VoiceFollower.layer = -5

\once \override VoiceFollower.thickness = 5 % line thickness
\once \override VoiceFollower.color = #color

% Padding can be adjusted to move arrow ends closer to the
% notes.
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2

\once \override VoiceFollower.bound-details.right.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
% ##f prevents line breaks within an arrow.
\once \override VoiceFollower.breakable = ##t

% Arrows within the same staff use the Glissando spanner, so
% we repeat setting the above properties for this grob.
\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.right.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

backwardArrow =
#(define-music-function (color) (color?)
#{
\once \override VoiceFollower.layer = -5
\once \override VoiceFollower.thickness = 5
\once \override VoiceFollower.color = #color
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2
\once \override VoiceFollower.bound-details.left.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
\once \override VoiceFollower.breakable = ##t

\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.left.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

\relative c' {
<<
% Usage: Place the arrow function call before the note, and the
% glissando statement after the note.
\new Staff = upper {
c4 d e \backwardArrow #blue c \glissando |
R1*5 |
c4 d e c |
e1 |
d1 |
c1 |
}
\new Staff = middle {
R1 |
c4 d e c |
e8 d e f g f e c |
d8 c d e f e f d |
c1 |
R1*5
}
\new Staff = lower <<
\new Voice {
\oneVoice
R1*2 |
c4 d e \forwardArrow #blue c\glissando |
R1 |
c4 d e c |
d4 c b2 |
R1*4
}
\new Voice {
\override NoteColumn.ignore-collision = ##t

% For cross-staff arrows we use an additional voice with
% hidden notes. To make these notes visible, uncomment the
% following lines
%
% \override NoteHead.color = #cyan
% \override NoteHead.layer = #2
%
% and remove the following "\hideNotes" line.
\hideNotes

\set Voice.followVoice = ##t
\change Staff = "upper" c4 s2. |
% Place the arrow function call immediately before the staff
% change.
\backwardArrow #green \change Staff = middle c4 s2. |
\forwardArrow #red \change Staff = lower c4 s2. |
s1 |
c4 s2. | \break
s1 |
\forwardArrow #red \change Staff = upper c4 s2. |
}
>>
>>
}
</lilypond>

[[Category:Connecting notes]]
[[Category:Editorial annotations]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

LSR 1029

2026-07-09T04:50:13Z

Lemzwerg: Changed redirect target from Easily enter music expressions in markup to Easily enter music expressions in markup (obsolete in 2.23)

#REDIRECT [[Easily enter music expressions in markup (obsolete in 2.23)]]

LSR 835

2026-07-09T04:48:51Z

Lemzwerg: Changed redirect target from Compound time signatures to Complex time signatures

#REDIRECT [[Complex time signatures]]

LSR 961

2026-07-09T04:46:56Z

Lemzwerg: Changed redirect target from Colored arrow to Colored arrows

#REDIRECT [[Colored arrows]]

LSR 962

2026-07-09T04:46:18Z

Lemzwerg: Changed redirect target from Colored arrows (alternative method) to Colored arrows (2)

#REDIRECT [[Colored arrows (2)]]

Colored arrows

2026-07-09T04:45:59Z

Lemzwerg: Lemzwerg moved page Colored arrow to Colored arrows without leaving a redirect

This snippet demonstrates drawing colored arrows in a score, e.g., for analysis purposes. These arrows have a fixed length and angle. If you prefer arrows that adapt to layout changes, check snippet [[Colored arrows (2)]].

<lilypond version="2.24">
#(define-markup-command (Arrow layout props color angle length moveX moveY)
(color? number? number? number? number?)
(interpret-markup layout props
#{
\markup {
\with-dimensions #'(0 . 0) #'(0 . 0)
\translate #(cons moveX moveY)
\rotate #angle
\override #'(thickness . 5) % line thickness
\fontsize #10 % arrow-head size
\with-dimensions #'(0 . 0) #'(0 . 0)
\with-color $color
\translate #(cons 0 (- 0 length))
\combine
\draw-line #(cons 0 length) % can be replaced by \draw-dashed-line or \draw-dotted-line
\translate-scaled #'(0 . -0.5) % might have to be adjusted if line thickness is changed
\with-color $color
\arrow-head #Y #DOWN ##t % ##t - filled arrow-head, ##f - empty arrow-head
}
#}))

{<<
\new Staff {R1*3}
\new Staff {
e'1-\tweak layer #-1 -\markup {\Arrow #green #138 #16 #2 #2 }
e'1-\tweak layer #-1 -\markup {\Arrow #cyan #255 #14 #-1 #2 }
e'1-\tweak layer #2 -\markup {\Arrow #red #172 #11 #1 #2 }
% To have the arrow behind the staff, choose a value below 0 for the layer.
% If you want the arrows to cover the notes, choose a value of 2 or more.
}
>>}
</lilypond>

[[Category:Education]]
[[Category:Editorial annotations]]
[[Category:Tweaks and overrides]]
[[Category:Specific notation]]
[[Category:Syntax and expressions]]
[[Category:Snippet]]

Colored arrows

2026-07-09T04:45:45Z

Lemzwerg:

Colored arrows (2)

2026-07-09T04:44:34Z

Lemzwerg:

This snippet demonstrates drawing colored arrows in a score, e.g., for analysis purposes. These arrows adapt to layout changes, because they are made of spanners between (invisible) note heads. If you need arrows with a fixed length and angle, you might prefer the snippet [[Colored arrows]].

<lilypond version="2.24">
forwardArrow =
#(define-music-function (color) (color?)
#{
% Cross-staff arrows are made using the VoiceFollower. To have
% the arrow behind the staff, choose a value below 0 for the
% layer. If you want the arrows to cover the notes, choose a
% value of 2 or more.
\once \override VoiceFollower.layer = -5

\once \override VoiceFollower.thickness = 5 % line thickness
\once \override VoiceFollower.color = #color

% Padding can be adjusted to move arrow ends closer to the
% notes.
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2

\once \override VoiceFollower.bound-details.right.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
% ##f prevents line breaks within an arrow.
\once \override VoiceFollower.breakable = ##t

% Arrows within the same staff use the Glissando spanner, so
% we repeat setting the above properties for this grob.
\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.right.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

backwardArrow =
#(define-music-function (color) (color?)
#{
\once \override VoiceFollower.layer = -5
\once \override VoiceFollower.thickness = 5
\once \override VoiceFollower.color = #color
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2
\once \override VoiceFollower.bound-details.left.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
\once \override VoiceFollower.breakable = ##t

\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.left.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

\relative c' {
<<
% Usage: Place the arrow function call before the note, and the
% glissando statement after the note.
\new Staff = upper {
c4 d e \backwardArrow #blue c \glissando |
R1*5 |
c4 d e c |
e1 |
d1 |
c1 |
}
\new Staff = middle {
R1 |
c4 d e c |
e8 d e f g f e c |
d8 c d e f e f d |
c1 |
R1*5
}
\new Staff = lower <<
\new Voice {
\oneVoice
R1*2 |
c4 d e \forwardArrow #blue c\glissando |
R1 |
c4 d e c |
d4 c b2 |
R1*4
}
\new Voice {
\override NoteColumn.ignore-collision = ##t

% For cross-staff arrows we use an additional voice with
% hidden notes. To make these notes visible, uncomment the
% following lines
%
% \override NoteHead.color = #cyan
% \override NoteHead.layer = #2
%
% and remove the following "\hideNotes" line.
\hideNotes

\set Voice.followVoice = ##t
\change Staff = "upper" c4 s2. |
% Place the arrow function call immediately before the staff
% change.
\backwardArrow #green \change Staff = middle c4 s2. |
\forwardArrow #red \change Staff = lower c4 s2. |
s1 |
c4 s2. | \break
s1 |
\forwardArrow #red \change Staff = upper c4 s2. |
}
>>
>>
}
</lilypond>

[[Category:Editorial annotations]]
[[Category:Breaks]]
[[Category:Paper and layout]]
[[Category:Tweaks and overrides]]
[[Category:Connecting notes]]
[[Category:Specific notation]]
[[Category:Snippet]]

Colored arrows (2)

2026-07-09T04:44:03Z

Lemzwerg: Lemzwerg moved page Colored arrow (2) to Colored arrows (2) without leaving a redirect

This snippet demonstrates drawing colored arrows in a score, e.g., for analysis purposes. These arrows adapt to layout changes, because they are made of spanners between (invisible) note heads. If you need arrows with a fixed length and angle, you might prefer the snippet [[Colored arrow]].

<lilypond version="2.24">
forwardArrow =
#(define-music-function (color) (color?)
#{
% Cross-staff arrows are made using the VoiceFollower. To have
% the arrow behind the staff, choose a value below 0 for the
% layer. If you want the arrows to cover the notes, choose a
% value of 2 or more.
\once \override VoiceFollower.layer = -5

\once \override VoiceFollower.thickness = 5 % line thickness
\once \override VoiceFollower.color = #color

% Padding can be adjusted to move arrow ends closer to the
% notes.
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2

\once \override VoiceFollower.bound-details.right.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
% ##f prevents line breaks within an arrow.
\once \override VoiceFollower.breakable = ##t

% Arrows within the same staff use the Glissando spanner, so
% we repeat setting the above properties for this grob.
\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.right.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

backwardArrow =
#(define-music-function (color) (color?)
#{
\once \override VoiceFollower.layer = -5
\once \override VoiceFollower.thickness = 5
\once \override VoiceFollower.color = #color
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2
\once \override VoiceFollower.bound-details.left.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
\once \override VoiceFollower.breakable = ##t

\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.left.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

\relative c' {
<<
% Usage: Place the arrow function call before the note, and the
% glissando statement after the note.
\new Staff = upper {
c4 d e \backwardArrow #blue c \glissando |
R1*5 |
c4 d e c |
e1 |
d1 |
c1 |
}
\new Staff = middle {
R1 |
c4 d e c |
e8 d e f g f e c |
d8 c d e f e f d |
c1 |
R1*5
}
\new Staff = lower <<
\new Voice {
\oneVoice
R1*2 |
c4 d e \forwardArrow #blue c\glissando |
R1 |
c4 d e c |
d4 c b2 |
R1*4
}
\new Voice {
\override NoteColumn.ignore-collision = ##t

% For cross-staff arrows we use an additional voice with
% hidden notes. To make these notes visible, uncomment the
% following lines
%
% \override NoteHead.color = #cyan
% \override NoteHead.layer = #2
%
% and remove the following "\hideNotes" line.
\hideNotes

\set Voice.followVoice = ##t
\change Staff = "upper" c4 s2. |
% Place the arrow function call immediately before the staff
% change.
\backwardArrow #green \change Staff = middle c4 s2. |
\forwardArrow #red \change Staff = lower c4 s2. |
s1 |
c4 s2. | \break
s1 |
\forwardArrow #red \change Staff = upper c4 s2. |
}
>>
>>
}
</lilypond>

[[Category:Editorial annotations]]
[[Category:Breaks]]
[[Category:Paper and layout]]
[[Category:Tweaks and overrides]]
[[Category:Connecting notes]]
[[Category:Specific notation]]
[[Category:Snippet]]

Colored arrows (2)

2026-07-09T04:42:57Z

Lemzwerg: Fix and improve.

This snippet demonstrates drawing colored arrows in a score, e.g., for analysis purposes. These arrows adapt to layout changes, because they are made of spanners between (invisible) note heads. If you need arrows with a fixed length and angle, you might prefer the snippet [[Colored arrow]].

<lilypond version="2.24">
forwardArrow =
#(define-music-function (color) (color?)
#{
% Cross-staff arrows are made using the VoiceFollower. To have
% the arrow behind the staff, choose a value below 0 for the
% layer. If you want the arrows to cover the notes, choose a
% value of 2 or more.
\once \override VoiceFollower.layer = -5

\once \override VoiceFollower.thickness = 5 % line thickness
\once \override VoiceFollower.color = #color

% Padding can be adjusted to move arrow ends closer to the
% notes.
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2

\once \override VoiceFollower.bound-details.right.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
% ##f prevents line breaks within an arrow.
\once \override VoiceFollower.breakable = ##t

% Arrows within the same staff use the Glissando spanner, so
% we repeat setting the above properties for this grob.
\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.right.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

backwardArrow =
#(define-music-function (color) (color?)
#{
\once \override VoiceFollower.layer = -5
\once \override VoiceFollower.thickness = 5
\once \override VoiceFollower.color = #color
\once \override VoiceFollower.bound-details.left.padding = 2
\once \override VoiceFollower.bound-details.right.padding = 2
\once \override VoiceFollower.bound-details.left.arrow = ##t
\once \override VoiceFollower.arrow-width = 1
\once \override VoiceFollower.arrow-length = 2
\once \override VoiceFollower.breakable = ##t

\once \override Glissando.layer = -5
\once \override Glissando.thickness = 5
\once \override Glissando.color = #color
\once \override Glissando.bound-details.left.padding = 2
\once \override Glissando.bound-details.right.padding = 2
\once \override Glissando.bound-details.left.arrow = ##t
\once \override Glissando.arrow-width = 1
\once \override Glissando.arrow-length = 2
\once \override Glissando.breakable = ##t
#})

\relative c' {
<<
% Usage: Place the arrow function call before the note, and the
% glissando statement after the note.
\new Staff = upper {
c4 d e \backwardArrow #blue c \glissando |
R1*5 |
c4 d e c |
e1 |
d1 |
c1 |
}
\new Staff = middle {
R1 |
c4 d e c |
e8 d e f g f e c |
d8 c d e f e f d |
c1 |
R1*5
}
\new Staff = lower <<
\new Voice {
\oneVoice
R1*2 |
c4 d e \forwardArrow #blue c\glissando |
R1 |
c4 d e c |
d4 c b2 |
R1*4
}
\new Voice {
\override NoteColumn.ignore-collision = ##t

% For cross-staff arrows we use an additional voice with
% hidden notes. To make these notes visible, uncomment the
% following lines
%
% \override NoteHead.color = #cyan
% \override NoteHead.layer = #2
%
% and remove the following "\hideNotes" line.
\hideNotes

\set Voice.followVoice = ##t
\change Staff = "upper" c4 s2. |
% Place the arrow function call immediately before the staff
% change.
\backwardArrow #green \change Staff = middle c4 s2. |
\forwardArrow #red \change Staff = lower c4 s2. |
s1 |
c4 s2. | \break
s1 |
\forwardArrow #red \change Staff = upper c4 s2. |
}
>>
>>
}
</lilypond>

[[Category:Editorial annotations]]
[[Category:Breaks]]
[[Category:Paper and layout]]
[[Category:Tweaks and overrides]]
[[Category:Connecting notes]]
[[Category:Specific notation]]
[[Category:Snippet]]

Horizontally aligning stanza numbers of different staves

2026-06-26T15:39:11Z

Lemzwerg:

It can happen that stanza numbers don’t align horizontally if the verses are attached to different staves. To fix that, override the <code>self-alignment-X</code> property of the <code>LyricText</code> grob.

<lilypond version="2.24">
\markup { default behavior }

<<
\new Staff { b b b b }
\lyrics {
\set stanza = "3."
a a a a
}

\new Staff { b b b b }
\lyrics {
\set stanza = "1."
aaaaaaaaaa a a a
}
\lyrics {
\set stanza = "2."
a a a a
}
>>

\markup \vspace #1
\markup {
using \typewriter "self-alignment-X = #LEFT" }

<<
\new Staff { b b b b }
\new Lyrics \lyricmode {
\set stanza = "3."
a a a a
}

\new Staff { b b b b }
\new Lyrics \lyricmode {
\set stanza = "1."
\once \override LyricText.self-alignment-X = #LEFT
aaaaaaaaaa a a a
}
\new Lyrics \lyricmode {
\set stanza = "2."
a a a a
}
>>
</lilypond>

[[Category:Tweaks and overrides]]
[[Category:Vocal music]]
[[Category:Included in the official documentation]]
[[Category:Snippet]]

LSR 1193

2026-06-26T15:37:38Z

Lemzwerg: Changed redirect target from Vertically aligning stanza numbers of different staves to Horizontally aligning stanza numbers of different staves

#REDIRECT [[Horizontally aligning stanza numbers of different staves]]

Horizontally aligning stanza numbers of different staves

2026-06-26T15:36:53Z

Lemzwerg: Lemzwerg moved page Vertically aligning stanza numbers of different staves to Horizontally aligning stanza numbers of different staves without leaving a redirect

It can happen that stanza numbers don't align vertically if the verses are attached to different staves. To fix that, override the <code>self-alignment-X</code> property of the <code>LyricText</code> grob.

<lilypond version="2.24">
\markup { default behavior }

<<
\new Staff { b b b b }
\lyrics {
\set stanza = "3."
a a a a
}

\new Staff { b b b b }
\lyrics {
\set stanza = "1."
aaaaaaaaaa a a a
}
\lyrics {
\set stanza = "2."
a a a a
}
>>

\markup \vspace #1
\markup {
using \typewriter "self-alignment-X = #LEFT" }

<<
\new Staff { b b b b }
\new Lyrics \lyricmode {
\set stanza = "3."
a a a a
}

\new Staff { b b b b }
\new Lyrics \lyricmode {
\set stanza = "1."
\once \override LyricText.self-alignment-X = #LEFT
aaaaaaaaaa a a a
}
\new Lyrics \lyricmode {
\set stanza = "2."
a a a a
}
>>
</lilypond>

[[Category:Tweaks and overrides]]
[[Category:Vocal music]]
[[Category:Included in the official documentation]]
[[Category:Snippet]]

Talk:SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines

2026-05-25T19:54:54Z

Lemzwerg: /* Title Change */ Reply

== Title Change ==

I believe that “non-” in the current page title is a typo; the title should instead read “… with SpanBars for special bar lines.” @[[User:Lemzwerg|Lemzwerg]] [[User:Gabriel Ellsworth|Gabriel Ellsworth]] ([[User talk:Gabriel Ellsworth|talk]]) 18:39, 25 May 2026 (UTC)

:Agreed – and moved -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 19:54, 25 May 2026 (UTC)

LSR 299

2026-05-25T19:54:24Z

Lemzwerg: Changed redirect target from SemiChoirStaff is a ChoirStaff with SpanBars for non-special bar lines to SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines

#REDIRECT [[SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines]]

Talk:SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines

2026-05-25T19:54:04Z

Lemzwerg: Lemzwerg moved page Talk:SemiChoirStaff is a ChoirStaff with SpanBars for non-special bar lines to Talk:SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines without leaving a redirect

SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines

2026-05-25T19:54:04Z

Lemzwerg: Lemzwerg moved page SemiChoirStaff is a ChoirStaff with SpanBars for non-special bar lines to SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines without leaving a redirect

If you wish to typeset <code>|.</code> and friends as connected in a <code>ChoirStaff</code> while ordinary bar lines stay unconnected, you can add the <code>Span_bar_engraver</code> and instruct it to omit the <code>|</code>-style bars.

In this example a new context, <code>SemiChoirStaff</code>, is created to achieve this.

<lilypond version="2.24">
mus = {
\clef F
c4 d e f | c d e f \bar "||"
c4 d e f | c d e f \bar "|."
}

\layout {
\context {
\ChoirStaff
\name "SemiChoirStaff"
\consists "Span_bar_engraver"
\override SpanBar.stencil =
#(lambda (grob)
(if (string=? (ly:grob-property grob 'glyph-name) "|")
(set! (ly:grob-property grob 'glyph-name) ""))
(ly:span-bar::print grob))
}
\context {
\Score
\accepts SemiChoirStaff
}
}

\score {
\new SemiChoirStaff {
<<
\new Staff \mus
\new Staff \mus
>>
}
}
</lilypond>

[[Category:Contexts and engravers]]
[[Category:Scheme]]
[[Category:Workaround]]
[[Category:Snippet]]

Magnetic lyrics: snap syllables together if the hyphen inbetween is too short

2026-05-19T05:11:08Z

Lemzwerg: Make it an official snippet

The current code that LilyPond uses to handle lyric hyphens (i.e., <code>LyricHyphen</code> grobs) often leads to very short hyphens or even small gaps between syllables with no hyphen visible. This snippet merges adjacent syllables into one string in such cases, also taking care of ligatures as if the string was not hyphenated.

It supersedes previous implementations of “magnetic snap” engravers that were in circulation via the lilypond-user mailing list.

<lilypond version="2.24">
% magnetic-lyrics.ily
%
% written by
% Jean Abou Samra <jean@abou-samra.fr>
% Werner Lemberg <wl@gnu.org>

#(define (Left_hyphen_pointer_engraver context)
"Collect syllable-hyphen-syllable occurrences in lyrics and store
them in properties. This engraver only looks to the left. For
example, if the lyrics input is 'foo -- bar', it does the
following.

* Set the `text` property of the `LyricHyphen` grob between 'foo' and
'bar' to 'foo'.

* Set the `left-hyphen` property of the `LyricText` grob with text
'foo' to the `LyricHyphen` grob between 'foo' and 'bar'.

Use this auxiliary engraver in combination with the
`lyric-text::apply-magnetic-offset!` hook."
(let ((hyphen #f)
(text #f))
(make-engraver
(acknowledgers
((lyric-syllable-interface engraver grob source-engraver)
(set! text grob)))
(end-acknowledgers
((lyric-hyphen-interface engraver grob source-engraver)
(when (not (grob::has-interface grob 'lyric-space-interface))
(set! hyphen grob))))
((stop-translation-timestep engraver)
(when (and text hyphen)
(ly:grob-set-object! text 'left-hyphen hyphen))
(set! text #f)
(set! hyphen #f)))))

#(define (lyric-text::apply-magnetic-offset! grob)
"If the space between two syllables is less than the value in
property `LyricText.details.squash-threshold`, move the right syllable
to the left so that it gets concatenated with the left syllable.

Use this function as a hook for `LyricText.after-line-breaking` if the
`Left_hyphen_pointer_engraver} is active."
(let ((hyphen (ly:grob-object grob 'left-hyphen #f)))
(when hyphen
(let ((left-text (ly:spanner-bound hyphen LEFT)))
(when (grob::has-interface left-text 'lyric-syllable-interface)
(let* ((common (ly:grob-common-refpoint grob left-text X))
(this-x-ext (ly:grob-extent grob common X))
(left-x-ext
(begin
;; Trigger magnetism for left-text.
(ly:grob-property left-text 'after-line-breaking)
(ly:grob-extent left-text common X)))
;; `delta` is the gap width between two syllables.
(delta (- (interval-start this-x-ext)
(interval-end left-x-ext)))
(details (ly:grob-property grob 'details))
(threshold (assoc-get 'squash-threshold details 0.2)))
(when (< delta threshold)
(let* (;; We have to manipulate the input text so that
;; ligatures crossing syllable boundaries are not
;; disabled. For languages based on the Latin
;; script this is essentially a beautification.
;; However, for non-Western scripts it can be a
;; necessity.
(lt (ly:grob-property left-text 'text))
(rt (ly:grob-property grob 'text))
;; Append new syllable.
(ltrt (if (and (string? lt) (string? rt))
(string-append lt rt)
(make-concat-markup (list lt rt))))
;; Right-align `ltrt` to the right side.
(markup (grob-interpret-markup
grob
(make-translate-markup
(cons (interval-length this-x-ext) 0)
(make-right-align-markup ltrt)))))
;; Don't print `left-text`.
(ly:grob-set-property! left-text 'stencil #f)
;; Set text and stencil (which holds all collected
;; syllables so far) and shift it to the left.
(ly:grob-set-property! grob 'text ltrt)
(ly:grob-set-property! grob 'stencil markup)
(ly:grob-translate-axis! grob (- delta) X)))))))))

#(define (lyric-hyphen::displace-bounds-first grob)
;; Make very sure this callback isn't triggered too early.
(let ((left (ly:spanner-bound grob LEFT))
(right (ly:spanner-bound grob RIGHT)))
(ly:grob-property left 'after-line-breaking)
(ly:grob-property right 'after-line-breaking)
(ly:lyric-hyphen::print grob)))

%% demonstration

music = {
<<
{ d'4 4 4 4 |
r4 4 4 4 }
\addlyrics { suf -- fice baff -- ling
car -- fuff -- ling }
>>
}

\markup "Without magnetic lyrics:"

\score {
\music
}

\markup "With magnetic lyrics:"

\score {
\music

\layout {
\context {
\Lyrics
\consists #Left_hyphen_pointer_engraver
\override LyricText.after-line-breaking =
#lyric-text::apply-magnetic-offset!
\override LyricHyphen.stencil =
#lyric-hyphen::displace-bounds-first
\override LyricText.details.squash-threshold = 0.4
\override LyricHyphen.minimum-distance = 0
\override LyricHyphen.minimum-length = 0.4
\override LyricSpace.minimum-distance = 1
}
}
}

\paper {
line-width = 83\mm
ragged-last = ##f
}
</lilypond>

[[Category:Vocal music]]
[[Category:Spacing]]
[[Category:Included in the official documentation]]
[[Category:Snippet]]

Magnetic lyrics: snap syllables together if the hyphen inbetween is too short

2026-05-19T05:07:31Z

Lemzwerg: Don't use Texinfo markup in documentation strings

User talk:Ksnortum

2026-05-18T04:40:52Z

Lemzwerg: /* Templates for convert-ly */

== Please be careful while using 'Edit' ==

Hello Knute! There is currently a bug in the 'Edit' mode: If you only change some details in the description (i.e., not touching the LilyPond code), the <code><lilypond></code> block gets ‘destroyed’ and is no longer rendered as an image. Please use 'Edit source' instead for the time being to avoid that. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:26, 8 April 2026 (UTC)

:Got it, thanks. [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 19:34, 8 April 2026 (UTC)
:...and thanks for cleaning up the mess! [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 14:58, 10 April 2026 (UTC)
::You're welcome! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:44, 10 April 2026 (UTC)

== Templates for convert-ly ==

I noticed that there are templates for convert-ly-stable (pointing to 2.24) and convery-ly-devel (pointing to 2.25). Should these be changed to 2.26 and 2.27 respectively? The template for convert-ly-devel is only used in a handful of places and convert-ly-stable doesn't look like it's used at all. --[[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 19:05, 17 May 2026 (UTC)

: In the long run, yes. I suggest we wait for 2.26.1, then the transition to 2.26 could start in the Wiki for all snippets. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:40, 18 May 2026 (UTC)

Time signature with alternate in parentheses

2026-04-15T04:35:44Z

Lemzwerg: Aaand another improvement.

In polymetric music, a composer may indicate beat structure by following one time signature with another in parenthesis, for example, ‘3/4 (6/8)’ indicating a 6/8 beat in a 3/4 measure, or ‘6/4 (6/8)’ indicating a 6/8 beat in a 6/4 measure.

This snippet provides a music function <code>\timeP</code> that is a small Scheme wrapper around the <code>\compound-meter</code> markup function. It overrides the <code>TimeSignature</code> stencil once to display both a regular and an alternate time signature.

<lilypond version="2.24">
timeP =
#(define-music-function (t tp) (list? list?)
(define ((time-parenthesized-time t tp) grob)
(let ((m1 (grob-interpret-markup
grob (markup #:compound-meter t)))
(m2 (grob-interpret-markup
grob (markup #:compound-meter tp))))
(ly:stencil-combine-at-edge
m1 X RIGHT
(parenthesize-stencil m2 0.1 0.4 0.4 0.1)
0.3)))
#{
\once \override Timing.TimeSignature.stencil =
#(time-parenthesized-time t tp)
#})

\relative c' {
\timeP #'(3 4) #'(6 8) \time 3/4
b8 b8 gis8 gis4 gis8 |
\timeP #'(4 4) #'(3 2 3 8) \time 4/4
b4. b4 b4.
}
</lilypond>

[[Category:Rhythms]]
[[Category:Scheme]]
[[Category:Snippet]]

Time signature with alternate in parentheses

2026-04-15T04:10:29Z

Lemzwerg: Improve more.

In polymetric music, a composer may indicate beat structure by following one time signature with another in parenthesis, for example, ‘3/4 (6/8)’ indicating a 6/8 beat in a 3/4 measure, or ‘6/4 (6/8)’ indicating a 6/8 beat in a 6/4 measure.

This snippet provides a small Scheme wrapper around the <code>\compound-meter</code> markup function that can be used to override the <code>TimeSignature</code> stencil, displaying both a regular and an alternate time signature.

<lilypond version="2.24">
#(define ((time-parenthesized-time t tp) grob)
(let ((m1 (grob-interpret-markup
grob (markup #:compound-meter t)))
(m2 (grob-interpret-markup
grob (markup #:compound-meter tp))))
(ly:stencil-combine-at-edge
m1 X RIGHT
(parenthesize-stencil m2 0.1 0.4 0.4 0.1)
0.3)))

\relative c' {
\once \override Staff.TimeSignature.stencil =
#(time-parenthesized-time '(3 4) '(6 8))
\time 3/4 b8 b8 gis8 gis4 gis8 |
\once \override Staff.TimeSignature.stencil =
#(time-parenthesized-time '(4 4) '(3 2 3 8))
\time 4/4 b4. b4 b4.
}
</lilypond>

[[Category:Rhythms]]
[[Category:Scheme]]
[[Category:Snippet]]

Time signature with alternate in parentheses

2026-04-14T20:42:54Z

Lemzwerg: Improved

In polymetric music, a composer may indicate beat structure by following one time signature with another in parenthesis, for example: 3/4 (6/8) indicating a 6/8 beat in a 3/4 measure, or 6/4 (6/8) indicating a 6/8 beat in a 6/4 measure.

This snippet uses a small Scheme function that overrides the <code>TimeSignature</code> stencil once to display both the regular and the alternate time signature.

<lilypond version="2.24">
#(define ((time-parenthesized-time up down upp downp) grob)
(let ((m1 (grob-interpret-markup
grob
(markup #:override '(baseline-skip . 0)
#:number (#:center-column
((number->string up)
(number->string down))))))
(m2 (grob-interpret-markup
grob
(markup #:override '(baseline-skip . 0)
#:number (#:center-column
((number->string upp)
(number->string downp)))))))
(ly:stencil-combine-at-edge
m1 X RIGHT
(parenthesize-stencil m2 0.1 0.4 0.4 0.1)
0.3)))

\relative c' {
\once \override Staff.TimeSignature.stencil =
#(time-parenthesized-time 3 4 6 8)
\time 3/4 b8 b8 gis8 gis4 gis8 |
\time 4/4 b4 b b b
}
</lilypond>

[[Category:Rhythms]]
[[Category:Scheme]]
[[Category:Snippet]]

User talk:Ksnortum

2026-04-10T15:44:01Z

Lemzwerg: /* Please be careful while using 'Edit' */ Reply

Clef change at the beginning of a piece (alternative)

2026-04-08T17:29:32Z

Lemzwerg:

When changing the clef at the beginning of the first measure, Lilypond just changes the clef for the staff. This is how to keep the staff clef and add an extra clef after the time signature and before the first note. See also [[Initial clef change]] and [[Clef change at the beginning of a piece]].

<lilypond version="2.24">
\relative c' {
%% Start with a bass clef :
\clef bass
%% Use a hidden grace note:
\once\hideNotes\grace c64
%% Adjust the clef spacing:
\once\override Staff.Clef.X-extent = #'(1 . 2)
%% Put in the treble clef:
\clef treble
c4 c c c | c1
}
</lilypond>

[[Category:Staff notation]]
[[Category:Pitches]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

Clef change at the beginning of a piece (alternative)

2026-04-08T17:29:02Z

Lemzwerg: Reverted edit by Ksnortum (talk) to last revision by Jean Abou Samra

When changing the clef at the beginning of the first measure, Lilypond just changes the clef for the staff. This is how to keep the staff clef and add an extra clef after the time signature and before the first note.

<lilypond version="2.24">
\relative c' {
%% Start with a bass clef :
\clef bass
%% Use a hidden grace note:
\once\hideNotes\grace c64
%% Adjust the clef spacing:
\once\override Staff.Clef.X-extent = #'(1 . 2)
%% Put in the treble clef:
\clef treble
c4 c c c | c1
}
</lilypond>

[[Category:Staff notation]]
[[Category:Pitches]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

Clef change at the beginning of a piece

2026-04-08T17:28:29Z

Lemzwerg:

When changing the clef at the beginning of the first measure, Lilypond just changes the clef for the staff. This is how to keep the staff clef and add an extra clef after the time signature and before the first note. See also [[Clef change at the beginning of a piece (alternative)]] and [[Initial clef change]].

<lilypond version="2.24">
%% http://lsr.di.unimi.it/LSR/Item?id=792
%% see also http://lilypond.org/doc/stable/Documentation/notation/displaying-pitches

% Append markup in the text property to the grob
#(define (append-markup grob old-stencil)
(ly:stencil-combine-at-edge
old-stencil X RIGHT (ly:text-interface::print grob)))

trebleToBass = {
\clef bass
% Fake staff clef appearance
\once \override Staff.Clef.glyph-name = #"clefs.G"
\once \override Staff.Clef.Y-offset = #-1
% Make sure any key signatures will printed with respect to
% correct middle c position expected for treble clef
\once \set Staff.middleCClefPosition = -6
% Append change clef to the time signature
\once \override Staff.TimeSignature.text = \markup {
\hspace #1.2
\raise #1
\musicglyph "clefs.F_change"
}
\once \override Staff.TimeSignature.stencil = #(lambda (grob)
(append-markup grob (ly:time-signature::print grob)))
}

bassToTreble = {
\clef treble
% Fake staff clef appearance
\once \override Staff.Clef.glyph-name = #"clefs.F"
\once \override Staff.Clef.Y-offset = #1
% Make sure any key signatures will printed with respect to
% correct middle c position expected for bass clef
\once \set Staff.middleCClefPosition = 6
% Append change clef to the time signature
\once \override Staff.TimeSignature.text = \markup {
\hspace #1.2
\lower #1
\musicglyph "clefs.G_change"
}
\once \override Staff.TimeSignature.stencil = #(lambda (grob)
(append-markup grob (ly:time-signature::print grob)))
}

\relative c {
\trebleToBass
\key f \major
c4 d e f
% This should not be visible
\clef bass
g a b c
% This should be visible
\clef treble
d e f g
}
</lilypond>

[[Category:Staff notation]]
[[Category:Staff notation]]
[[Category:Pitches]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

Clef change at the beginning of a piece

2026-04-08T17:27:58Z

Lemzwerg: Reverted edit by Ksnortum (talk) to last revision by Lemzwerg

When changing the clef at the beginning of the first measure, Lilypond just changes the clef for the staff. This is how to keep the staff clef and add an extra clef after the time signature and before the first note.

<lilypond version="2.24">
%% http://lsr.di.unimi.it/LSR/Item?id=792
%% see also http://lilypond.org/doc/stable/Documentation/notation/displaying-pitches

% Append markup in the text property to the grob
#(define (append-markup grob old-stencil)
(ly:stencil-combine-at-edge
old-stencil X RIGHT (ly:text-interface::print grob)))

trebleToBass = {
\clef bass
% Fake staff clef appearance
\once \override Staff.Clef.glyph-name = #"clefs.G"
\once \override Staff.Clef.Y-offset = #-1
% Make sure any key signatures will printed with respect to
% correct middle c position expected for treble clef
\once \set Staff.middleCClefPosition = -6
% Append change clef to the time signature
\once \override Staff.TimeSignature.text = \markup {
\hspace #1.2
\raise #1
\musicglyph "clefs.F_change"
}
\once \override Staff.TimeSignature.stencil = #(lambda (grob)
(append-markup grob (ly:time-signature::print grob)))
}

bassToTreble = {
\clef treble
% Fake staff clef appearance
\once \override Staff.Clef.glyph-name = #"clefs.F"
\once \override Staff.Clef.Y-offset = #1
% Make sure any key signatures will printed with respect to
% correct middle c position expected for bass clef
\once \set Staff.middleCClefPosition = 6
% Append change clef to the time signature
\once \override Staff.TimeSignature.text = \markup {
\hspace #1.2
\lower #1
\musicglyph "clefs.G_change"
}
\once \override Staff.TimeSignature.stencil = #(lambda (grob)
(append-markup grob (ly:time-signature::print grob)))
}

\relative c {
\trebleToBass
\key f \major
c4 d e f
% This should not be visible
\clef bass
g a b c
% This should be visible
\clef treble
d e f g
}
</lilypond>

[[Category:Staff notation]]
[[Category:Staff notation]]
[[Category:Pitches]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

User talk:Ksnortum

2026-04-08T17:26:25Z

Lemzwerg: /* Please be careful while using 'Edit' */ new section

Initial clef change

2026-04-08T17:22:41Z

Lemzwerg:

This snippet handles initial clef changes with a custom engraver. This engraver checks whether there is a difference between the initial clef (as given by <code>\with { \clef ... }</code> and the clef at the first timestep. If any difference is encountered a new clef (spaced like a cue clef) is created, while the original clef and any key signatures are modified to look like the initial clef values. See also the snippets [[Clef change at the beginning of a piece]] and [[Clef change at the beginning of a piece (alternative)]].

<lilypond version="2.24">
%%% This engraver records the initial clef properties (e.g. what is set by \with { \clef ... })
%%% If in the first timestep these changed, engrave the original clef, and change formatting and break
%%% alignment of the actual clef to mimic a clef change clef. Duplicates some procedure from clef engraver
%%% and could easily be integrated.
#(define (initial-clef-change-engraver context)
(let ((initial-clef-properties #f) (cclef #f) (keysigs '()))
; macro for checking if any clef property has changed
(define (clef-changed)
(>
(length initial-clef-properties)
(length
(filter
(lambda (x) (equal? (cdr x) (ly:context-property context (car x))))
initial-clef-properties))))
(make-engraver
; Record initials propertis
((initialize engraver)
(set!
initial-clef-properties
`((clefGlyph . ,(ly:context-property context 'clefGlyph))
(clefPosition . ,(ly:context-property context 'clefPosition))
(middleCClefPosition . ,(ly:context-property context 'middleCClefPosition))
(clefTransposition . ,(ly:context-property context 'clefTransposition)))))
; Record the actual clef to adjust. Use details.muted to not acknowledge clef created by this engraver.
(acknowledgers
((clef-interface engraver grob source-engraver)
(if (not (assoc-get 'muted (ly:grob-property grob 'details) #f))
(set! cclef grob)))
((key-signature-interface engraver grob source-engraver)
(set! keysigs (cons grob keysigs))))
; Create a clef if necessary
((process-music engraver)
(if (and initial-clef-properties (clef-changed))
(let ((clef (ly:engraver-make-grob engraver 'Clef '())))
(ly:grob-set-property! clef 'staff-position (assoc-get 'clefPosition initial-clef-properties))
(ly:grob-set-property! clef 'glyph (assoc-get 'clefGlyph initial-clef-properties))
(ly:grob-set-nested-property! clef '(details muted) #t)
(if ((lambda (x) (and (number? x) (not (= 0 x))))
(assoc-get 'clefTransposition initial-clef-properties 0))
(let ((mod (ly:engraver-make-grob engraver 'ClefModifier '()))
(formatter (ly:context-property context 'clefTranspositionFormatter))
(style (ly:context-property context 'clefTranspositionStyle))
(dir (sign (assoc-get 'clefTransposition initial-clef-properties 0)))
(abs_trans (1+ (abs (assoc-get 'clefTransposition initial-clef-properties 0)))))
(if (procedure? formatter)
(ly:grob-set-property! mod 'text (formatter (number->string abs_trans) style)))
(ly:grob-set-object! mod 'side-support-elements (ly:grob-list->grob-array (list clef)))
(ly:grob-set-parent! mod X clef)
(ly:grob-set-parent! mod Y clef)
(ly:grob-set-property! mod 'direction dir))))))
; Adjust the actual clef and key signatures
((process-acknowledged engraver)
(if (and cclef initial-clef-properties (clef-changed))
(begin

; Key signatures need to be handled if they appear before the cue-clef
; This requires the break alignment information, so this only sets a
; hook which will be processed during `before-line-breaking` of the
; BreakAlignGroups
(for-each
(lambda (keysig)
(let ((det (ly:grob-property keysig 'details))
(initial-clef-properties initial-clef-properties))
(ly:grob-set-property!
keysig
'details
(acons
'break-alignment-handler
(lambda (grob break-alignment)
(let ((start-of-line
(vector-ref
(ly:grob-property break-alignment 'break-align-orders)
2)))
(if (member 'cue-clef (or (member 'key-signature start-of-line) '()))
(ly:grob-set-property!
grob 'c0-position
(assoc-get 'middleCClefPosition initial-clef-properties)))))
det))))
keysigs)

(ly:grob-set-property! cclef 'non-default #t)
(ly:grob-set-property! cclef 'break-align-symbol 'cue-clef)
(if (not (eq? #t (ly:grob-property cclef 'full-size-change)))
(ly:grob-set-property! cclef 'glyph-name
(format #f "~a_change" (ly:grob-property cclef 'glyph)))))))
; Unset parameters
((stop-translation-timestep engraver)
(set! initial-clef-properties #f)
(set! clef #f)
(set! keysigs '())))))

\layout {
\context {
\Staff
\consists #initial-clef-change-engraver
}
\context {
\Score
\override BreakAlignGroup.before-line-breaking =
#(lambda (grob)
(let ((grobs (ly:grob-object grob 'elements))
(break-alignment (ly:grob-parent grob X)))
(if (not (null? grobs))
(set! grobs (ly:grob-array->list grobs)))
(for-each
(lambda (grob)
(let* ((det (ly:grob-property grob 'details))
(handler (assoc-get 'break-alignment-handler det)))
(if (procedure? handler)
(handler grob break-alignment))))
grobs)))
}
}

\new Staff \with { \clef "bass^15" } {
\key bes\major
\clef "treble_8"
c'1 c'1
\clef bass
c'1
}

\score {
\layout {
\context {
\Score
\override BreakAlignment.break-align-orders =
##((staff-ellipsis
left-edge
cue-end-clef
ambitus
breathing-sign
optional-material-end-bracket
signum-repetitionis
clef
cue-clef
staff-bar
key-cancellation
key-signature
time-signature
optional-material-start-bracket
custos)
(staff-ellipsis
left-edge
optional-material-end-bracket
cue-end-clef
ambitus
breathing-sign
signum-repetitionis
clef
cue-clef
staff-bar
key-cancellation
key-signature
time-signature
optional-material-start-bracket
custos)
(staff-ellipsis
left-edge
optional-material-end-bracket
ambitus
breathing-sign
signum-repetitionis
clef
cue-clef
key-cancellation
key-signature
time-signature
staff-bar
optional-material-start-bracket
custos))
}
}
\new Staff \with { \clef "bass^15" } {
\key bes\major
\clef "treble_8"
c'1 c'1
\clef bass
c'1
}
}

% Basic usage:
\score {
<<
% Just the treble clef
\new Staff {
\key bes \major
c''1
}

% Just the bass clef
\new Staff \with { \clef bass } {
\key bes \major
c1
}

% Initial treble clef, then bass clef
\new Staff {
\key bes \major
\clef bass
c1
}

% Initial bass clef, then treble clef
\new Staff \with { \clef bass } {
\key bes \major
\clef treble
c''1
}
>>

\layout {
\context {
\Staff
\consists #initial-clef-change-engraver
}
}
}
</lilypond>

[[Category:Contexts and engravers]]
[[Category:Scheme]]
[[Category:Staff notation]]
[[Category:Snippet]]

Initial clef change

2026-04-08T17:21:45Z

Lemzwerg: Reverted edit by Ksnortum (talk) to last revision by Lemzwerg

This snippet handles initial clef changes with a custom engraver. This engraver checks whether there is a difference between the initial clef (as given by <code>\with { \clef ... }</code> and the clef at the first timestep. If any difference is encountered a new clef (spaced like a cue clef) is created, while the original clef and any key signatures are modified to look like the initial clef values.

<lilypond version="2.24">
%%% This engraver records the initial clef properties (e.g. what is set by \with { \clef ... })
%%% If in the first timestep these changed, engrave the original clef, and change formatting and break
%%% alignment of the actual clef to mimic a clef change clef. Duplicates some procedure from clef engraver
%%% and could easily be integrated.
#(define (initial-clef-change-engraver context)
(let ((initial-clef-properties #f) (cclef #f) (keysigs '()))
; macro for checking if any clef property has changed
(define (clef-changed)
(>
(length initial-clef-properties)
(length
(filter
(lambda (x) (equal? (cdr x) (ly:context-property context (car x))))
initial-clef-properties))))
(make-engraver
; Record initials propertis
((initialize engraver)
(set!
initial-clef-properties
`((clefGlyph . ,(ly:context-property context 'clefGlyph))
(clefPosition . ,(ly:context-property context 'clefPosition))
(middleCClefPosition . ,(ly:context-property context 'middleCClefPosition))
(clefTransposition . ,(ly:context-property context 'clefTransposition)))))
; Record the actual clef to adjust. Use details.muted to not acknowledge clef created by this engraver.
(acknowledgers
((clef-interface engraver grob source-engraver)
(if (not (assoc-get 'muted (ly:grob-property grob 'details) #f))
(set! cclef grob)))
((key-signature-interface engraver grob source-engraver)
(set! keysigs (cons grob keysigs))))
; Create a clef if necessary
((process-music engraver)
(if (and initial-clef-properties (clef-changed))
(let ((clef (ly:engraver-make-grob engraver 'Clef '())))
(ly:grob-set-property! clef 'staff-position (assoc-get 'clefPosition initial-clef-properties))
(ly:grob-set-property! clef 'glyph (assoc-get 'clefGlyph initial-clef-properties))
(ly:grob-set-nested-property! clef '(details muted) #t)
(if ((lambda (x) (and (number? x) (not (= 0 x))))
(assoc-get 'clefTransposition initial-clef-properties 0))
(let ((mod (ly:engraver-make-grob engraver 'ClefModifier '()))
(formatter (ly:context-property context 'clefTranspositionFormatter))
(style (ly:context-property context 'clefTranspositionStyle))
(dir (sign (assoc-get 'clefTransposition initial-clef-properties 0)))
(abs_trans (1+ (abs (assoc-get 'clefTransposition initial-clef-properties 0)))))
(if (procedure? formatter)
(ly:grob-set-property! mod 'text (formatter (number->string abs_trans) style)))
(ly:grob-set-object! mod 'side-support-elements (ly:grob-list->grob-array (list clef)))
(ly:grob-set-parent! mod X clef)
(ly:grob-set-parent! mod Y clef)
(ly:grob-set-property! mod 'direction dir))))))
; Adjust the actual clef and key signatures
((process-acknowledged engraver)
(if (and cclef initial-clef-properties (clef-changed))
(begin

; Key signatures need to be handled if they appear before the cue-clef
; This requires the break alignment information, so this only sets a
; hook which will be processed during `before-line-breaking` of the
; BreakAlignGroups
(for-each
(lambda (keysig)
(let ((det (ly:grob-property keysig 'details))
(initial-clef-properties initial-clef-properties))
(ly:grob-set-property!
keysig
'details
(acons
'break-alignment-handler
(lambda (grob break-alignment)
(let ((start-of-line
(vector-ref
(ly:grob-property break-alignment 'break-align-orders)
2)))
(if (member 'cue-clef (or (member 'key-signature start-of-line) '()))
(ly:grob-set-property!
grob 'c0-position
(assoc-get 'middleCClefPosition initial-clef-properties)))))
det))))
keysigs)

(ly:grob-set-property! cclef 'non-default #t)
(ly:grob-set-property! cclef 'break-align-symbol 'cue-clef)
(if (not (eq? #t (ly:grob-property cclef 'full-size-change)))
(ly:grob-set-property! cclef 'glyph-name
(format #f "~a_change" (ly:grob-property cclef 'glyph)))))))
; Unset parameters
((stop-translation-timestep engraver)
(set! initial-clef-properties #f)
(set! clef #f)
(set! keysigs '())))))

\layout {
\context {
\Staff
\consists #initial-clef-change-engraver
}
\context {
\Score
\override BreakAlignGroup.before-line-breaking =
#(lambda (grob)
(let ((grobs (ly:grob-object grob 'elements))
(break-alignment (ly:grob-parent grob X)))
(if (not (null? grobs))
(set! grobs (ly:grob-array->list grobs)))
(for-each
(lambda (grob)
(let* ((det (ly:grob-property grob 'details))
(handler (assoc-get 'break-alignment-handler det)))
(if (procedure? handler)
(handler grob break-alignment))))
grobs)))
}
}

\new Staff \with { \clef "bass^15" } {
\key bes\major
\clef "treble_8"
c'1 c'1
\clef bass
c'1
}

\score {
\layout {
\context {
\Score
\override BreakAlignment.break-align-orders =
##((staff-ellipsis
left-edge
cue-end-clef
ambitus
breathing-sign
optional-material-end-bracket
signum-repetitionis
clef
cue-clef
staff-bar
key-cancellation
key-signature
time-signature
optional-material-start-bracket
custos)
(staff-ellipsis
left-edge
optional-material-end-bracket
cue-end-clef
ambitus
breathing-sign
signum-repetitionis
clef
cue-clef
staff-bar
key-cancellation
key-signature
time-signature
optional-material-start-bracket
custos)
(staff-ellipsis
left-edge
optional-material-end-bracket
ambitus
breathing-sign
signum-repetitionis
clef
cue-clef
key-cancellation
key-signature
time-signature
staff-bar
optional-material-start-bracket
custos))
}
}
\new Staff \with { \clef "bass^15" } {
\key bes\major
\clef "treble_8"
c'1 c'1
\clef bass
c'1
}
}

% Basic usage:
\score {
<<
% Just the treble clef
\new Staff {
\key bes \major
c''1
}

% Just the bass clef
\new Staff \with { \clef bass } {
\key bes \major
c1
}

% Initial treble clef, then bass clef
\new Staff {
\key bes \major
\clef bass
c1
}

% Initial bass clef, then treble clef
\new Staff \with { \clef bass } {
\key bes \major
\clef treble
c''1
}
>>

\layout {
\context {
\Staff
\consists #initial-clef-change-engraver
}
}
}
</lilypond>

[[Category:Contexts and engravers]]
[[Category:Scheme]]
[[Category:Staff notation]]
[[Category:Snippet]]

Splitting chords

2026-04-07T03:53:53Z

Lemzwerg:

This snippet is a 2009 contribution by Gilles Thibault in [https://lists.gnu.org/archive/html/lilypond-user/2009-01/msg00685.html lilypond-user]. It provides two functions to split a chord sequence into two separate voices, also preserving articulations and slurs: <code>\keepOnlyFirstNote</code> extracts the first note (as given in the input; this is usually the lowest one) of every chord, and <code>\deleteFirstNote</code> collects the remaining notes.

Note that these functions don't support <samp>q</samp> to repeat the last chord.

<lilypond version="2.24">
#(define (has-duration? music)
(ly:duration? (ly:music-property music 'duration)))

#(define (not-has-duration? music)
(not (has-duration? music)))

keepOnlyFirstNote =
#(define-music-function (parser location music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property!
evt 'elements
(cons (car elts)
(filter not-has-duration? (cdr elts)))))))
evt)
music))

deleteFirstNote =
#(define-music-function (parser location music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property! evt 'elements (cdr elts)))))
evt)
music))

music = \relative c' {
<c e>4-> <d f>( <b g'>) <c e>-. g2 c2
}

\markup { Music with chords }
\new Staff \music

\markup { Music split into two staves }
<<
\new Staff \deleteFirstNote \music
\new Staff \keepOnlyFirstNote \music
>>
</lilypond>

[[category:Chords]]
[[category:Scheme]]
[[category:Really cool]]

Splitting chords

2026-04-07T03:51:40Z

Lemzwerg: Not sure how it could happen that changing a single letter in the docstring completely ruined the rendering...

This snippet is a 2009 contribution by Gilles Thibault in [https://lists.gnu.org/archive/html/lilypond-user/2009-01/msg00685.html lilypond-user]. It provides two functions to split a chord sequence into two separate voices, also preserving articulations and slurs: <code>\keepOnlyFirstNote</code> extracts the first note (as given in the input; this is usually the lowest one) of every chord, and <code>\deleteFirstNote</code> collects the remaining notes.

Note that these function don't support <samp>q</samp> to repeat the last chord.

<lilypond version="2.24">
#(define (has-duration? music)
(ly:duration? (ly:music-property music 'duration)))

#(define (not-has-duration? music)
(not (has-duration? music)))

keepOnlyFirstNote =
#(define-music-function (parser location music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property!
evt 'elements
(cons (car elts)
(filter not-has-duration? (cdr elts)))))))
evt)
music))

deleteFirstNote =
#(define-music-function (parser location music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property! evt 'elements (cdr elts)))))
evt)
music))

music = \relative c' {
<c e>4-> <d f>( <b g'>) <c e>-. g2 c2
}

\markup { Music with chords }
\new Staff \music

\markup { Music split into two staves }
<<
\new Staff \deleteFirstNote \music
\new Staff \keepOnlyFirstNote \music
>>
</lilypond>

[[category:Chords]]
[[category:Scheme]]
[[category:Really cool]]

Splitting chords

2026-04-05T09:09:04Z

Lemzwerg: Formatting, improved docstring

This snippet is a 2009 contribution by Gilles Thibault in [https://lists.gnu.org/archive/html/lilypond-user/2009-01/msg00685.html lilypond-user]. It provides two functions to split a chord sequence into two separate voices, also preserving articulations and slurs: <code>\keepOnlyFirstNode</code> extracts the first note (as given in the input; this is usually the lowest one) of every chord, and <code>\deleteFirstNote</code> collects the remaining notes.

Note that these function don't support <samp>q</samp> to repeat the last chord.

<lilypond version="2.24">
#(define (has-duration? music)
(ly:duration? (ly:music-property music 'duration)))

#(define (not-has-duration? music)
(not (has-duration? music)))

keepOnlyFirstNote =
#(define-music-function (parser location music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property!
evt 'elements
(cons (car elts)
(filter not-has-duration? (cdr elts)))))))
evt)
music))

deleteFirstNote =
#(define-music-function (parser location music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property! evt 'elements (cdr elts)))))
evt)
music))

music = \relative c' {
<c e>4-> <d f>( <b g'>) <c e>-. g2 c2
}

\markup { Music with chords }
\new Staff \music

\markup { Music split into two staffs }
<<
\new Staff \deleteFirstNote \music
\new Staff \keepOnlyFirstNote \music
>>
</lilypond>

[[category:Chords]]
[[category:Scheme]]
[[category:Really cool]]

User talk:MartialR

2026-03-31T11:16:49Z

Lemzwerg: /* Recorder diagrams */ new section

== Recorder diagrams ==

Please have a look at [https://wiki.lilypond.community/wiki/Talk:Diagram_for_Recorder_baroque_in_F_and_C#c-Lemzwerg-20260331094100-Better_markup_definitions this comment] -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 11:16, 31 March 2026 (UTC)

Talk:Diagram for Recorder baroque in F and C

2026-03-31T11:10:26Z

Lemzwerg:

== Better markup definitions ==

Please ask for help on the [mailto:lilypond-user@gnu.org 'lilypond-user' mailing list] how to write a Scheme function for defining the fingering markups, avoiding tedious repetition! This will dramatically reduce the size of the definitions, also making them easier to maintain. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 09:41, 31 March 2026 (UTC)

Talk:Diagram for Recorder baroque in F and C

2026-03-31T09:41:28Z

Lemzwerg: /* Better markup definitions */ new section

== Better markup definitions ==

Please ask for help on the [[mailto:lilypond-user@gnu.org 'lilypond-user' mailing list]] how to write a Scheme function for defining the fingering markups, avoiding tedious repetition! This will dramatically reduce the size of the definitions, also making them easier to maintain. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 09:41, 31 March 2026 (UTC)

Key signatures for small staves

2026-03-18T18:11:37Z

Lemzwerg: Revised.

Traditionally, the spacing of key signatures in smaller staves is larger in comparison to full-size staves.

Here is a function that extends <code>\magnifyStaff</code> to automatically calculate the right key signature spacing according to the staff size.

<lilypond version="2.24">
scaleStaff =
#(define-music-function (scaleFac) (number?)
#{
\magnifyStaff #scaleFac
\override KeySignature.padding = #(* 2/3 (- 1 scaleFac))
#})

keyTest = { \key cis\major s4*4 \bar "" }

\markup\italic "Default output:"
<<
\new Staff \with { \magnifyStaff #5/7 } \keyTest
\new Staff \keyTest
>>

\markup\italic "Traditional output:"
<<
\new Staff \with { \scaleStaff #5/7 } \keyTest
\new Staff \keyTest
>>
</lilypond>

[[Category:Staff notation]]
[[Category:Vocal music]]
[[Category:Spacing]]
[[Category:Tweaks and overrides]]
[[Category:Specific notation]]
[[Category:Workaround]]
[[Category:Snippet]]

LSR 1094

2026-03-18T17:55:16Z

Lemzwerg: Changed redirect target from Key signature and small staff to Key signatures for small staves

#REDIRECT [[Key signatures for small staves]]

Key signatures for small staves

2026-03-18T17:54:43Z

Lemzwerg: Lemzwerg moved page Key signature and small staff to Key signatures for small staves without leaving a redirect

Traditionally, smaller staves key signature spacing is slightly different than full size staves ones.

Here's a function that automatically calculates the right key signature spacing according to the staff size.

<lilypond version="2.24">
%% => http://lsr.di.unimi.it/LSR/Item?id=1094

%% This extends \staffSize as defined in
%% "Changing the size of a staff with a music function"
%% http://lsr.di.unimi.it/LSR/Item?id=862
staffSize = #(define-music-function (new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol.staff-space = #(magstep new-size)
\override StaffSymbol.thickness = #(magstep new-size)
\override KeySignature.padding = #(* 2/3 (- 1 (magstep new-size)))
#})

keyTest = { \key cis\major s4*4 \bar "" }

\markup\italic "Default output:"
<<
\new Staff \with {
fontSize = #-3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
} \keyTest
\new Staff \keyTest

>>

\markup\italic "Traditional output:"
<<
\new Staff \with { \staffSize #-3 } \keyTest
\new Staff \keyTest

>>

%{
% For v.2.19 and higher:

scaleStaff = #(define-music-function (scaleFac) (number?)
#{
\magnifyStaff #scaleFac
\override KeySignature.padding = #(* 2/3 (- 1 scaleFac))
#})

sizeTest = #5/7
keyTest = { \key cis\major s4*4 \bar "" }

<<
\new Staff \with { \scaleStaff #sizeTest } \keyTest
\new Staff \keyTest
>>
%}
</lilypond>

[[Category:Staff notation]]
[[Category:Vocal music]]
[[Category:Spacing]]
[[Category:Contexts and engravers]]
[[Category:Tweaks and overrides]]
[[Category:Specific notation]]
[[Category:Workaround]]
[[Category:Snippet]]

Talk:Airy tone

2026-03-18T16:58:38Z

Lemzwerg: /* Circles not displaying in Wiki */ Reply

== Circles not displaying in Wiki ==

The circles are not displaying in the Wiki. However, if I copy and paste the code and compile it locally, the circles do display. Does anyone know how to fix this? [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 16:40, 18 March 2026 (UTC)

:The usual thing: The code for drawing the circles is Postscript, which is not supported by the SVG backend used in the Wiki. It should be rewritten using LilyPond drawing commands. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:58, 18 March 2026 (UTC)

Feta font chart

2026-03-16T23:15:20Z

Lemzwerg: Revised

This chart shows all articulations or scripts that LilyPond's “feta” font contains.

<lilypond version="2.24">
<<
\new Staff \relative c'' {
c\accent c\marcato c\staccatissimo
c\staccato c\tenuto c\portato
c\upbow c\downbow c\flageolet
c\thumb c^\lheel c\rheel
c^\ltoe c\rtoe c\open
c\stopped c\turn c\reverseturn
c\trill c\prall c\mordent
c\prallprall c\prallmordent c\upprall
c\downprall c\upmordent c\downmordent
c\pralldown c\prallup c\lineprall
c\signumcongruentiae c\shortfermata c\fermata
c\longfermata c\verylongfermata c\segno
c\coda c\varcoda
}

\new Lyrics \lyricmode {
accent marcato staccatissimo
staccato tenuto portato
upbow downbow flageolet
thumb lheel rheel
ltoe rtoe open
stopped turn reverseturn
trill prall mordent
prallprall prallmordent upprall
downprall upmordent downmordent
pralldown prallup lineprall
signumcongruentiae shortfermata fermata
longfermata verylongfermata segno
coda varcoda
}
>>

\layout {
\context {
\Staff
\remove Clef_engraver
\remove Time_signature_engraver
\remove Bar_line_engraver
}
\context {
\Lyrics
\override LyricText.font-family = #'typewriter
\override LyricSpace.minimum-distance = 3
}
\context {
\Score
timing = ##f
forbidBreakBetweenBarLines = ##f
}
}
</lilypond>

[[Category:Symbols and glyphs]]
[[Category:Expressive marks]]
[[Category:Snippet]]

Positioning a \fermata over the last bar line

2026-03-15T16:41:23Z

Lemzwerg:

To position a \fermata sign over the last bar line, you must use a specially modified rehearsal mark.

<lilypond version="2.24">
\relative c'' {
\override Score.RehearsalMark.break-visibility = #begin-of-line-invisible
c1 \mark \markup { \musicglyph "scripts.ufermata" }
}
</lilypond>

[[Category:Expressive marks]]
[[Category:Breaks]]
[[Category:Staff notation]]
[[Category:Workaround]]
[[Category:Symbols and glyphs]]
[[Category:Snippet]]

Alternate \textSpanner engraver

2026-03-12T06:46:28Z

Lemzwerg:

LilyPond's default text spanner engraver can only handle a single text spanner per voice at a time. The engraver in this snippet provides an alternate implementation to circumvent this limitation; it uses spanner IDs to specify start and end of overlapping text spanners.

To use it, replace <code>Text_spanner_engraver</code> with <code>\alternateTextSpannerEngraver</code>. The example below demonstrates two possible ways to specify a spanner ID: either define a new command or use the <code>\=</code> command to directly set the ID.

To control the vertical order of text spanners, use the standard way of tweaking the <code>outside-staff-priority</code> property.

<lilypond version="2.24">
% LSR written by Dave Nalesnik
% LSR https://lists.gnu.org/archive/html/lilypond-user/2026-01/msg00006.html

% Incorporating some code from the rewrite in Scheme of
% Text_spanner_engraver in input/regression/scheme-text-spanner.ly

#(define (add-bound-item spanner item)
(if (null? (ly:spanner-bound spanner LEFT))
(ly:spanner-set-bound! spanner LEFT item)
(ly:spanner-set-bound! spanner RIGHT item)))

#(define (set-axis! grob axis)
(when (not (number? (ly:grob-property grob 'side-axis)))
(set! (ly:grob-property grob 'side-axis) axis)
(ly:grob-chain-callback
grob
(if (eq? axis X)
ly:side-position-interface::x-aligned-side
side-position-interface::y-aligned-side)
(if (eq? axis X)
'X-offset
'Y-offset))))

#(define (assign-spanner-index orig-ls)
"Determine an available position of a new spanner in an ordered
sequence of spanners (a list of pairs, where the car of the pair
gives the position). The goal is for the sequence to begin with
zero and contain no gaps. Return the index representing the
spanner's position.

Examples (only showing the cars of the pairs):

(0 1) => 2
(2 3) => 0
(0 3) => 1
(0 1 3) => 2
"
(if (null? orig-ls)
0
(let loop ((ls orig-ls)
(insert? #t)
(result 0))
(cond
((null? ls)
result)
;; Position at head of list.
((and insert? (> (caar orig-ls) 0))
(loop ls #f 0))
;; No gaps, put at end of list.
((and insert? (null? (cdr ls)))
(loop (cdr ls) #f (1+ (caar ls))))
;; Fill lowest position of gap.
((and insert?
(> (caadr ls) (1+ (caar ls))))
(loop (cdr ls) #f (1+ (caar ls))))
(else
(loop (cdr ls) insert? result))))))

alternateTextSpannerEngraver =
#(lambda (context)
(let (;; A list of pairs comprising a spanner index (not
;; `spanner-id` values) and a spanner which has been begun.
(spanners '())
(finished '()) ; A list of spanners in completion stage.
(start-events '()) ; A list of START events.
(stop-events '())) ; A list of STOP events.
(make-engraver
;; `\startTextSpan`, `\stopTextSpan`, and the like create
;; events which we collect here.
(listeners
((text-span-event engraver event)
(if (= START (ly:event-property event 'span-direction))
(set! start-events (cons event start-events))
(set! stop-events (cons event stop-events)))))

;; Populate `note-columns` property of spanners. Bounds are
;; set to note columns, and each spanner keeps a record of
;; the note columns it traverses.
(acknowledgers
((note-column-interface engraver grob source-engraver)
(for-each (lambda (s)
(ly:pointer-group-interface::add-grob
(cdr s) 'note-columns grob)
(when (null? (ly:spanner-bound (cdr s) LEFT))
(add-bound-item (cdr s) grob)))
spanners)
;; `finished` only contains spanners, no indices.
(for-each (lambda (f)
(ly:pointer-group-interface::add-grob
f 'note-columns grob)
(when (null? (ly:spanner-bound f RIGHT))
(add-bound-item f grob)))
finished)))

((process-music trans)
;; Move begun spanners from `span` to `finished`. We do
;; this on the basis of `spanner-id`. If we find a match
;; -- either the strings are the same, or both are unset --
;; a transfer can be made. Return a warning if we find no
;; match: spanner hasn't been properly begun.
(for-each
(lambda (es)
(let ((es-id (ly:event-property es 'spanner-id)))
(let loop ((sp spanners))
(if (null? sp)
(ly:warning "No spanner to end!")
(let ((sp-id (ly:event-property
(event-cause (cdar sp))
'spanner-id)))
(cond
((equal? sp-id es-id)
(set! finished (cons (cdar sp) finished))
(set! spanners
(remove (lambda (s)
(eq? s (car sp))) spanners)))
(else
(loop (cdr sp)))))))))
stop-events)

;; The end of our spanners can be acknowledged by other
;; engravers, thus announce them.
(for-each
(lambda (f)
(ly:engraver-announce-end-grob trans f (event-cause f)))
finished)

;; Make spanners in response to START events.
;;
;; Each new spanner is assigned an index denoting its
;; position relative to other active spanners. This is
;; enforced (for the moment) by adding a small amount to
;; the spanner's `outside-staff-priority` proportional to
;; this index. This is unlikely to result in conflicts,
;; though a better solution may be to organize the spanners
;; by a new alignment grob.
;;
;; Also, add any existing spanners to the
;; `side-support-elements` array of the new spanner. This
;; ensures correct ordering over line breaks when
;; `outside-staff-priority` is set to `#f` (which means
;; that it is no longer an outside-staff object -- not the
;; default).
(for-each
(lambda (es)
(let* ((new (ly:engraver-make-grob
trans 'TextSpanner es))
(new-idx (assign-spanner-index spanners))
(new-osp (ly:grob-property
new 'outside-staff-priority))
(new-osp (if (number? new-osp)
(+ new-osp (/ new-idx 1000.0))
new-osp)))
(set! (ly:grob-property
new 'outside-staff-priority) new-osp)
(set-axis! new Y)
;; Add spanners with a lower index than the new
;; spanner to its `side-support-elements` list. This
;; allows new spanners to fill gaps under the topmost
;; spanner.
(for-each (lambda (sp)
(when (< (car sp) new-idx)
(ly:pointer-group-interface::add-grob
new 'side-support-elements (cdr sp))))
spanners)
(set! spanners (cons (cons new-idx new) spanners))
(set! spanners (sort spanners car<))))
start-events)

;; Events have served their purpose for this timestep.
;; Clear the way for new events in later timesteps.
(set! start-events '())
(set! stop-events '()))

((stop-translation-timestep trans)
;; Set bounds of spanners to `PaperColumns` grobs if they
;; haven't been set. This allows spanners to be drawn
;; between spacers.
;;
;; Other uses? Doesn't appear to affect whether spanners
;; can de drawn between rests.
(for-each (lambda (s)
(when (null? (ly:spanner-bound (cdr s) LEFT))
(ly:spanner-set-bound!
(cdr s) LEFT
(ly:context-property context
'currentMusicalColumn))))
spanners)
(for-each (lambda (f)
(when (null? (ly:spanner-bound f RIGHT))
(ly:spanner-set-bound!
f RIGHT
(ly:context-property context
'currentMusicalColumn))))
finished)
(set! finished '()))

((finalize trans)
;; If spanner ends on spacer at end of context?
(for-each (lambda (f)
(when (null? (ly:spanner-bound f RIGHT))
(ly:spanner-set-bound!
f RIGHT
(ly:context-property context
'currentMusicalColumn))))
finished)
(set! finished '())
;; User didn't end spanner.
(for-each (lambda (sp)
(ly:warning "incomplete spanner removed!")
(ly:grob-suicide! (cdr sp)))
spanners)
(set! spanners '())))))

%%%%%%%%%%%%%%%%%%%%%%%%%%%%% EXAMPLE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

startTextSpanOne =
#(make-music 'TextSpanEvent 'span-direction START 'spanner-id "1")
stopTextSpanOne =
#(make-music 'TextSpanEvent 'span-direction STOP 'spanner-id "1")
startTextSpanTwo =
#(make-music 'TextSpanEvent 'span-direction START 'spanner-id "2")
stopTextSpanTwo =
#(make-music 'TextSpanEvent 'span-direction STOP 'spanner-id "2")

\layout {
\context {
\Voice
\remove Text_spanner_engraver
\consists \alternateTextSpannerEngraver
}
}

\relative c' {
\override TextSpanner.style = ##f
\override TextSpanner.thickness = 10
% \override TextSpanner.to-barline = ##t

a4 \tweak color #red \startTextSpan
b \tweak color #green \startTextSpanOne
c \tweak color #blue \startTextSpanTwo
d \=3\startTextSpan |
a4\stopTextSpan
b \stopTextSpanOne
\tweak color #red \startTextSpan
c \stopTextSpanTwo
\tweak color #green \startTextSpanOne
d \=3\stopTextSpan
\tweak color #blue \startTextSpanTwo |
a4 \=3\startTextSpan
b c d | \break

a4 b c d |
a4\stopTextSpan
\stopTextSpanOne
\stopTextSpanTwo
\=3\stopTextSpan
b
c \startTextSpan
d \tweak outside-staff-priority #0 \=1\startTextSpan |
a4 b
c \=1\stopTextSpan
d \stopTextSpan |
}
</lilypond>

[[Category:Contexts and engravers]]
[[Category:Editorial annotations]]
[[Category:Expressive marks]]
[[Category:Scheme]]
[[Category:Workaround]]
[[Category:Snippet]]