Slanted parentheses around dynamics - Revision history

Jean Abou Samra: Conform to the format of snippets included in the official documentation

2026-02-01T18:38:12Z

Conform to the format of snippets included in the official documentation

← Older revision		Revision as of 18:38, 1 February 2026
Line 1:		Line 1:
	~~Although the~~ easiest way to ~~add parentheses to a dynamic mark~~ is to use a <code>\~~markup~~</code> ~~block~~, ~~this method has a downside: the created objects behave like text markups and not like dynamics~~.		The easiest way to parenthesize dynamics is to use the normal <code>\parenthesize</code> command and adjust the font size, e.g., <code>{ c'4\tweak Parentheses.font-size 2 \parenthesize \f }</code>. However, this results in upright parentheses, while dynamic marks are normally slanted. This snippet gives a method to make the parentheses slanted as well.

	~~However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference)~~, ~~combined with the~~ <code>~~make~~-~~dynamic-script~~</code> ~~function~~. This ~~way,~~ the ~~markup is regarded~~ as ~~a dynamic and therefore remains compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>~~.

	<lilypond version="2.24">		<lilypond version="2.24">
Line 17:		Line 15:
	c4\paren\f c c \dynamicUp c\paren\p		c4\paren\f c c \dynamicUp c\paren\p
	}		}
	~~</lilypond>~~

	~~Another way to do parenthesize dynamics is to use the <code>\parenthesize</code> command, although this way doesn't give you the fine-tuning of the dynamic text.~~

	~~<lilypond version="2.24">~~
	~~\relative c'' {~~
	~~\override Parentheses.font-size = #2~~
	~~c4\parenthesize\f c c \dynamicUp c\parenthesize\p~~
	}
	</lilypond>		</lilypond>

Jean Abou Samra: Jean Abou Samra moved page Creating “real” parenthesized dynamics to Slanted parentheses around dynamics

2026-02-01T18:31:57Z

Jean Abou Samra moved page Creating “real” parenthesized dynamics to Slanted parentheses around dynamics

← Older revision	Revision as of 18:31, 1 February 2026
(No difference)

Ksnortum: Another way to parenthesize dynamic text w/o Scheme code

2026-02-01T16:16:15Z

Another way to parenthesize dynamic text w/o Scheme code

← Older revision		Revision as of 16:16, 1 February 2026
Line 17:		Line 17:
	c4\paren\f c c \dynamicUp c\paren\p		c4\paren\f c c \dynamicUp c\paren\p
	}		}
			</lilypond>

			Another way to do parenthesize dynamics is to use the <code>\parenthesize</code> command, although this way doesn't give you the fine-tuning of the dynamic text.

			<lilypond version="2.24">
			\relative c'' {
			\override Parentheses.font-size = #2
			c4\parenthesize\f c c \dynamicUp c\parenthesize\p
			}
	</lilypond>		</lilypond>

Lemzwerg at 08:44, 28 December 2025

2025-12-28T08:44:06Z

← Older revision		Revision as of 08:44, 28 December 2025
Line 1:		Line 1:
	Although the easiest way to add parentheses to a dynamic mark is to use a <code>\markup</code> block, this method has a downside: the created objects ~~will~~ behave like text markups, and not like dynamics.		Although the easiest way to add parentheses to a dynamic mark is to use a <code>\markup</code> block, this method has a downside: the created objects behave like text markups and not like dynamics.

	However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference), combined with the <code>make-dynamic-script</code> function. This way, the markup ~~will be~~ regarded as a dynamic, and therefore ~~will remain~~ compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>.		However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference), combined with the <code>make-dynamic-script</code> function. This way, the markup is regarded as a dynamic and therefore remains compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>.

	<lilypond version="2.24">		<lilypond version="2.24">
Line 9:		Line 9:
	#{ \markup \concat {		#{ \markup \concat {
	\normal-text \italic \fontsize #2 (		\normal-text \italic \fontsize #2 (
	\pad-x #0.2 #(ly:music-property dyn 'text)		\pad-x #0.2 #(ly:music-property dyn 'text)
	\normal-text \italic \fontsize #2 )		\normal-text \italic \fontsize #2 )
	}		}
	#}))		#}))

Lemzwerg at 13:55, 3 December 2025

2025-12-03T13:55:12Z

← Older revision		Revision as of 13:55, 3 December 2025
Line 20:		Line 20:

	[[Category:Expressive marks]]		[[Category:Expressive marks]]
			[[Category:Scheme]]
	[[Category:Text]]		[[Category:Text]]
	[[Category:Workaround]]		[[Category:Workaround]]
	[[Category:Included in the official documentation]]		[[Category:Included in the official documentation]]
	[[Category:Snippet]]		[[Category:Snippet]]

Lemzwerg: Lemzwerg moved page Creating "real" parenthesized dynamics to Creating “real” parenthesized dynamics without leaving a redirect

2025-12-03T13:53:28Z

Lemzwerg moved page Creating "real" parenthesized dynamics to Creating “real” parenthesized dynamics without leaving a redirect

← Older revision	Revision as of 13:53, 3 December 2025
(No difference)

Lemzwerg: New category

2025-11-21T23:21:43Z

New category

← Older revision		Revision as of 23:21, 21 November 2025
Line 22:		Line 22:
	[[Category:Text]]		[[Category:Text]]
	[[Category:Workaround]]		[[Category:Workaround]]
	[[Category:Included in the official documentation]][[Category:Snippet]]		[[Category:Included in the official documentation]]
			[[Category:Snippet]]

Lemzwerg at 22:50, 21 November 2025

2025-11-21T22:50:32Z

← Older revision		Revision as of 22:50, 21 November 2025
Line 22:		Line 22:
	[[Category:Text]]		[[Category:Text]]
	[[Category:Workaround]]		[[Category:Workaround]]
	[[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:47:49Z

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:47, 16 November 2025
Line 3:		Line 3:
	However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference), combined with the <code>make-dynamic-script</code> function. This way, the markup will be regarded as a dynamic, and therefore will remain compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>.		However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference), combined with the <code>make-dynamic-script</code> function. This way, the markup will be regarded as a dynamic, and therefore will remain compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>.

	<lilypond version="2.24.0">		<lilypond version="2.24">
	paren =		paren =
	#(define-event-function (dyn) (ly:event?)		#(define-event-function (dyn) (ly:event?)

Jean Abou Samra: Import snippet from LSR

2025-10-26T22:38:37Z

Import snippet from LSR

New page

Although the easiest way to add parentheses to a dynamic mark is to use a <code>\markup</code> block, this method has a downside: the created objects will behave like text markups, and not like dynamics.

However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference), combined with the <code>make-dynamic-script</code> function. This way, the markup will be regarded as a dynamic, and therefore will remain compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>.

<lilypond version="2.24.0">
paren =
#(define-event-function (dyn) (ly:event?)
(make-dynamic-script
#{ \markup \concat {
\normal-text \italic \fontsize #2 (
\pad-x #0.2 #(ly:music-property dyn 'text)
\normal-text \italic \fontsize #2 )
}
#}))

\relative c'' {
c4\paren\f c c \dynamicUp c\paren\p
}
</lilypond>

[[Category:Expressive marks]]
[[Category:Text]]
[[Category:Workaround]]
[[Category:Included in the official documentation]]