LilyPond wiki - Recent changes [en]

Curly end barline

Ksnortum — Wed, 17 Jun 2026 13:21:16 GMT

Decrease paper size so there is less white space between the rendered image and the code

← Older revision		Revision as of 13:21, 17 June 2026
Line 5:		Line 5:
	% Credits: PPS on March 2015		% Credits: PPS on March 2015

	\paper { tagline = ##f }		% Paper block variables can be removed
			\paper {
			#(set-paper-size '(cons (* 75 mm) (* 50 mm)))
			tagline = ##f
			}

	endBarCurlyPath = \markup {		endBarCurlyPath = \markup {

User:JT612

JT612 — Mon, 15 Jun 2026 20:05:24 GMT

User account JT612 was created

Metric modulation (proportional tempi)

Gabriel Ellsworth — Sat, 13 Jun 2026 22:38:39 GMT

I added links to Yoshiaki Onishi’s solution.

← Older revision		Revision as of 22:38, 13 June 2026
Line 1:		Line 1:
	This snippet shows how you can typeset a metric modulation as a rehearsal mark. (See [https://lists.gnu.org/archive/html/lilypond-user/2026-05/msg00194.html this thread on the mailing list].) ~~Compare [[Metric modulation with tuplet]].~~		This snippet shows how you can '''typeset a metric modulation as a rehearsal mark'''. (See [https://lists.gnu.org/archive/html/lilypond-user/2026-05/msg00194.html this thread on the mailing list].)

	In the code below, the following commands enable you to to center the = glyph above the bar line.		In the code below, the following commands enable you to '''center the = glyph above the bar line'''.
	# <code>\general-align</code> commands set the center of the <code>myMetricModulation</code> markup to be the center of the equals sign (=). For more information, see [https://lilypond.org/doc/v2.26/Documentation/notation/text-markup-commands#markup-for-text-alignment A.1.2 Markup for text alignment] in the Notation Reference.		# <code>\general-align</code> commands set the center of the <code>myMetricModulation</code> markup to be the center of the equals sign (=). For more information, see [https://lilypond.org/doc/v2.26/Documentation/notation/text-markup-commands#markup-for-text-alignment A.1.2 Markup for text alignment] in the Notation Reference.
	# <code>\put-adjacent</code> commands add elements to the sides of the equals sign without shifting it. See [https://lilypond.org/doc/v2.26/Documentation/notation/text-markup-commands#markup-for-text-alignment A.1.2 Markup for text alignment].		# <code>\put-adjacent</code> commands add elements to the sides of the equals sign without shifting it. See [https://lilypond.org/doc/v2.26/Documentation/notation/text-markup-commands#markup-for-text-alignment A.1.2 Markup for text alignment].
	# Switching off <code>self-alignment-X</code> means that the 0 coordinate of the stencil gets used for alignment with the bar line, without any shifting. ~~Without~~ <code>\tweak self-alignment-X ##f</code>, <code>self-alignment-X = 0</code> ~~would~~ calculate a shift in order to align the center of the markup (rather than the equals sign) to its anchor point.		# Switching off <code>self-alignment-X</code> means that the 0 coordinate of the stencil gets used for alignment with the bar line, without any shifting. (If you do not include <code>\tweak self-alignment-X ##f</code>, then <code>self-alignment-X = 0</code> will calculate a shift in order to align the center of the markup, rather than the equals sign, to its anchor point.)

	The music is from Tomás Luis de Victoria, “O magnum mysterium,” Tenor part ([https://ks15.imslp.org/files/imglnks/usimg/6/69/IMSLP106031-PMLP216234-TENOR.pdf PDF of source]).		The music on this page is from Tomás Luis de Victoria, “O magnum mysterium,” Tenor part ([https://ks15.imslp.org/files/imglnks/usimg/6/69/IMSLP106031-PMLP216234-TENOR.pdf PDF of source]).

			'''Some other approaches to metric modulations:'''
			# [[Metric modulation with tuplet]] shows a way to indicate a metric modulation that refers to a duration within a tuplet.
			# Yoshiaki Onishi’s approaches use <code>\textEndMark</code> and <code>\textMark</code> and print left and right arrows (← →) on each side of the equation, following the example of the scores of composer Elliott Carter. For an explanation, search for “Metric Modulation Equation” in Onishi’s [https://github.com/yoshiakionishi/lilypond-snippets/blob/main/DOCUMENT/YO_SNIPPETS_COOKBOOK_MASTER.pdf LilyPond Contemporary Notation Cookbook]; for the code, see [https://github.com/yoshiakionishi/lilypond-snippets/blob/main/DOCUMENT/metricModulationRegularFlag.ly metricModulationRegularFlag.ly] and [https://github.com/yoshiakionishi/lilypond-snippets/blob/main/DOCUMENT/metricmodulationStraightFlag.ly metricmodulationStraightFlag.ly]. His commands support tuplet note values.

	<lilypond version="2.26">		<lilypond version="2.26">

Talk:Displaying LilyPond's data directory

Gabriel Ellsworth — Fri, 12 Jun 2026 11:38:08 GMT

Gabriel Ellsworth moved page Talk:Displaying LilyPond's data directory to Talk:Displaying LilyPond’s data directory Misspelled title: I changed the tick mark in “LilyPond’s” to curly (typographical) punctuation (a real apostrophe).

New page

== No LilyPond tag on scheme code ==

I purposely did not use the <code><lilypond></code> tag on this code because I didn't want to expose the Wiki's internal structure. If I'm being overly paranoid we can add it later. [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 16:42, 18 February 2026 (UTC)

:Printing the path inside the wiki wouldn't be a problem, but you can't use <code><nowiki><lilypond></nowiki></code> because it doesn't support snippets which don't produce any visual output. I think giving an error in this case is the right default for <code><nowiki><lilypond></nowiki></code> because we want to remind editors that snippets should come with examples, but adding a <code>no-output</code> option to <code><nowiki><lilypond></nowiki></code> could be sensible. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:12, 19 February 2026 (UTC)

Displaying LilyPond's data directory

Gabriel Ellsworth — Fri, 12 Jun 2026 11:38:08 GMT

Gabriel Ellsworth moved page Displaying LilyPond's data directory to Displaying LilyPond’s data directory Misspelled title: I changed the tick mark in “LilyPond’s” to curly (typographical) punctuation (a real apostrophe).

New page

In [[Frescobaldi]], you can install LilyPond while editing the Settings options. However, it is not always clear what directory LilyPond is installed in.

Using the following code will display LilyPond’s data directory in the LilyPond log.

<pre>
\version "2.24"

#(ly:message "The LilyPond data directory is located at: ~a" (ly:get-option 'datadir))
</pre>

(Thanks to Mark Knoop for this code.)

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

Metric modulation (proportional tempi)

Gabriel Ellsworth — Thu, 11 Jun 2026 22:03:21 GMT

Created page with "This snippet shows how you can typeset a metric modulation as a rehearsal mark. (See [https://lists.gnu.org/archive/html/lilypond-user/2026-05/msg00194.html this thread on the mailing list].) Compare Metric modulation with tuplet. In the code below, the following commands enable you to to center the = glyph above the bar line. # <code>\general-align</code> commands set the center of the <code>myMetricModulation</code> markup to be the center of the equals sign (=)...."

New page

This snippet shows how you can typeset a metric modulation as a rehearsal mark. (See [https://lists.gnu.org/archive/html/lilypond-user/2026-05/msg00194.html this thread on the mailing list].) Compare [[Metric modulation with tuplet]].

In the code below, the following commands enable you to to center the = glyph above the bar line.
# <code>\general-align</code> commands set the center of the <code>myMetricModulation</code> markup to be the center of the equals sign (=). For more information, see [https://lilypond.org/doc/v2.26/Documentation/notation/text-markup-commands#markup-for-text-alignment A.1.2 Markup for text alignment] in the Notation Reference.
# <code>\put-adjacent</code> commands add elements to the sides of the equals sign without shifting it. See [https://lilypond.org/doc/v2.26/Documentation/notation/text-markup-commands#markup-for-text-alignment A.1.2 Markup for text alignment].
# Switching off <code>self-alignment-X</code> means that the 0 coordinate of the stencil gets used for alignment with the bar line, without any shifting. Without <code>\tweak self-alignment-X ##f</code>, <code>self-alignment-X = 0</code> would calculate a shift in order to align the center of the markup (rather than the equals sign) to its anchor point.

The music is from Tomás Luis de Victoria, “O magnum mysterium,” Tenor part ([https://ks15.imslp.org/files/imglnks/usimg/6/69/IMSLP106031-PMLP216234-TENOR.pdf PDF of source]).

<lilypond version="2.26">
% Optional: Define markup commands
% to contain shortcuts for the notes
% to typeset in your metric modulation markup.
simpleBreve = \markup {
\override #'(style . baroque)
\note { \breve }
#UP % (stem direction)
}

dottedBreve = \markup {
\override #'(style . baroque)
\note { \breve. }
#UP % (stem direction)
}

thickSpace = \markup \char ##x2004
% Unicode codepoint U+2004 is a
% Three-per-Em space
% (also known as a “thick space”); see
% https://en.wikipedia.org/wiki/Whitespace_character#Unicode

% Define a custom markup command
% to typeset an equals sign (=)
% with a thick space on each side.
equals = \markup {
\put-adjacent #X #RIGHT
\put-adjacent #X #LEFT
\general-align #Y #DOWN \char ##x003D
% https://en.wikipedia.org/wiki/Mathematical_operators_and_symbols_in_Unicode
\thickSpace
\thickSpace
}

% Define a markup that says
% “breve = dotted breve”
% with the = glyph at the
% center of this markup.
myMetricModulation = \markup {
\put-adjacent #X #RIGHT
\put-adjacent #X #LEFT

\general-align #X #CENTER
\general-align #Y #CENTER
\equals

\simpleBreve
\dottedBreve
}

words = \lyricmode {
Ie -- sum Chris -- tum
al -- le -- lu -- ia
al
}

music = \relative {
\key g \dorian
\clef "petrucci-c4"
\override NoteHead.style = #'baroque
\tag #'metronome { \tempo 1 = 60 }
\time 2/1
f\breve | g1 a1 |
\tweak self-alignment-X ##f
\mark \myMetricModulation
\tag #'metronome {
\once \override Score.MetronomeMark.X-offset = #7
\tempo "" 1 = 90
}
\time 3/1
g\breve g1 | d'\breve d1 |
c\breve c1 |
}

\markup { \circle 1 Metric modulation: }
\markup \vspace #0.2
\score {
<<
\new Voice = "tenor"
\removeWithTag #'metronome \music
\new Lyrics \lyricsto "tenor" \words
>>
}

\markup { \circle 2 With metronome marks added: }
\markup \vspace #0.2
\score {
<<
\new Voice = "tenor"
\keepWithTag #'metronome \music
\new Lyrics \lyricsto "tenor" \words
>>
}
</lilypond>
[[Category:Rhythms]]
[[Category:Editorial annotations]]
[[Category:Ancient notation]]
[[Category:Real music]]
[[Category:Snippet]]

Main Page

Gabriel Ellsworth — Thu, 11 Jun 2026 21:33:18 GMT

I created a numbered list to make it easier for readers to understand what they can do on this site.

← Older revision		Revision as of 21:33, 11 June 2026
Line 1:		Line 1:
	Welcome to the LilyPond wiki! This is a place where you can find and contribute commented code snippets for the [https://lilypond.org GNU LilyPond] music typesetting program.		Welcome to the LilyPond wiki! This is a place where you can find and contribute commented code snippets for the [https://lilypond.org GNU LilyPond] music typesetting program.

	Use the search box to look for snippets~~, view~~ the [[Special:AllPages\|list of all pages]]~~, or read~~ the [[Help:Contributing\|~~editing help~~]]~~. You might also enter a LilyPond Snippet Repository (LSR) number to access a redirection to the corresponding page~~.		You can:
			# Use the search box to look for snippets.
			# Enter a LilyPond Snippet Repository (LSR) number to access a redirection to the corresponding page.
			# View the [[Special:AllPages\|list of all pages]].
			# Browse [[Special:Categories\|snippets by category]].
			# Read the [[Help:Contributing\|guide to contributing new snippets]].

	Most snippets are set up to use the stable LilyPond release 2.24 (the intended version is always shown in the snippet). To use a newer version, ~~don't~~ forget to call {{Convert-ly-devel}} on the snippet since the syntax might have changed!		Most snippets are set up to use the stable LilyPond release 2.24 (the intended version is always shown in the snippet). To use a newer version, don’t forget to call {{Convert-ly-devel}} on the snippet since the syntax might have changed!

User:Musicologyman

Musicologyman — Thu, 11 Jun 2026 16:30:10 GMT

User account Musicologyman was created

User:Chris

Chris — Thu, 11 Jun 2026 15:34:28 GMT

User account Chris was created

Bracketed passages

Ksnortum — Wed, 10 Jun 2026 18:33:15 GMT

Doesn't need "full" indicator, or removing the tag line

← Older revision		Revision as of 18:33, 10 June 2026
Line 1:		Line 1:
	Code to make Lilypond draw left and right brackets vertically spanning a staff. This is intended to indicate an optional passage of music.		Code to make Lilypond draw left and right brackets vertically spanning a staff. This is intended to indicate an optional passage of music.

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

Line 7:		Line 7:
	% spanning an entire staff. It is useful for offseting optional passages of music,		% spanning an entire staff. It is useful for offseting optional passages of music,
	% as shown in the example		% as shown in the example

	~~\paper { tagline = ##f }~~

	% The number next to "th" in (th 0.2) controls thickness of the brackets.		% The number next to "th" in (th 0.2) controls thickness of the brackets.

Talk:Arpeggio bracket

Ksnortum — Wed, 10 Jun 2026 14:05:30 GMT

2.26 Conversion Note: new section

New page

== 2.26 Conversion Note ==

When this is converted to 2.26, it should use <code>\nonArpeggiato</code>. [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 14:05, 10 June 2026 (UTC)

User:David R

David R — Wed, 03 Jun 2026 16:37:11 GMT

User account David R was created

Talk:Repeats headword

Ksnortum — Tue, 26 May 2026 14:24:53 GMT

New property for initial repeat bar: new section

New page

== New property for initial repeat bar ==

I believe this snippet should change in 2.26 as there is now a property <code>\set Score.printInitialRepeatBar = ##t\</code> [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 14:24, 26 May 2026 (UTC)

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

Gabriel Ellsworth — Mon, 25 May 2026 22:31:32 GMT

Title Change: Reply

← Older revision		Revision as of 22:31, 25 May 2026
Line 4:		Line 4:

	:Agreed – and moved -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 19:54, 25 May 2026 (UTC)		:Agreed – and moved -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 19:54, 25 May 2026 (UTC)
			::Thank you! [[User:Gabriel Ellsworth\|Gabriel Ellsworth]] ([[User talk:Gabriel Ellsworth\|talk]]) 22:31, 25 May 2026 (UTC)

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

Lemzwerg — Mon, 25 May 2026 19:54:54 GMT

Title Change: Reply

← Older revision		Revision as of 19:54, 25 May 2026
Line 2:		Line 2:

	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)		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

Lemzwerg — Mon, 25 May 2026 19:54:24 GMT

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

← Older revision		Revision as of 19:54, 25 May 2026
Line 1:		Line 1:
	#REDIRECT [[SemiChoirStaff is a ChoirStaff with SpanBars for ~~non-~~special bar lines]]		#REDIRECT [[SemiChoirStaff is a ChoirStaff with SpanBars for special bar lines]]

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

Lemzwerg — Mon, 25 May 2026 19:54:04 GMT

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

New page

== 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)

SemiChoirStaff is a ChoirStaff with SpanBars for non-special bar lines

Lemzwerg — Mon, 25 May 2026 19:54:04 GMT

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

New page

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]]

User:Jc123

Jc123 — Mon, 25 May 2026 19:28:37 GMT

User account Jc123 was created

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

Gabriel Ellsworth — Mon, 25 May 2026 18:39:31 GMT

Title Change: new section

New page

Automatically coloring grobs to indicate when their direction has been manually set

Ksnortum — Mon, 25 May 2026 14:57:46 GMT

Doesn't need "full" layout

← Older revision		Revision as of 14:57, 25 May 2026
Line 1:		Line 1:
	When editing a piece of music, it can be helpful to see when the directions of slurs, stems, or other grobs have been manually set (as opposed to being automatically set by LilyPond). This snippet changes the color of grobs when their direction has been manually set. Red indicates up, and blue indicates down. It can be applied to all grobs, or just to certain types of grob (i.e. just <code>Slur</code>, or just <code>Slur</code> and <code>TextScript</code>).		When editing a piece of music, it can be helpful to see when the directions of slurs, stems, or other grobs have been manually set (as opposed to being automatically set by LilyPond). This snippet changes the color of grobs when their direction has been manually set. Red indicates up, and blue indicates down. It can be applied to all grobs, or just to certain types of grob (i.e. just <code>Slur</code>, or just <code>Slur</code> and <code>TextScript</code>).

	<lilypond version="2.24" ~~full~~>		<lilypond version="2.24">
	%% http://lsr.di.unimi.it/LSR/Item?u=1&id=889		%% http://lsr.di.unimi.it/LSR/Item?u=1&id=889

Diagram for Recorder in C (soprano & tenor)

Jean Abou Samra — Mon, 25 May 2026 12:58:26 GMT

Jean Abou Samra deleted page Diagram for Recorder in C (soprano & tenor) Author request