LilyPond wiki - Recent changes [en]

Lowest and highest pitch as chord

Manuela — Sun, 03 May 2026 11:07:16 GMT

Code replaced with Harm's version from the German Lilypond forum

@@ Line 1: / Line 1: @@
-This code returns the lowest and the highest pitch of a music expression as chord.
+Takes <code>MUSIC</code> and returns sequential music, simultaneous music or an event-chord
-The duration of the chord can be chosen arbitrarily as input parameter.
+<lilypond version="2.26.0" >
-You can easily change the chord to a fixed duration. You can even chose different durations for the pitches in the chord.
+#(define (make-note-event pitch duration)
+  "Takes PITCH and DURATION and returns a NoteEvent."
-<lilypond version="2.26.0" >
+  (make-music
-%% This snippets returns the lowest and the highest pitch
+extrema =
-%% of a music expression als chord
+#(define-music-function (proc m music duration)
-%% the duration of the chord is passed as argument
+  ((procedure? identity) ly:music? ly:music? ly:duration?)
-myambitus =
+testMus = \relative { d' e fis g a b cis }
-#(define-music-function (mus dur)(ly:music? ly:duration?)
-   (let*
+{ \extrema {} \testMus 4 }
+%% Below, preceed with \new Staff to avoid implicit creation of two staves
-      (alle-pitches
+{ \extrema <<>> \testMus 4 }
-       (let loop ((mus mus) (pitches '()))
+{ \extrema <> \testMus 4 }
-mymus = \relative { c' c f,, }
+%% Get only bottom or top note
-{ \clef bass \myambitus \mymus #(ly:make-duration 0) }
+{ \extrema #first {} \testMus 4 }
-{ \clef bass \myambitus \transpose c e \mymus 2. }
+{ \extrema #last {} \testMus 4 }</lilypond>
 [[Category:Pitches]]
 [[Category:Scheme]]

User:Manuela/lowest and highest pitch as chord

Manuela — Sun, 03 May 2026 08:04:38 GMT

Manuela moved page User:Manuela/lowest and highest pitch as chord to Lowest and highest pitch as chord

← Older revision		Revision as of 08:04, 3 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	This code returns the lowest and the highest pitch of a music expression as chord.		This code returns the lowest and the highest pitch of a music expression as chord.

	The duration of the chord can be chosen arbitrarily.		The duration of the chord can be chosen arbitrarily as input parameter.

	You can easily change the chord to a fixed duration.		You can easily change the chord to a fixed duration. You can even chose different durations for the pitches in the chord.

	<lilypond version="2.26.0" >		<lilypond version="2.26.0" >

User:Manuela/lowest and highest pitch as chord

Manuela — Sun, 03 May 2026 07:52:45 GMT

Created page with "This code returns the lowest and the highest pitch of a music expression as chord. The duration of the chord can be chosen arbitrarily. You can easily change the chord to a fixed duration. <lilypond version="2.26.0" > %% This snippets returns the lowest and the highest pitch %% of a music expression als chord %% the duration of the chord is passed as argument myambitus = #(define-music-function (mus dur)(ly:music? ly:duration?) (let* ( (alle-pitches..."

New page

This code returns the lowest and the highest pitch of a music expression as chord.

The duration of the chord can be chosen arbitrarily.

You can easily change the chord to a fixed duration.

<lilypond version="2.26.0" >

%% This snippets returns the lowest and the highest pitch
%% of a music expression als chord
%% the duration of the chord is passed as argument

myambitus =
#(define-music-function (mus dur)(ly:music? ly:duration?)
(let*
(
(alle-pitches
(let loop ((mus mus) (pitches '()))
(let ((p (ly:music-property mus 'pitch)))
(if (ly:pitch? p)
(cons p pitches)
(let ((elt (ly:music-property mus 'element)))
(fold loop
(if (ly:music? elt)
(loop elt pitches)
pitches)
(ly:music-property mus 'elements)))))))
(alle-sortiert (sort alle-pitches ly:pitch<?))
(tief (car alle-sortiert))
(hoch (car (reverse alle-sortiert)))
)
; (display tief )(display hoch)
; (write-me "alle pitches----> " (list? alle-pitches))
(make-music
'EventChord 'elements
(list
(make-music
'NoteEvent
'duration
dur
'pitch
tief)
(make-music
'NoteEvent
'pitch
hoch
'duration
dur)))
))

mymus = \relative { c' c f,, }
{ \clef bass \myambitus \mymus #(ly:make-duration 0) }
{ \clef bass \myambitus \transpose c e \mymus 2. }
</lilypond>
[[Category:Pitches]]
[[Category:Scheme]]

Typesetting IPA transcriptions for lyrics

Gabriel Ellsworth — Fri, 01 May 2026 18:23:12 GMT

I updated the code for version 2.26 and added the \eventCount function.

Show changes

Aligning lyrics based on vowels

Gabriel Ellsworth — Thu, 30 Apr 2026 16:27:34 GMT

Created page with "This snippet shows how, in music with lyrics, you can align lyrics based on where vowels fall within <code>LyricText</code> items. In each measure of this snippet, '''the first note demonstrates the use of these functions''', and the second note shows LilyPond’s default alignment. '''Source:''' Solution by Kieren MacMillan posted to the mailing list [https://lists.gnu.org/archive/html/lilypond-user/2026-01/msg00334.html in this thread]. The code for this solution was..."

New page

This snippet shows how, in music with lyrics, you can align lyrics based on where vowels fall within <code>LyricText</code> items.

In each measure of this snippet, '''the first note demonstrates the use of these functions''', and the second note shows LilyPond’s default alignment.

'''Source:''' Solution by Kieren MacMillan posted to the mailing list [https://lists.gnu.org/archive/html/lilypond-user/2026-01/msg00334.html in this thread]. The code for this solution was inspired by [[Center lyric syllables (ignoring punctuation)]].

<lilypond version="2.26">
% View this snippet online:
% https://wiki.lilypond.community/wiki/Aligning_lyrics_based_on_vowels

% Define the set of characters that will be
% classified as vowels for these commands:
#(define vowel-set
(list->char-set
(string->list "AÁÀÃÂÆǼEÉÈÊIÍÌÎOÓÒÕÔŒU
ÚÙÛYaáàãâæǽeéèêiíìîoóòõôœuúùûy")))
% Tweak this set based on your needs.
% For example, if your lyrics are in a language
% in which ⟨y⟩ is *always* pronounced as a vowel,
% you will want to make sure that Y and y are in your list.

% This function returns the width of the
% grob (stencil) for a given piece of text.
#(define (width grob text)
(let* ((X-extent
(ly:stencil-extent (grob-interpret-markup grob text) X)))
(if (interval-empty? X-extent)
0
(cdr X-extent))))

% This callback sets the alignment point of a LyricText grob
% to the centre of the first vowel that it contains.
#(define (center-on-first-vowel grob)
(let* ((text (ly:grob-property-data grob 'text))
(syllable (markup->string text))
(vowel-position
(if (string-index syllable vowel-set)
(string-index syllable vowel-set)
0))
(vowel-end
(if (string-index syllable vowel-set)
(+ (string-index syllable vowel-set) 1)
(string-length syllable)))
(preword (substring syllable 0 vowel-position))
(word (substring syllable vowel-position vowel-end))
(preword-width (width grob preword))
(word-width (width grob
(if (string-null? syllable) text word)))
(note-column (ly:grob-parent grob X))
(note-column-extent (ly:grob-extent
note-column note-column X))
(note-column-width (interval-length note-column-extent))
(self-X (ly:grob-property-data grob 'self-alignment-X)))
(-
(*
(/ (- note-column-width word-width) 2)
(1+ (if (procedure? self-X) (self-X grob) self-X)))
preword-width)))

% This callback sets the alignment point of a LyricText grob
% to the point midway between its first and last vowels.
#(define (center-between-vowels grob)
(let* ((text (ly:grob-property-data grob 'text))
(syllable (markup->string text))
(word-position
(if (string-index syllable vowel-set)
(string-index syllable vowel-set)
0))
(word-end
(if (string-index-right syllable vowel-set)
(+ (string-index-right syllable vowel-set) 1)
(string-length syllable)))
(preword (substring syllable 0 word-position))
(word (substring syllable word-position word-end))
(preword-width (width grob preword))
(word-width (width grob
(if (string-null? syllable) text word)))
(note-column (ly:grob-parent grob X))
(note-column-extent (ly:grob-extent
note-column note-column X))
(note-column-width (interval-length note-column-extent))
(self-X (ly:grob-property-data grob 'self-alignment-X)))

(-
(*
(/ (- note-column-width word-width) 2)
(1+ (if (procedure? self-X) (self-X grob) self-X)))
preword-width)))

% Helper functions that use the above code:
cvs = \once \override LyricText.X-offset = #center-between-vowels
cfv = \once \override LyricText.X-offset = #center-on-first-vowel

\fixed c' {
\*8 { f2 f }
% The command \* requires
% version 2.25 or later.
% For version 2.24, use
% \repeat unfold 8
}

\addlyrics {
\cfv piste piste
\cfv “O—!!!” “O—!!!”
\cvs “O—!!!” “O—!!!”
\cfv blessed blessed
\cfv heaven heaven
\cvs heav’n heav’n
\cvs youths youths
\cvs each each
}
</lilypond>

If you want to apply one of these functions globally, you can place either of the following in your <code>\layout</code> block:
<br>
<code>\override Score.LyricText.X-offset = #center-between-vowels
</code>
<br>
<code>\override Score.LyricText.X-offset = #center-on-first-vowel</code>

If you then need to switch off the function locally, use <code>\once \revert LyricText.X-offset</code>.
[[Category:Vocal music]]
[[Category:Text]]
[[Category:Tweaks and overrides]]
[[Category:Scheme]]
[[Category:Spacing]]
[[Category:Snippet]]

Main Page

Ksnortum — Sat, 25 Apr 2026 13:57:55 GMT

2.24 is no longer the current stable release

← Older revision		Revision as of 13:57, 25 April 2026
Line 3:		Line 3:
	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.		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.

	Most snippets are set up to use the ~~current~~ 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!

Diagram for Recorder baroque in F and C

MartialR — Thu, 23 Apr 2026 18:38:41 GMT

← Older revision		Revision as of 18:38, 23 April 2026
Line 5:		Line 5:
	cI cII cIII dI dII dIII etc.		cI cII cIII dI dII dIII etc.

	<lilypond version="2.24">		<lilypond version="2.24.4">
	\language "english"		\language "english"
	%{		%{

Indenting individual systems

137.248.70.14 — Thu, 23 Apr 2026 12:27:22 GMT

Update LilyPond version

← Older revision		Revision as of 12:27, 23 April 2026
Line 10:		Line 10:
	* The code is not protected against multiple calls per system break.		* The code is not protected against multiple calls per system break.

	<lilypond version="2.24" full>		<lilypond version="2.26" full="">
	%%%%%%%% HEADER %%%%%%%%		%%%%%%%% HEADER %%%%%%%%
	%		%

User talk:Rudi Guggt

Manuela — Thu, 16 Apr 2026 17:32:15 GMT

Deutsches Forum nicht erreichbar

← Older revision		Revision as of 17:32, 16 April 2026
(One intermediate revision by the same user not shown)
Line 35:		Line 35:

	Hallo Rudi, ich bin es wieder mit einem Forumsproblem. Kommst du rein? Ich bekomme nur die Fehlermeldung, dass der Server nicht erreichbar ist [[User:Manuela\|Manuela]] ([[User talk:Manuela\|talk]]) 18:08, 14 April 2026 (UTC)		Hallo Rudi, ich bin es wieder mit einem Forumsproblem. Kommst du rein? Ich bekomme nur die Fehlermeldung, dass der Server nicht erreichbar ist [[User:Manuela\|Manuela]] ([[User talk:Manuela\|talk]]) 18:08, 14 April 2026 (UTC)
			:Hat sich inzwischen erledigt [[User:Manuela\|Manuela]] ([[User talk:Manuela\|talk]]) 17:32, 16 April 2026 (UTC)

Chord with ties and interval bigger than a fifth (tie fix)

Ksnortum — Wed, 15 Apr 2026 20:11:17 GMT

"Full" layout not necessary

← Older revision		Revision as of 20:11, 15 April 2026
Line 4:		Line 4:
	This is bug issue 1126 Tie positioning not as expected.		This is bug issue 1126 Tie positioning not as expected.

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

Time signature with alternate in parentheses

Lemzwerg — Wed, 15 Apr 2026 04:35:44 GMT

Aaand another improvement.

← Older revision		Revision as of 04:35, 15 April 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	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 is ~~derived from~~ the ~~parenthesize~~-time ~~snippet, adding an unparenthesized fraction in front of the parenthesized one~~.		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">		<lilypond version="2.24">
	~~%% http://lsr.di.unimi.it/LSR/Item?id~~=~~782~~		timeP =
			#(define-music-function (t tp) (list? list?)
	#(define ((time-parenthesized-time ~~up down upp downp~~) grob)		(define ((time-parenthesized-time t tp) grob)
	(grob-interpret-markup grob		(let ((m1 (grob-interpret-markup
	(markup #:~~override '(baseline~~-~~skip . 0~~) ~~#:number~~		grob (markup #:compound-meter t)))
	(~~#:line~~ (		(m2 (grob-interpret-markup
	(#:~~center~~-~~column (up down~~))		grob (markup #:compound-meter tp))))
	#:~~vcenter "("~~		(ly:stencil-combine-at-edge
	(~~#:center~~-~~column (upp downp)~~)		m1 X RIGHT
	~~#:vcenter ")"~~ )))))		(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' {		\relative c' {
	\~~override Staff.TimeSignature.stencil =~~ #(~~time-parenthesized-time "~~3~~" "~~4~~" "~~6~~" "~~8")		\timeP #'(3 4) #'(6 8) \time 3/4
	\time 3/4		b8 b8 gis8 gis4 gis8 \|
	b8 b8 gis8 gis4 gis8		\timeP #'(4 4) #'(3 2 3 8) \time 4/4
			b4. b4 b4.
	}		}
	</lilypond>		</lilypond>

User talk:Rudi Guggt

Manuela — Tue, 14 Apr 2026 18:08:28 GMT

Deutsches Forum nicht erreichbar: new section

← Older revision		Revision as of 18:08, 14 April 2026
Line 31:		Line 31:
	::::Inzwischen komme ich wieder rein [[User:Manuela\|Manuela]] ([[User talk:Manuela\|talk]]) 22:23, 20 February 2026 (UTC)		::::Inzwischen komme ich wieder rein [[User:Manuela\|Manuela]] ([[User talk:Manuela\|talk]]) 22:23, 20 February 2026 (UTC)
	:::::Ebenso, danke. -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 04:09, 21 February 2026 (UTC)		:::::Ebenso, danke. -- [[User:Lemzwerg\|Lemzwerg]] ([[User talk:Lemzwerg\|talk]]) 04:09, 21 February 2026 (UTC)

			== Deutsches Forum nicht erreichbar ==

			Hallo Rudi, ich bin es wieder mit einem Forumsproblem. Kommst du rein? Ich bekomme nur die Fehlermeldung, dass der Server nicht erreichbar ist [[User:Manuela\|Manuela]] ([[User talk:Manuela\|talk]]) 18:08, 14 April 2026 (UTC)

User talk:Ksnortum

Lemzwerg — Fri, 10 Apr 2026 15:44:01 GMT

Please be careful while using 'Edit': Reply

← Older revision		Revision as of 15:44, 10 April 2026
Line 5:		Line 5:
	:Got it, thanks. [[User:Ksnortum\|Ksnortum]] ([[User talk:Ksnortum\|talk]]) 19:34, 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)		:...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)

User talk:Ksnortum

Ksnortum — Fri, 10 Apr 2026 14:58:19 GMT

Please be careful while using 'Edit': Reply

← Older revision		Revision as of 14:58, 10 April 2026
(One intermediate revision by the same user not shown)
Line 2:		Line 2:

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

Clef change at the beginning of a piece (alternative)

Lemzwerg — Wed, 08 Apr 2026 17:29:32 GMT

← Older revision		Revision as of 17:29, 8 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	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]].		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]].

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

	[[Category:Staff notation]]		[[Category:Staff notation]]

Clef change at the beginning of a piece

Lemzwerg — Wed, 08 Apr 2026 17:28:29 GMT

← Older revision		Revision as of 17:28, 8 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	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]].		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]].

	<~~span></span>~~		<lilypond version="2.24">
	\version "2.24"		%% http://lsr.di.unimi.it/LSR/Item?id=792
			%% see also http://lilypond.org/doc/stable/Documentation/notation/displaying-pitches
	%% ~~<nowiki>~~http://lsr.di.unimi.it/LSR/Item?id=792~~</nowiki>~~
	%% see also ~~<nowiki>~~http://lilypond.org/doc/stable/Documentation/notation/displaying-pitches~~</nowiki>~~		% Append markup in the text property to the grob
			#(define (append-markup grob old-stencil)
	% Append markup in the text property to the grob		(ly:stencil-combine-at-edge
	#(define (append-markup grob old-stencil)		old-stencil X RIGHT (ly:text-interface::print grob)))
	(ly:stencil-combine-at-edge
	old-stencil X RIGHT (ly:text-interface::print grob)))		trebleToBass = {
			\clef bass
	trebleToBass = {		% Fake staff clef appearance
	\clef bass		\once \override Staff.Clef.glyph-name = #"clefs.G"
	% Fake staff clef appearance		\once \override Staff.Clef.Y-offset = #-1
	\once \override Staff.Clef.glyph-name = #"clefs.G"		% Make sure any key signatures will printed with respect to
	\once \override Staff.Clef.Y-offset = #-1		% correct middle c position expected for treble clef
	% Make sure any key signatures will printed with respect to		\once \set Staff.middleCClefPosition = -6
	% correct middle c position expected for treble clef		% Append change clef to the time signature
	\once \set Staff.middleCClefPosition = -6		\once \override Staff.TimeSignature.text = \markup {
	% Append change clef to the time signature		\hspace #1.2
	\once \override Staff.TimeSignature.text = \markup {		\raise #1
	\hspace #1.2		\musicglyph "clefs.F_change"
	\raise #1		}
	\musicglyph "clefs.F_change"		\once \override Staff.TimeSignature.stencil = #(lambda (grob)
	}		(append-markup grob (ly:time-signature::print grob)))
	\once \override Staff.TimeSignature.stencil = #(lambda (grob)		}
	(append-markup grob (ly:time-signature::print grob)))
	}		bassToTreble = {
			\clef treble
	bassToTreble = {		% Fake staff clef appearance
	\clef treble		\once \override Staff.Clef.glyph-name = #"clefs.F"
	% Fake staff clef appearance		\once \override Staff.Clef.Y-offset = #1
	\once \override Staff.Clef.glyph-name = #"clefs.F"		% Make sure any key signatures will printed with respect to
	\once \override Staff.Clef.Y-offset = #1		% correct middle c position expected for bass clef
	% Make sure any key signatures will printed with respect to		\once \set Staff.middleCClefPosition = 6
	% correct middle c position expected for bass clef		% Append change clef to the time signature
	\once \set Staff.middleCClefPosition = 6		\once \override Staff.TimeSignature.text = \markup {
	% Append change clef to the time signature		\hspace #1.2
	\once \override Staff.TimeSignature.text = \markup {		\lower #1
	\hspace #1.2		\musicglyph "clefs.G_change"
	\lower #1		}
	\musicglyph "clefs.G_change"		\once \override Staff.TimeSignature.stencil = #(lambda (grob)
	}		(append-markup grob (ly:time-signature::print grob)))
	\once \override Staff.TimeSignature.stencil = #(lambda (grob)		}
	(append-markup grob (ly:time-signature::print grob)))
	}		\relative c {
			\trebleToBass
	\relative c {		\key f \major
	\trebleToBass		c4 d e f
	\key f \major		% This should not be visible
	c4 d e f		\clef bass
	% This should not be visible		g a b c
	\clef bass		% This should be visible
	g a b c		\clef treble
	% This should be visible		d e f g
	\clef treble		}
	d e f g		</lilypond>
	}
	~~<span>~~</~~span~~>

	[[Category:Staff notation]]		[[Category:Staff notation]]

User talk:Ksnortum

Lemzwerg — Wed, 08 Apr 2026 17:26:25 GMT

Please be careful while using 'Edit': new section

New page

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

Initial clef change

Lemzwerg — Wed, 08 Apr 2026 17:22:41 GMT

Show changes

Clef change at the beginning of a piece

Ksnortum — Wed, 08 Apr 2026 16:47:08 GMT

Add "See also"

← Older revision		Revision as of 16:47, 8 April 2026
Line 1:		Line 1:
	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.		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">		<span></span>
	%% http://lsr.di.unimi.it/LSR/Item?id=792		\version "2.24"
	%% see also http://lilypond.org/doc/stable/Documentation/notation/displaying-pitches
			%% <nowiki>http://lsr.di.unimi.it/LSR/Item?id=792</nowiki>
	% Append markup in the text property to the grob		%% see also <nowiki>http://lilypond.org/doc/stable/Documentation/notation/displaying-pitches</nowiki>
	#(define (append-markup grob old-stencil)
	(ly:stencil-combine-at-edge		% Append markup in the text property to the grob
	old-stencil X RIGHT (ly:text-interface::print grob)))		#(define (append-markup grob old-stencil)
			(ly:stencil-combine-at-edge
	trebleToBass = {		old-stencil X RIGHT (ly:text-interface::print grob)))
	\clef bass
	% Fake staff clef appearance		trebleToBass = {
	\once \override Staff.Clef.glyph-name = #"clefs.G"		\clef bass
	\once \override Staff.Clef.Y-offset = #-1		% Fake staff clef appearance
	% Make sure any key signatures will printed with respect to		\once \override Staff.Clef.glyph-name = #"clefs.G"
	% correct middle c position expected for treble clef		\once \override Staff.Clef.Y-offset = #-1
	\once \set Staff.middleCClefPosition = -6		% Make sure any key signatures will printed with respect to
	% Append change clef to the time signature		% correct middle c position expected for treble clef
	\once \override Staff.TimeSignature.text = \markup {		\once \set Staff.middleCClefPosition = -6
	\hspace #1.2		% Append change clef to the time signature
	\raise #1		\once \override Staff.TimeSignature.text = \markup {
	\musicglyph "clefs.F_change"		\hspace #1.2
	}		\raise #1
	\once \override Staff.TimeSignature.stencil = #(lambda (grob)		\musicglyph "clefs.F_change"
	(append-markup grob (ly:time-signature::print grob)))		}
	}		\once \override Staff.TimeSignature.stencil = #(lambda (grob)
			(append-markup grob (ly:time-signature::print grob)))
	bassToTreble = {		}
	\clef treble
	% Fake staff clef appearance		bassToTreble = {
	\once \override Staff.Clef.glyph-name = #"clefs.F"		\clef treble
	\once \override Staff.Clef.Y-offset = #1		% Fake staff clef appearance
	% Make sure any key signatures will printed with respect to		\once \override Staff.Clef.glyph-name = #"clefs.F"
	% correct middle c position expected for bass clef		\once \override Staff.Clef.Y-offset = #1
	\once \set Staff.middleCClefPosition = 6		% Make sure any key signatures will printed with respect to
	% Append change clef to the time signature		% correct middle c position expected for bass clef
	\once \override Staff.TimeSignature.text = \markup {		\once \set Staff.middleCClefPosition = 6
	\hspace #1.2		% Append change clef to the time signature
	\lower #1		\once \override Staff.TimeSignature.text = \markup {
	\musicglyph "clefs.G_change"		\hspace #1.2
	}		\lower #1
	\once \override Staff.TimeSignature.stencil = #(lambda (grob)		\musicglyph "clefs.G_change"
	(append-markup grob (ly:time-signature::print grob)))		}
	}		\once \override Staff.TimeSignature.stencil = #(lambda (grob)
			(append-markup grob (ly:time-signature::print grob)))
	\relative c {		}
	\trebleToBass
	\key f \major		\relative c {
	c4 d e f		\trebleToBass
	% This should not be visible		\key f \major
	\clef bass		c4 d e f
	g a b c		% This should not be visible
	% This should be visible		\clef bass
	\clef treble		g a b c
	d e f g		% This should be visible
	}		\clef treble
	</~~lilypond~~>		d e f g
			}
			<span></span>

	[[Category:Staff notation]]		[[Category:Staff notation]]

Initial clef change

Ksnortum — Wed, 08 Apr 2026 16:45:47 GMT

Add "See also"

Show changes

Clef change at the beginning of a piece (alternative)

Ksnortum — Wed, 08 Apr 2026 16:44:01 GMT

Add "See also"

← Older revision		Revision as of 16:44, 8 April 2026
Line 1:		Line 1:
	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.		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">		<span></span>
	\relative c' {		\version "2.24"
	%% Start with a bass ~~clef~~ :
	\clef bass		\relative c' {
	%% Use a hidden grace note:		%% Start with a bass clef :
	\once\hideNotes\grace c64		\clef bass
	%% Adjust the clef spacing:		%% Use a hidden grace note:
	\once\override Staff.Clef.X-extent = #'(1 . 2)		\once\hideNotes\grace c64
	%% Put in the treble clef:		%% Adjust the clef spacing:
	\clef treble		\once\override Staff.Clef.X-extent = #'(1 . 2)
	c4 c c c \| c1		%% Put in the treble clef:
	}		\clef treble
	</~~lilypond~~>		c4 c c c \| c1
			}
			<span></span>

	[[Category:Staff notation]]		[[Category:Staff notation]]

User:Alain

Alain — Tue, 07 Apr 2026 18:25:44 GMT

User account Alain was created

Coloring elements of notation

Jean Abou Samra — Tue, 07 Apr 2026 11:37:32 GMT

← Older revision		Revision as of 11:37, 7 April 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	Individual objects may be assigned colors. Several pre-defined colors are available; they are exhaustively listed in the Notation Reference.		Individual objects may be assigned colors. Several pre-defined colors are available; they are [https://lilypond.org/doc/v2.25/Documentation/notation/list-of-colors.html exhaustively listed] in the Notation Reference.

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

	\relative c'' {		\relative c'' {
	\override NoteHead.color = #red		\override NoteHead.color = #red

Splitting chords

Jean Abou Samra — Tue, 07 Apr 2026 09:51:33 GMT

← Older revision		Revision as of 09:51, 7 April 2026
Line 1:		Line 1:
	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.		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.		Note that these functions don't support <code>q</code> to repeat the last chord.

	<lilypond version="2.24">		<lilypond version="2.24">
Line 11:		Line 11:

	keepOnlyFirstNote =		keepOnlyFirstNote =
	#(define-music-function (~~parser location~~ music) (ly:music?)		#(define-music-function (music) (ly:music?)
	(music-map		(music-map
	(lambda (evt)		(lambda (evt)
Line 25:		Line 25:

	deleteFirstNote =		deleteFirstNote =
	#(define-music-function (~~parser location~~ music) (ly:music?)		#(define-music-function (music) (ly:music?)
	(music-map		(music-map
	(lambda (evt)		(lambda (evt)

Coloring individual staff lines

Jean Abou Samra — Tue, 07 Apr 2026 09:46:10 GMT

← Older revision		Revision as of 09:46, 7 April 2026
Line 2:		Line 2:

	The <code>StaffSymbol</code> callback <code>color-staff-lines</code> takes a set of colors (using LilyPond's predefined colors or the functions <code>x11-color</code> and <code>rgb-color</code>) which are applied to each staff line in turn starting with the fifth line (for a standard staff), or each item in the list for custom staves defined with <code>line-positions</code>. To signal that a particular line between colored lines should remain black, use <code>#f</code>.		The <code>StaffSymbol</code> callback <code>color-staff-lines</code> takes a set of colors (using LilyPond's predefined colors or the functions <code>x11-color</code> and <code>rgb-color</code>) which are applied to each staff line in turn starting with the fifth line (for a standard staff), or each item in the list for custom staves defined with <code>line-positions</code>. To signal that a particular line between colored lines should remain black, use <code>#f</code>.

			Contributed by Neil Puttock.

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

	~~%LSR This snippet was contributed by Neil Puttock~~

	#(define-public ((color-staff-lines . rest) grob)		#(define-public ((color-staff-lines . rest) grob)

Clef change at the beginning of a piece (alternative)

Jean Abou Samra — Tue, 07 Apr 2026 09:44:26 GMT

← Older revision		Revision as of 09:44, 7 April 2026
Line 2:		Line 2:

	<lilypond version="2.24">		<lilypond version="2.24">
	~~% LSR: http://lsr.di.unimi.it/LSR/Item?id=956~~
	~~%% => http://lilypond.1069038.n5.nabble.com/Clef-change-at-the-beginning-of-a-staff-tc168090.html~~
	~~%% see also: http://lsr.di.unimi.it/LSR/Item?id=792~~

	\relative c' {		\relative c' {
	%% Start with a bass clef :		%% Start with a bass clef :

Splitting chords

Lemzwerg — Tue, 07 Apr 2026 03:53:53 GMT

← Older revision		Revision as of 03:53, 7 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	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.		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.		Note that these functions don't support <samp>q</samp> to repeat the last chord.

	<~~span></span>~~		<lilypond version="2.24">
	\version "2.24"		#(define (has-duration? music)
			(ly:duration? (ly:music-property music 'duration)))
	#(define (has-duration? music)
	(ly:duration? (ly:music-property music 'duration)))		#(define (not-has-duration? music)
			(not (has-duration? music)))
	#(define (not-has-duration? music)
	(not (has-duration? music)))		keepOnlyFirstNote =
			#(define-music-function (parser location music) (ly:music?)
	keepOnlyFirstNote =		(music-map
	#(define-music-function (parser location music) (ly:music?)		(lambda (evt)
	(music-map		(when (eq? 'EventChord (ly:music-property evt 'name))
	(lambda (evt)
	(when (eq? 'EventChord (ly:music-property evt 'name))
	(let ((elts (ly:music-property evt 'elements)))		(let ((elts (ly:music-property evt 'elements)))
	(when (has-duration? (car elts))		(when (has-duration? (car elts))
Line 23:		Line 21:
	(cons (car elts)		(cons (car elts)
	(filter not-has-duration? (cdr elts)))))))		(filter not-has-duration? (cdr elts)))))))
	evt)		evt)
	music))		music))

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


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

			\markup { Music with chords }
	\markup { Music with chords }		\new Staff \music
	\new Staff \music
			\markup { Music split into two staves }
	\markup { Music split into two ~~staffs~~ }		<<
	<<		\new Staff \deleteFirstNote \music
	\new Staff \deleteFirstNote \music		\new Staff \keepOnlyFirstNote \music
	\new Staff \keepOnlyFirstNote \music		>>
	>>		</lilypond>
	~~<span>~~</~~span~~>

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

Splitting chords

Ksnortum — Mon, 06 Apr 2026 22:09:35 GMT

Node -> Note

← Older revision		Revision as of 22:09, 6 April 2026
Line 1:		Line 1:
	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.		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.		Note that these function don't support <samp>q</samp> to repeat the last chord.

	<~~lilypond~~ version="2.24">		<span></span>
	#(define (has-duration? music)		\version "2.24"
	(ly:duration? (ly:music-property music 'duration)))
			#(define (has-duration? music)
	#(define (not-has-duration? music)		(ly:duration? (ly:music-property music 'duration)))
	(not (has-duration? music)))
			#(define (not-has-duration? music)
	keepOnlyFirstNote =		(not (has-duration? music)))
	#(define-music-function (parser location music) (ly:music?)
	(music-map		keepOnlyFirstNote =
	(lambda (evt)		#(define-music-function (parser location music) (ly:music?)
	(when (eq? 'EventChord (ly:music-property evt 'name))		(music-map
	(let ((elts (ly:music-property evt 'elements)))		(lambda (evt)
	(when (has-duration? (car elts))		(when (eq? 'EventChord (ly:music-property evt 'name))
	(ly:music-set-property!		(let ((elts (ly:music-property evt 'elements)))
	evt 'elements		(when (has-duration? (car elts))
	(cons (car elts)		(ly:music-set-property!
	(filter not-has-duration? (cdr elts)))))))		evt 'elements
	evt)		(cons (car elts)
	music))		(filter not-has-duration? (cdr elts)))))))
			evt)
	deleteFirstNote =		music))
	#(define-music-function (parser location music) (ly:music?)
	(music-map		deleteFirstNote =
	(lambda (evt)		#(define-music-function (parser location music) (ly:music?)
	(when (eq? 'EventChord (ly:music-property evt 'name))		(music-map
	(let ((elts (ly:music-property evt 'elements)))		(lambda (evt)
	(when (has-duration? (car elts))		(when (eq? 'EventChord (ly:music-property evt 'name))
	(ly:music-set-property! evt 'elements (cdr elts)))))		(let ((elts (ly:music-property evt 'elements)))
	evt)		(when (has-duration? (car elts))
	music))		(ly:music-set-property! evt 'elements (cdr elts)))))
			evt)
			music))
	music = \relative c' {
	<c e>4-> <d f>( <b g'>) <c e>-. g2 c2
	}		music = \relative c' {
			<c e>4-> <d f>( <nowiki><b g'>) <c e>-. g2 c2</nowiki>
			}
	\markup { Music with chords }
	\new Staff \music
			\markup { Music with chords }
	\markup { Music split into two staffs }		\new Staff \music
	<<
	\new Staff \deleteFirstNote \music		\markup { Music split into two staffs }
	\new Staff \keepOnlyFirstNote \music		<<
	>>		\new Staff \deleteFirstNote \music
	</~~lilypond~~>		\new Staff \keepOnlyFirstNote \music
			>>
			<span></span>

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

User talk:MartialR

MartialR — Sun, 05 Apr 2026 09:22:35 GMT

Recorder diagrams: Reply

← Older revision		Revision as of 09:22, 5 April 2026
Line 2:		Line 2:

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

			:Hi, thanks for your message and advice. I'll think about optimizing with Scheme code. [[User:MartialR\|MartialR]] ([[User talk:MartialR\|talk]]) 09:22, 5 April 2026 (UTC)

Diagram for Recorder baroque in F and C

MartialR — Sun, 05 Apr 2026 09:19:13 GMT

← Older revision		Revision as of 09:19, 5 April 2026
Line 906:		Line 906:
	}		}
	}		}
	%End ~~sample~~ for F and C Baroque Recorder		%End example for F and C Baroque Recorder
	%===========================================		%===========================================

	</lilypond>		</lilypond>

Splitting chords

Lemzwerg — Sun, 05 Apr 2026 09:09:04 GMT

Formatting, improved docstring

← Older revision		Revision as of 09:09, 5 April 2026
Line 1:		Line 1:
	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 ~~splits~~ a chord sequence into two ~~separated~~ voices: ~~the first one built on~~ the first note (usually the lowest) of every chord and ~~the other on~~ the remaining notes. ~~It works well in 2.24.4 and even in 2.25.35. I find it very useful. It also preserves articulations and slurs. The only drawback: it doesn~~'t ~~work if you use «q»~~ to repeat last chord.		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">		<lilypond version="2.24">
			#(define (has-duration? music)
			(ly:duration? (ly:music-property music 'duration)))

	~~#(define (has-duration? music)~~		#(define (not-has-duration? music)
	~~(ly:duration? (ly:music-property music 'duration)))~~		(not (has-duration? music)))

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


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

	\markup { Music with chords }
	\new Staff \music		\markup { Music with chords }
	\markup { Music ~~splitted in 2~~ staffs }		\new Staff \music
	<<
	\new Staff \deleteFirstNote \music		\markup { Music split into two staffs }
	\new Staff \~~keepsOnlyFirstNote~~ \music		<<
	>>		\new Staff \deleteFirstNote \music
			\new Staff \keepOnlyFirstNote \music
			>>
	</lilypond>		</lilypond>


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

Diagram for Recorder baroque in F and C

MartialR — Sun, 05 Apr 2026 08:32:24 GMT

Show changes

Talk:Diagram for Recorder baroque in F and C

MartialR — Sun, 05 Apr 2026 07:08:22 GMT

Better markup definitions: Reply

← Older revision		Revision as of 07:08, 5 April 2026
Line 2:		Line 2:

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

			:Hi
			:thank for your message and advice.
			:I'll think about optimizing this code with Scheme function [[User:MartialR\|MartialR]] ([[User talk:MartialR\|talk]]) 07:08, 5 April 2026 (UTC)

Diagram for Recorder baroque in F and C

MartialR — Sun, 05 Apr 2026 07:04:49 GMT

Show changes

← Older revision		Revision as of 15:44, 10 April 2026
Line 5:		Line 5:
	:Got it, thanks. [[User:Ksnortum\|Ksnortum]] ([[User talk:Ksnortum\|talk]]) 19:34, 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)		:...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)