Horizontally aligning custom dynamics like “più f” - Revision history

Lemzwerg at 05:33, 15 January 2026

2026-01-15T05:33:20Z

← Older revision		Revision as of 05:33, 15 January 2026
Line 3:		Line 3:
	To correctly align the “sempre '''pp'''” horizontally so that it is aligned as if it were only the \pp, there are several approaches:		To correctly align the “sempre '''pp'''” horizontally so that it is aligned as if it were only the \pp, there are several approaches:

	* Simply use <code>\once\override DynamicText.X-offset = #-9.2</code> before the note with the dynamics to manually shift it to the correct position. Drawback: This has to be done manually each time you use that dynamic markup...		* Simply use <code>\once \override DynamicText.X-offset = #-9.2</code> before the note with the dynamics to manually shift it to the correct position. Drawback: This has to be done manually each time you use that dynamic markup...
	* Add some padding (<code>#:hspace 7.1</code>) into the definition of your custom dynamic mark so that after LilyPond center-aligns it, it is already correctly aligned. Drawback: The padding really takes up that space and does not allow any other markup or dynamics to be shown in that position.		* Add some padding (<code>#:hspace 7.1</code>) into the definition of your custom dynamic mark so that after LilyPond center-aligns it, it is already correctly aligned. Drawback: The padding really takes up that space and does not allow any other markup or dynamics to be shown in that position.
	* Shift the dynamic script <code>\once\override ... .X-offset = ...</code>. Drawback: <code>\once\override</code> is needed for every invocation!		* Shift the dynamic script <code>\once \override ... .X-offset = ...</code>. Drawback: <code>\once \override</code> is needed for every invocation!
	* Set the dimensions of the additional text to 0 (using <code>#:with-dimensions '(0 . 0) '(0 . 0)</code>). Drawback: For LilyPond, “sempre” has no extent now. This means it might put other stuff there, causing collisions (which are not detected by LilyPond's collision detection algorithm!). There also seems to be some spacing, so it is not exactly the same alignment as without the additional text.		* Set the dimensions of the additional text to 0 (using <code>#:with-dimensions '(0 . 0) '(0 . 0)</code>). Drawback: For LilyPond, “sempre” has no extent now. This means it might put other stuff there, causing collisions (which are not detected by LilyPond's collision detection algorithm!). There also seems to be some spacing, so it is not exactly the same alignment as without the additional text.
	* Add an explicit shift directly inside the scheme function for the dynamic script.		* Add an explicit shift directly inside the scheme function for the dynamic script.
	* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.		* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.

Lemzwerg: Simplify

2025-12-03T14:33:20Z

Simplify

← Older revision		Revision as of 14:33, 3 December 2025
Line 10:		Line 10:
	* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.		* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.

	<lilypond version="2.24" ~~full~~>		<lilypond version="2.24">
	\paper {		\paper {
	ragged-right = ##f		ragged-right = ##f
	indent = 2.5\cm		indent = 5\cm
	~~tagline = ##f~~
	}		}

Line 79:		Line 78:

	\new StaffGroup <<		\new StaffGroup <<
	\new Staff ~~= "s"~~ \with { instrumentName = ~~\markup \column { Normal }~~ }		\new Staff \with { instrumentName = "standard" }
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
	c4\pp c\p c c \| c\ff c c\pp c		c4\pp c\p c c \| c\ff c c\pp c
	}		}
	>>		\new Staff \with {instrumentName = "normal markup" }
	\new Staff ~~= "sMarkup"~~ \with {
	instrumentName = \markup ~~\column { Normal markup }~~
	}
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
	c4-\semppMarkup c\p c c \| c\ff c c-\semppMarkup c		c4-\semppMarkup c\p c c \| c\ff c c-\semppMarkup c
	}		}
	>>		\new Staff \with { instrumentName = "explicit shifting" }
	\new Staff ~~= "sK"~~ \with {
	instrumentName = ~~\markup \column { Explicit~~ shifting }
	}
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
Line 107:		Line 97:
	c4\semppK c		c4\semppK c
	}		}
	>>		\new Staff \with { instrumentName = "right padding" }
	\new Staff ~~= "sT"~~ \with {
	instrumentName = ~~\markup \column { Right~~ padding }
	}
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
	c4\semppT c\p c c \| c\ff c c\semppT c		c4\semppT c\p c c \| c\ff c c\semppT c
	}		}
	>>		\new Staff \with { instrumentName = "set dimension to zero" }
	\new Staff ~~= "sM"~~ \with {
	instrumentName = ~~\markup \column { Set~~ dimension "to zero" }
	}
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
	c4\semppM c\p c c \| c\ff c c\semppM c		c4\semppM c\p c c \| c\ff c c\semppM c
	}		}
	>>		\new Staff \with { instrumentName = "shift inside dynamics" }
	\new Staff ~~= "sG"~~ \with {
	instrumentName = ~~\markup \column { Shift~~ inside dynamics}
	}
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
	c4\semppG c\p c c \| c\ff c c\semppG c		c4\semppG c\p c c \| c\ff c c\semppG c
	}		}
	>>		\new Staff \with { instrumentName = "alignment inside dynamics" }
	\new Staff ~~= "sMII"~~ \with {
	instrumentName = ~~\markup \column { Alignment~~ inside dynamics }
	}
	<<
	\relative c'' {		\relative c'' {
	\key es \major		\key es \major
	~~% Setting to ##f (false) gives the same result~~		\override DynamicText.X-offset = #-1
	\override DynamicText.X-offset = #0
	c4\semppMII c\p c c \| c\ff c c\semppMII c		c4\semppMII c\p c c \| c\ff c c\semppMII c
	}		}
	>>
	>>		>>

Line 153:		Line 125:
	[[Category:Expressive marks]]		[[Category:Expressive marks]]
	[[Category:Tweaks and overrides]]		[[Category:Tweaks and overrides]]
	~~[[Category:Version-specific]]~~
	[[Category:Included in the official documentation]]		[[Category:Included in the official documentation]]
	[[Category:Snippet]]		[[Category:Snippet]]

Lemzwerg: Lemzwerg moved page Horizontally aligning custom dynamics (e.g. "sempre pp", "piu f", "subito p") to Horizontally aligning custom dynamics like “più f” without leaving a redirect

2025-12-03T14:17:56Z

Lemzwerg moved page Horizontally aligning custom dynamics (e.g. "sempre pp", "piu f", "subito p") to Horizontally aligning custom dynamics like “più f” without leaving a redirect

← Older revision	Revision as of 14:17, 3 December 2025
(No difference)

Lemzwerg: New category

2025-11-21T23:23:45Z

New category

← Older revision		Revision as of 23:23, 21 November 2025
Line 154:		Line 154:
	[[Category:Tweaks and overrides]]		[[Category:Tweaks and overrides]]
	[[Category:Version-specific]]		[[Category:Version-specific]]
	[[Category:Included in the official documentation]][[Category:Snippet]]		[[Category:Included in the official documentation]]
			[[Category:Snippet]]

Lemzwerg at 22:54, 21 November 2025

2025-11-21T22:54:32Z

← Older revision		Revision as of 22:54, 21 November 2025
Line 154:		Line 154:
	[[Category:Tweaks and overrides]]		[[Category:Tweaks and overrides]]
	[[Category:Version-specific]]		[[Category:Version-specific]]
	[[Category:Included in the official documentation]]		[[Category:Included in the official documentation]][[Category:Snippet]]

Jean Abou Samra: Replace version="2.24.0" with version="2.24" now that the LilyWiki extension supports auto-selecting the latest release in a stable series

2025-11-16T18:53:30Z

Replace version="2.24.0" with version="2.24" now that the LilyWiki extension supports auto-selecting the latest release in a stable series

← Older revision		Revision as of 18:53, 16 November 2025
Line 10:		Line 10:
	* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.		* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.

	<lilypond version="2.24.0" full>		<lilypond version="2.24" full>
	\paper {		\paper {
	ragged-right = ##f		ragged-right = ##f

Jean Abou Samra: Import snippet from LSR

2025-10-26T22:41:26Z

Import snippet from LSR

New page

Some dynamic expressions involve additional text, like “sempre '''pp'''”. Since dynamics are usually centered under the note, the \pp would be displayed way after the note it applies to.

To correctly align the “sempre '''pp'''” horizontally so that it is aligned as if it were only the \pp, there are several approaches:

* Simply use <code>\once\override DynamicText.X-offset = #-9.2</code> before the note with the dynamics to manually shift it to the correct position. Drawback: This has to be done manually each time you use that dynamic markup...
* Add some padding (<code>#:hspace 7.1</code>) into the definition of your custom dynamic mark so that after LilyPond center-aligns it, it is already correctly aligned. Drawback: The padding really takes up that space and does not allow any other markup or dynamics to be shown in that position.
* Shift the dynamic script <code>\once\override ... .X-offset = ...</code>. Drawback: <code>\once\override</code> is needed for every invocation!
* Set the dimensions of the additional text to 0 (using <code>#:with-dimensions '(0 . 0) '(0 . 0)</code>). Drawback: For LilyPond, “sempre” has no extent now. This means it might put other stuff there, causing collisions (which are not detected by LilyPond's collision detection algorithm!). There also seems to be some spacing, so it is not exactly the same alignment as without the additional text.
* Add an explicit shift directly inside the scheme function for the dynamic script.
* Set an explicit alignment inside the dynamic script. By default, this won't have any effect, only if one sets <code>X-offset</code>! Drawback: One needs to set <code>DynamicText.X-offset</code>, which will apply to all dynamic texts! Also, it is aligned at the right edge of the additional text, not at the center of \pp.

<lilypond version="2.24.0" full>
\paper {
ragged-right = ##f
indent = 2.5\cm
tagline = ##f
}

% Solution 1: Using a simple markup with a particular halign value
% Drawback: It's a markup, not a dynamic command, so \dynamicDown
% etc. will have no effect
semppMarkup = \markup { \halign #1.4 \italic "sempre" \dynamic "pp" }

% Solution 2: Using a dynamic script & shifting with
% \once \override ...X-offset = ..
% Drawback: \once \override needed for every invocation
semppK =
#(make-dynamic-script
(markup #:line
(#:normal-text
#:italic "sempre"
#:dynamic "pp")))

% Solution 3: Padding the dynamic script so the center-alignment
% puts it at the correct position
% Drawback: the padding really reserves the space, nothing else can be there
semppT =
#(make-dynamic-script
(markup #:line
(#:normal-text
#:italic "sempre"
#:dynamic "pp"
#:hspace 7.1)))

% Solution 4: Dynamic, setting the dimensions of the additional text to 0
% Drawback: To lilypond "sempre" has no extent, so it might put
% other stuff there => collisions
% Drawback: Also, there seems to be some spacing, so it's not exactly the
% same alignment as without the additional text
semppM =
#(make-dynamic-script
(markup #:line
(#:with-dimensions '(0 . 0) '(0 . 0)
#:right-align
#:normal-text
#:italic "sempre"
#:dynamic "pp")))

% Solution 5: Dynamic with explicit shifting inside the scheme function
semppG =
#(make-dynamic-script
(markup #:hspace 0
#:translate '(-18.85 . 0)
#:line (#:normal-text
#:italic "sempre"
#:dynamic "pp")))

% Solution 6: Dynamic with explicit alignment. This has only effect
% if one sets X-offset!
% Drawback: One needs to set DynamicText.X-offset!
% Drawback: Aligned at the right edge of the additional text,
% not at the center of pp
semppMII =
#(make-dynamic-script
(markup #:line (#:right-align
#:normal-text
#:italic "sempre"
#:dynamic "pp")))

\new StaffGroup <<
\new Staff = "s" \with { instrumentName = \markup \column { Normal } }
<<
\relative c'' {
\key es \major
c4\pp c\p c c | c\ff c c\pp c
}
>>
\new Staff = "sMarkup" \with {
instrumentName = \markup \column { Normal markup }
}
<<
\relative c'' {
\key es \major
c4-\semppMarkup c\p c c | c\ff c c-\semppMarkup c
}
>>
\new Staff = "sK" \with {
instrumentName = \markup \column { Explicit shifting }
}
<<
\relative c'' {
\key es \major
\once \override DynamicText.X-offset = #-9.2
c4\semppK c\p c c
c4\ff c
\once \override DynamicText.X-offset = #-9.2
c4\semppK c
}
>>
\new Staff = "sT" \with {
instrumentName = \markup \column { Right padding }
}
<<
\relative c'' {
\key es \major
c4\semppT c\p c c | c\ff c c\semppT c
}
>>
\new Staff = "sM" \with {
instrumentName = \markup \column { Set dimension "to zero" }
}
<<
\relative c'' {
\key es \major
c4\semppM c\p c c | c\ff c c\semppM c
}
>>
\new Staff = "sG" \with {
instrumentName = \markup \column { Shift inside dynamics}
}
<<
\relative c'' {
\key es \major
c4\semppG c\p c c | c\ff c c\semppG c
}
>>
\new Staff = "sMII" \with {
instrumentName = \markup \column { Alignment inside dynamics }
}
<<
\relative c'' {
\key es \major
% Setting to ##f (false) gives the same result
\override DynamicText.X-offset = #0
c4\semppMII c\p c c | c\ff c c\semppMII c
}
>>
>>

\layout { \override Staff.InstrumentName.self-alignment-X = #LEFT }
</lilypond>

[[Category:Expressive marks]]
[[Category:Tweaks and overrides]]
[[Category:Version-specific]]
[[Category:Included in the official documentation]]