LilyPond wiki - Recent changes [en]

Main Page

Lemzwerg — Thu, 06 Aug 2026 04:40:11 GMT

← Older revision		Revision as of 04:40, 6 August 2026
Line 8:		Line 8:
	# Read the [[Help:Contributing\|guide to contributing new snippets]].		# 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-stable}} on the snippet since the syntax might have changed!

Time mark engraver

Lemzwerg — Thu, 06 Aug 2026 04:39:15 GMT

← Older revision		Revision as of 04:39, 6 August 2026
Line 10:		Line 10:
	* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).		* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).

	''Upgrade notice'': This snippet must be updated with the {{Convert-ly-~~devel~~}} script if used with a LilyPond version newer than 2.24.		''Upgrade notice'': This snippet must be updated with the {{Convert-ly-stable}} script if used with a LilyPond version newer than 2.24.

	<lilypond version="2.24">		<lilypond version="2.24">

Using Scheme to create a list of all available X11 colors (obsolete in 2.25)

Lemzwerg — Thu, 06 Aug 2026 04:38:07 GMT

← Older revision		Revision as of 04:38, 6 August 2026
Line 1:		Line 1:
	LilyPond supports named colors through <code>x11-color</code>, the corresponding color names can be found in the file <code>scm/x11-color.scm</code>. Using Scheme, one can easily create a LilyPond file displaying (all) supported color names with an example of each color automatically. The way to do this is loading the <code>scolor.scm</code> file and then creating a <code>\markup</code> for each color definition.		LilyPond supports named colors through <code>x11-color</code>, the corresponding color names can be found in the file <code>scm/x11-color.scm</code>. Using Scheme, one can easily create a LilyPond file displaying (all) supported color names with an example of each color automatically. The way to do this is loading the <code>scolor.scm</code> file and then creating a <code>\markup</code> for each color definition.

	This snippet is obsolete in version 2.25 since the documentation now contains a list of colors that also displays a square with each color, see [{{~~LILYDEVELDOC~~}}/notation/list-of-colors.html List of colors].		This snippet is obsolete in version 2.25 since the documentation now contains a list of colors that also displays a square with each color, see [{{LILYSTABLEDOC}}/notation/list-of-colors.html List of colors].

	<lilypond version="2.24">		<lilypond version="2.24">

Changing the default text font family

Lemzwerg — Thu, 06 Aug 2026 04:36:45 GMT

← Older revision		Revision as of 04:36, 6 August 2026
Line 2:		Line 2:

	<div class="nodoc">		<div class="nodoc">
	Note: Starting with LilyPond 2.25.4, font selection works differently; the most usual cases can be handled by {{Convert-ly-~~devel~~}}. See the [{{~~LILYDEVELDOC~~}}/notation/fonts ‘Notation’ manual] for more information.		Note: Starting with LilyPond 2.25.4, font selection works differently; the most usual cases can be handled by {{Convert-ly-stable}}. See the [{{LILYSTABLEDOC}}/notation/fonts ‘Notation’ manual] for more information.
	</div>		</div>

Applying tweaks to one voice in \partCombine

Lemzwerg — Thu, 06 Aug 2026 04:32:09 GMT

← Older revision		Revision as of 04:32, 6 August 2026
Line 1:		Line 1:
	When using <code>\partCombine</code>, commands applying to a <code>Voice</code> context affect both parts since when are merged in the same Voice. This snippet defines a music function to apply tweaks to all elements of a certain kind in a music expression. This can be used to apply modifications to all grobs caused by elements of a music expression regardless of the context structure. Possible values for the <code>event-class</code> argument are listed at the [{{LILYSTABLEDOC}}/internals/music-classes Internals Reference]		When using <code>\partCombine</code>, commands applying to a <code>Voice</code> context affect both parts since when are merged in the same Voice. This snippet defines a music function to apply tweaks to all elements of a certain kind in a music expression. This can be used to apply modifications to all grobs caused by elements of a music expression regardless of the context structure. Possible values for the <code>event-class</code> argument are listed at the [{{LILYSTABLEDOC}}/internals/music-classes Internals Reference]

	<lilypond version="2.24">		<lilypond version="2.26">
	% LSR https://lists.gnu.org/archive/html/lilypond-user/2021-06/msg00242.html		% LSR https://lists.gnu.org/archive/html/lilypond-user/2021-06/msg00242.html

	tweakEverywhere =		tweakEverywhere =
	#(define-music-function (parser location event-class property value music)		#(define-music-function
	(symbol? symbol-list-or-symbol? scheme? ly:music?)		(parser location event-class property value music)
	(for-some-music		(symbol? symbol-list-or-symbol? scheme? ly:music?)
	(lambda (m)
	(if (music-is-of-type? m event-class)		(for-some-music
	(begin		(lambda (m)
	(set! (ly:music-property m 'tweaks)		(if (music-is-of-type? m event-class)
	(cons (cons		(begin
	(if (symbol? property)		(set! (ly:music-property m 'tweaks)
	property		(cons (cons
	(apply cons* property))		(if (symbol? property)
	value)		property
	(ly:music-property m 'tweaks)))		(apply cons* property))
	#t)		value)
	#f))		(ly:music-property m 'tweaks)))
	music)		#t)
	music)		#f))
			music)
			music)

	soprano = { des' ees' fes' ges' fes' ges' aes' bes' }		soprano = { des' ees' fes' ges' fes' ges' aes' bes' }
	tenor = { des' ees' fes' ges' des' ees' fes' ges' }		tenor = { des' ees' fes' ges' des' ees' fes' ges' }

	\partCombineUp \soprano \tweakEverywhere rhythmic-event font-size -3 \tenor		\partCombineUp \soprano
	\partCombineUp \soprano \tweakEverywhere note-event Accidental.color #red \tenor		\tweakEverywhere rhythmic-event font-size -3 \tenor
			\partCombineUp \soprano
			\tweakEverywhere note-event Accidental.color #red \tenor
	</lilypond>		</lilypond>

	[[Category:Simultaneous notes]]		[[Category:Simultaneous notes]]
	[[Category:Snippet]]		[[Category:Snippet]]

Ambitus after key signature

Lemzwerg — Thu, 06 Aug 2026 04:27:49 GMT

← Older revision		Revision as of 04:27, 6 August 2026
Line 3:		Line 3:
	A common use case is printing the ambitus between key signature and time signature.		A common use case is printing the ambitus between key signature and time signature.

	<lilypond version="2.24">		<lilypond version="2.26">
	\new Staff \with {		\new Staff \with {
	\consists Ambitus_engraver		\consists Ambitus_engraver

Separating key cancellations from key signature changes

Lemzwerg — Thu, 06 Aug 2026 04:26:21 GMT

← Older revision		Revision as of 04:26, 6 August 2026
Line 13:		Line 13:
	We want to change that, moving <code>key-cancellation</code> before <code>staff-bar</code>. To make this happen we use the <code>grob-transformer</code> function, which gives us access to the original vector as the second argument of the lambda function, here called <var>orig</var> (we don't need the first argument, <var>grob</var>). We return a new vector, with unchanged first and last elements. For the middle element, we first remove <code>key-cancellation</code> from the list, then adding it again before <code>staff-bar</code>.		We want to change that, moving <code>key-cancellation</code> before <code>staff-bar</code>. To make this happen we use the <code>grob-transformer</code> function, which gives us access to the original vector as the second argument of the lambda function, here called <var>orig</var> (we don't need the first argument, <var>grob</var>). We return a new vector, with unchanged first and last elements. For the middle element, we first remove <code>key-cancellation</code> from the list, then adding it again before <code>staff-bar</code>.

	<lilypond version="2.24">		<lilypond version="2.26">
	%LSR based on		%LSR based on
	%LSR https://stackoverflow.com/questions/40964806/scheme-inserting-a-number-in-a-list		%LSR https://stackoverflow.com/questions/40964806/scheme-inserting-a-number-in-a-list

Accordion register symbols

Lemzwerg — Thu, 06 Aug 2026 04:24:03 GMT

← Older revision		Revision as of 04:24, 6 August 2026
Line 1:		Line 1:
	Accordion register symbols are available as <code>\markup</code> as well as as standalone music events (as register changes tend to occur between actual music events). Bass registers are not overly standardized. The available commands can be found in [{{LILYSTABLEDOC}}/notation/accordion#discant-symbols ‘Discant symbols’ in the Notation Reference].		Accordion register symbols are available as <code>\markup</code> as well as as standalone music events (as register changes tend to occur between actual music events). Bass registers are not overly standardized. The available commands can be found in [{{LILYSTABLEDOC}}/notation/accordion#discant-symbols ‘Discant symbols’ in the Notation Reference].

	<lilypond version="2.24">		<lilypond version="2.26">
	#(use-modules (lily accreg))		#(use-modules (lily accreg))

Segno or coda on top of rehearsal mark

Lemzwerg — Thu, 06 Aug 2026 04:22:55 GMT

← Older revision		Revision as of 04:22, 6 August 2026
Line 1:		Line 1:
	Starting with LilyPond 2.24 the <code>\textMark</code> command and the normal <code>\mark</code> command happily coexist. Furthermore, the sophisticated [{{LILYSTABLEDOC}}/notation/long-repeats#segno-repeat-structure <code>\repeat segno</code> command] is available. (Be sure to look at the English version, since translations of the Notation Reference might not be up to date.) Consequently, this snippet is much shorter in comparison to previous versions in the LSR.		Starting with LilyPond 2.24 the <code>\textMark</code> command and the normal <code>\mark</code> command happily coexist. Furthermore, the sophisticated [{{LILYSTABLEDOC}}/notation/long-repeats#segno-repeat-structure <code>\repeat segno</code> command] is available. (Be sure to look at the English version, since translations of the Notation Reference might not be up to date.) Consequently, this snippet is much shorter in comparison to previous versions in the LSR.

	<lilypond version="2.24">		<lilypond version="2.26">
	markDefault = \mark \default		markDefault = \mark \default

Changing properties for individual grobs

Lemzwerg — Thu, 06 Aug 2026 04:19:59 GMT

← Older revision		Revision as of 04:19, 6 August 2026
Line 5:		Line 5:
	See the [{{LILYSTABLEDOC}}/extending/running-a-function-on-all-layout-objects ‘Extending’ manual] for more information.		See the [{{LILYSTABLEDOC}}/extending/running-a-function-on-all-layout-objects ‘Extending’ manual] for more information.

	<lilypond version="2.24">		<lilypond version="2.26">
	#(define (mc-squared grob grob-origin context)		#(define (mc-squared grob grob-origin context)
	(let ((sp (ly:grob-property grob 'staff-position)))		(let ((sp (ly:grob-property grob 'staff-position)))

User talk:Jean Abou Samra

Lemzwerg — Thu, 06 Aug 2026 04:18:08 GMT

2.26 renders smaller than 2.24: new section

← Older revision		Revision as of 04:18, 6 August 2026
Line 149:		Line 149:
	:::::OK, this has become too much of a burden at this point, there are several users to block per day. I've added a simple anti-spam question which editors creating an account must solve ("What is the LilyPond command to set a time signature of 3/4?"), let's see how effective this is. [[User:Jean Abou Samra\|Jean Abou Samra]] ([[User talk:Jean Abou Samra\|talk]]) 13:14, 23 February 2026 (UTC)		:::::OK, this has become too much of a burden at this point, there are several users to block per day. I've added a simple anti-spam question which editors creating an account must solve ("What is the LilyPond command to set a time signature of 3/4?"), let's see how effective this is. [[User:Jean Abou Samra\|Jean Abou Samra]] ([[User talk:Jean Abou Samra\|talk]]) 13:14, 23 February 2026 (UTC)
	::::::It seems to work, thanks! -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 06:07, 28 February 2026 (UTC)		::::::It seems to work, thanks! -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 06:07, 28 February 2026 (UTC)

			== 2.26 renders smaller than 2.24 ==

			Jean, on my GNU/Linux box, both Chrome and Firefox render snippets using LilyPond 2.26 by about 25% smaller than 2.24. Any idea what causes this? This is definitely a larger difference in size than the slight margin increase introduced in 2.25 would cause. I prefer the larger size, or rather, I would like to have the images rendered even larger by default than what the Wiki for 2.24 provides.

			Another issue is the Wiki's 'dark' mode: the SVG images become almost invisible. Is it possible to detect dark mode and display the images with inverted drawing colours in this case? Alternatively, images should be given a white background. -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 04:18, 6 August 2026 (UTC)

Increasing spacing between staves

Lemzwerg — Thu, 06 Aug 2026 04:01:18 GMT

← Older revision		Revision as of 04:01, 6 August 2026
Line 5:		Line 5:
	For more details you should consult [{{LILYSTABLEDOC}}/notation/page-layout Section ‘Page layout’ of the Notation Reference].		For more details you should consult [{{LILYSTABLEDOC}}/notation/page-layout Section ‘Page layout’ of the Notation Reference].

	<lilypond version="2.24">		<lilypond version="2.26">
	\paper {		\paper {
	% spacing variables may be changed individually:		% spacing variables may be changed individually:

Creating fret diagrams with chord names but no staff/staves using fret diagram markup

Lemzwerg — Thu, 06 Aug 2026 04:00:07 GMT

← Older revision		Revision as of 04:00, 6 August 2026
Line 6:		Line 6:
	* https://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00080.html		* https://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00080.html

	<lilypond version="2.24">		<lilypond version="2.26">
	\storePredefinedDiagram		\storePredefinedDiagram
	#default-fret-table		#default-fret-table

Template:LILYDEVEL

Lemzwerg — Thu, 06 Aug 2026 03:55:38 GMT

← Older revision		Revision as of 03:55, 6 August 2026
Line 1:		Line 1:
	The current development version of LilyPond, without the patch level.		The current development version of LilyPond, without the patch level.

	<onlyinclude>2.25</onlyinclude>		<onlyinclude>2.27</onlyinclude>

	== Usage of this template ==		== Usage of this template ==

Template:LILYSTABLE

Lemzwerg — Thu, 06 Aug 2026 03:54:35 GMT

← Older revision		Revision as of 03:54, 6 August 2026
Line 1:		Line 1:
	The current stable version of LilyPond, without the patch level.		The current stable version of LilyPond, without the patch level.

	<onlyinclude>2.24</onlyinclude>		<onlyinclude>2.26</onlyinclude>

	== Usage of this template ==		== Usage of this template ==

User:Coffeebug

Coffeebug — Thu, 06 Aug 2026 02:15:11 GMT

User account Coffeebug was created

Combining beam and slur in one keystroke

Jean Abou Samra — Wed, 05 Aug 2026 22:55:53 GMT

← Older revision		Revision as of 22:55, 5 August 2026
Line 1:		Line 1:
	If a vocal part contains many short note values and melismata, and melismata are shown by both beams and slurs, there are many instances of <code> d([ b)] </code> for example. To save tedious keystrokes, it’s very convenient to redefine [ and ] so they provoke both the beam and the slur. Alternatively, the slurs may be omitted as in the second example, to avoid misinterpretations (performers might take the slur as an indication for dynamics and articulation, even if it’s only intended to provide information on melismata) or to get a clearer, less crowded look.		If a vocal part contains many short note values and melismata, and melismata are shown by both beams and slurs, there are many instances of <code> d([ b)] </code> for example. To save tedious keystrokes, it’s very convenient to redefine [ and ] so they provoke both the beam and the slur. Alternatively, the slurs may be omitted as in the second example, to avoid misinterpretations (performers might take the slur as an indication for dynamics and articulation, even if it’s only intended to provide information on melismata) or to get a clearer, less crowded look.

	<lilypond version="2.24" ~~full~~>		<lilypond version="2.26">
	~~\paper { tagline = ##f }~~

	"[" =		"[" =
	- #(make-music		- #(make-music

Changing beam thickness and spacing

Jean Abou Samra — Wed, 05 Aug 2026 22:38:26 GMT

Update to 2.26

← Older revision		Revision as of 22:38, 5 August 2026
Line 1:		Line 1:
	To make beams thicker or thinner, alter the <code>beam-thickness</code> property of the <code>Beam</code> grob. To adjust the spacing between beams, alter <code>length-fraction</code>.		To make beams thicker or thinner, alter the <code>beam-thickness</code> property of the <code>Beam</code> grob. To adjust the spacing between beams, alter <code>length-fraction</code>.

	<lilypond version="2.24">		<lilypond version="2.26">
	\relative f' {		\relative f' {
	\time 1/8		\time 1/8

User talk:Jean Abou Samra

Jean Abou Samra — Wed, 05 Aug 2026 21:40:14 GMT

More fonts for the Wiki: Reply

← Older revision		Revision as of 21:40, 5 August 2026
Line 86:		Line 86:
	:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra\|Jean Abou Samra]] ([[User talk:Jean Abou Samra\|talk]]) 09:13, 13 December 2025 (UTC)		:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra\|Jean Abou Samra]] ([[User talk:Jean Abou Samra\|talk]]) 09:13, 13 December 2025 (UTC)
	::::::Great, thanks! -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 10:50, 13 December 2025 (UTC)		::::::Great, thanks! -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 10:50, 13 December 2025 (UTC)
			:::::::For the record, I updated the snippet to use 2.26 and removed the extra fonts from the server. [[User:Jean Abou Samra\|Jean Abou Samra]] ([[User talk:Jean Abou Samra\|talk]]) 21:40, 5 August 2026 (UTC)

	== This wiki has no templates ==		== This wiki has no templates ==

UTF-8

Jean Abou Samra — Wed, 05 Aug 2026 21:39:32 GMT

Update to 2.26

← Older revision		Revision as of 21:39, 5 August 2026
Line 1:		Line 1:
	Various scripts may be used for texts (like titles and lyrics) by entering them in UTF-8 encoding. Depending on the fonts installed, this fragment renders Bulgarian (Cyrillic), Hebrew, Japanese, and Portuguese.		Various scripts may be used for texts (like titles and lyrics) by entering them in UTF-8 encoding. Depending on the fonts installed, this fragment renders Bulgarian (Cyrillic), Hebrew, Japanese, and Portuguese.

	<lilypond version="2.24">		<lilypond version="2.26">
	%{		%{
	You may have to install additional fonts.		You may have to install additional fonts.
Line 14:		Line 14:
	% 'Linux Libertine' fonts also contain Cyrillic and Hebrew glyphs.		% 'Linux Libertine' fonts also contain Cyrillic and Hebrew glyphs.
	\paper {		\paper {
	~~#(define fonts~~		property-defaults.fonts.serif = "Linux Libertine O, Noto Serif CJK JP, Noto Serif JP"
	~~(set-global~~-fonts
	~~#:roman~~ "Linux Libertine O, Noto Serif CJK JP, Noto Serif JP"
	))
	}		}

Changing the default text font family

Jean Abou Samra — Wed, 05 Aug 2026 21:38:16 GMT

Update to 2.26

← Older revision		Revision as of 21:38, 5 August 2026
Line 1:		Line 1:
	~~The~~ default font families for text ~~can be overridden with <code>make-pango-font-tree</code>~~.		Here is how to override the default font families for text.

	<div class="nodoc">		<div class="nodoc">
Line 5:		Line 5:
	</div>		</div>

	<lilypond version="2.24">		<lilypond version="2.26">
	%{		%{
	You may have to install additional fonts.		You may have to install additional fonts.
Line 16:		Line 16:

	\paper {		\paper {
	~~% change for a different default global staff size~~		property-defaults.fonts.serif = "DejaVu Serif"
	~~myStaffSize = #20~~		property-defaults.fonts.sans = "DejaVu Sans"
			property-defaults.fonts.typewriter = "DejaVu Sans Mono"
	%{
	~~run~~
	~~lilypond -dshow-available~~-fonts
	~~to show all fonts available in the process log~~.
	%}
	~~#(define fonts~~
	~~(make-pango-font-tree~~ "DejaVu Serif"
	"DejaVu Sans"
	"DejaVu Sans Mono"
	~~(/ myStaffSize 20)))~~
	}		}

Line 38:		Line 28:
	}		}
	g4_\markup {		g4_\markup {
	\~~override #'(font-family .~~ sans) {		\sans {
	DejaVu Sans: \bold bold		DejaVu Sans: \bold bold
	\italic italic		\italic italic
Line 45:		Line 35:
	}		}
	g''2^\markup {		g''2^\markup {
	\~~override #'(font-family .~~ typewriter) {		\typewriter {
	DejaVu Sans Mono: \bold bold		DejaVu Sans Mono: \bold bold
	\italic italic		\italic italic

Changing a single note’s size in a chord

Jean Abou Samra — Wed, 05 Aug 2026 21:24:41 GMT

Update to 2.26

← Older revision		Revision as of 21:24, 5 August 2026
Line 3:		Line 3:
	Inside the chord (within the brackets <code>< ></code>), before the note to be altered, place the <code>\tweak</code> command, followed by <code>font-size</code> and define the proper size like <code>#-2</code> (a tiny note head).		Inside the chord (within the brackets <code>< ></code>), before the note to be altered, place the <code>\tweak</code> command, followed by <code>font-size</code> and define the proper size like <code>#-2</code> (a tiny note head).

	<lilypond version="2.24">		<lilypond version="2.26">
	\relative c' {		\relative c' {
	<\tweak font-size #+2 c e g c		<\tweak font-size #+2 c e g c

A function to repeatedly print a given pattern with different notes

Jean Abou Samra — Wed, 05 Aug 2026 20:03:46 GMT

← Older revision		Revision as of 20:03, 5 August 2026
Line 4:		Line 4:
	This will replace notes in <code>\pattern</code> by notes in <code>\newnotes</code>. If the note-count in <code>\newnotes</code> is greater, the pattern is copied repeatedly. Rests or skips are allowed, and the function also works for chords. More detailed documentation (in pdf format), and also the most recent "changePitch.ly" can be found [http://gillesth.free.fr/Lilypond/changePitch/ here].		This will replace notes in <code>\pattern</code> by notes in <code>\newnotes</code>. If the note-count in <code>\newnotes</code> is greater, the pattern is copied repeatedly. Rests or skips are allowed, and the function also works for chords. More detailed documentation (in pdf format), and also the most recent "changePitch.ly" can be found [http://gillesth.free.fr/Lilypond/changePitch/ here].

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

	%% version 2013/05/11		%% version 2013/05/11
	%% for lilypond 2.18 or higher		%% for lilypond 2.18 or higher

Merging simultaneous voices into shared note heads

Mkouhia — Mon, 03 Aug 2026 12:36:59 GMT

Created page with "This snippet defines <code>\combineVoices</code>, a music function that takes any number of rhythmically identical voices written inside <code><< ... >></code> and merges them into a single voice under one stem. Wherever two or more of the voices share the same pitch at a given moment, only one note head is printed; wherever the pitches differ, a chord containing all of the distinct pitches is printed instead. This differs from the default functionality, where double no..."

New page

This snippet defines <code>\combineVoices</code>, a music function that takes
any number of rhythmically identical voices written inside
<code><< ... >></code> and merges them into a single voice under one stem.
Wherever two or more of the voices share the same pitch at a given
moment, only one note head is printed; wherever the pitches differ, a
chord containing all of the distinct pitches is printed instead.

This differs from the default functionality, where double note heads are printed in case of shared pitches.

<lilypond version="2.24">
% Return a list 0, 1, ..., n - 1.
#(define (int-range n)
(let loop ((i 0) (acc '()))
(if (= i n)
(reverse acc)
(loop (+ i 1) (cons i acc)))))

% Drill through any single-child wrapper node (as introduced by, e.g.,
% \relative) until a music object with a real, non-empty 'elements
% list is reached, and return that list.
#(define (music-elements m)
(let ((elts (ly:music-property m 'elements)))
(if (and (list? elts) (pair? elts))
elts
(let ((child (ly:music-property m 'element)))
(if (ly:music? child)
(music-elements child)
'())))))

% Return the NoteEvents contained in a single moment of music. A
% plain note is a bare NoteEvent; an explicit chord <...> is an
% EventChord wrapping one NoteEvent per pitch. Rests and skips
% contain no pitch and contribute nothing.
#(define (note-events moment)
(cond
((eq? (ly:music-property moment 'name) 'NoteEvent)
(list moment))
((eq? (ly:music-property moment 'name) 'EventChord)
(filter (lambda (e) (eq? (ly:music-property e 'name) 'NoteEvent))
(ly:music-property moment 'elements)))
(else '())))

% A comparable key for a pitch, since pitch objects do not compare
% correctly with equal?.
#(define (pitch-key p)
(list (ly:pitch-notename p) (ly:pitch-alteration p) (ly:pitch-octave p)))

% Merge one moment's worth of notes, taken from several voices, into
% a single EventChord with duplicate pitches removed.
#(define (merge-chords moments)
(let ((seen '())
(notes '()))
(for-each
(lambda (moment)
(for-each
(lambda (note)
(let ((key (pitch-key (ly:music-property note 'pitch))))
(if (not (member key seen))
(begin
(set! seen (cons key seen))
(set! notes (cons note notes))))))
(note-events moment)))
moments)
(if (null? notes)
(car moments) ; every voice rests here: keep a rest
(make-music 'EventChord 'elements (reverse notes)))))

combineVoices =
#(define-music-function (music) (ly:music?)
(let* ((voices (ly:music-property music 'elements))
(seqs (map music-elements voices))
(lens (map length seqs)))
(make-music 'SequentialMusic 'elements
(map (lambda (i) (merge-chords (map (lambda (s) (list-ref s i)) seqs)))
(int-range (apply min lens))))))

\new Voice \combineVoices <<
\relative { c''4 f8 d e16 f g8 d4 }
\relative { c''4 d8 b c16 d e8 b4 }
>>
</lilypond>

[[Category:Simultaneous notes]]
[[Category:Chords]]
[[Category:Snippet]]

User:Mkouhia

Mkouhia — Mon, 03 Aug 2026 12:15:13 GMT

User account Mkouhia was created

Metronome marks with parentheses

Ksnortum — Fri, 31 Jul 2026 17:11:01 GMT

Metronome marks with parentheses and no tempo name

New page

When you use the <code>\tempo</code> command, you can add a metronome mark to it. If you want just the metronome mark, leave out the tempo name. This gives you a metronome mark without parentheses. If you want the parentheses around the metronome mark, use an empty string <code>""</code> for the tempo name.

<lilypond version="2.26">
{
\tempo "Allegro" 4 = 132
c'1 1
\tempo 4 = 100
1
\tempo "" 4 = 120
1
}
</lilypond>

[[Category:Really simple]]
[[Category:Snippet]]