Defining a custom staff context - Revision history

Lemzwerg at 08:07, 3 December 2025

2025-12-03T08:07:15Z

← Older revision		Revision as of 08:07, 3 December 2025
Line 1:		Line 1:
	Instead of having to type the same customization commands every time you need to use a particular type of staff, you can define a custom staff context and use it instead. For example, instead of:		Instead of having to type the same customization commands every time you need to use a particular type of staff, you can define a custom staff context and use it instead. For example, instead of

	~~<code>~~\new Staff \with { ... }~~</code>~~		\new Staff \with { ... }

	~~You~~ would use:		you would use

	~~<code>~~\new MyCustomStaff~~</code>~~		\new MyCustomStaff

	A custom staff context can have any customizations that you would use in a Staff's \with block. Note that the custom staff's definition can be saved in a file that you <code>\include</code>, so you do not have to re-create it every time it is needed.		A custom staff context can have any customizations that you would use in a <code>Staff</code> context's <code>\with</code> block. Note that the custom staff's definition can be saved in a file that you <code>\include</code>, so you do not have to re-create it every time it is needed.

	<lilypond version="2.24">		<lilypond version="2.24">
	~~%% http://lsr.di.unimi.it/LSR/Item?id=979 (formerly id=882)~~

	% DEFINE A CUSTOM STAFF CONTEXT FOR "LAYOUT"		% DEFINE A CUSTOM STAFF CONTEXT FOR "LAYOUT"
	\layout {		\layout {

Lemzwerg: Lemzwerg moved page Defining a Custom Staff Context to Defining a custom staff context without leaving a redirect: Only the first letter of a title should be uppercase

2025-11-24T05:28:21Z

Lemzwerg moved page Defining a Custom Staff Context to Defining a custom staff context without leaving a redirect: Only the first letter of a title should be uppercase

← Older revision	Revision as of 05:28, 24 November 2025
(No difference)

Lemzwerg: New category

2025-11-21T23:18:28Z

New category

← Older revision		Revision as of 23:18, 21 November 2025
Line 71:		Line 71:

	[[Category:Contexts and engravers]]		[[Category:Contexts and engravers]]
	[[Category:Tweaks and overrides]][[Category:Snippet]]		[[Category:Tweaks and overrides]]
			[[Category:Snippet]]

Lemzwerg at 22:51, 21 November 2025

2025-11-21T22:51:33Z

← Older revision		Revision as of 22:51, 21 November 2025
Line 71:		Line 71:

	[[Category:Contexts and engravers]]		[[Category:Contexts and engravers]]
	[[Category:Tweaks and overrides]]		[[Category:Tweaks and overrides]][[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:11Z

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 9:		Line 9:
	A custom staff context can have any customizations that you would use in a Staff's \with block. Note that the custom staff's definition can be saved in a file that you <code>\include</code>, so you do not have to re-create it every time it is needed.		A custom staff context can have any customizations that you would use in a Staff's \with block. Note that the custom staff's definition can be saved in a file that you <code>\include</code>, so you do not have to re-create it every time it is needed.

	<lilypond version="2.24.0">		<lilypond version="2.24">
	%% http://lsr.di.unimi.it/LSR/Item?id=979 (formerly id=882)		%% http://lsr.di.unimi.it/LSR/Item?id=979 (formerly id=882)

Jean Abou Samra: Import snippet from LSR

2025-10-26T22:49:15Z

Import snippet from LSR

New page

Instead of having to type the same customization commands every time you need to use a particular type of staff, you can define a custom staff context and use it instead. For example, instead of:

<code>\new Staff \with { ... }</code>

You would use:

<code>\new MyCustomStaff</code>

A custom staff context can have any customizations that you would use in a Staff's \with block. Note that the custom staff's definition can be saved in a file that you <code>\include</code>, so you do not have to re-create it every time it is needed.

<lilypond version="2.24.0">
%% http://lsr.di.unimi.it/LSR/Item?id=979 (formerly id=882)

% DEFINE A CUSTOM STAFF CONTEXT FOR "LAYOUT"
\layout {
\context {
% make a copy of the standard Staff context
\Staff
% give this custom context a name of your choice
\name MyCustomStaff
% tell LilyPond that commands that work in a standard
% Staff context should also work in this custom context
\alias Staff
% add customizations, these are just examples,
% they can be anything that can go in a staff's \with block
\consists "Pitch_squash_engraver"
squashedPosition = #0
\override NoteHead.style = #'slash
\override Stem.transparent = ##t
\override Flag.transparent = ##t
}
% define which "parent" contexts will accept this custom context as a "child"
\context { \Score \accepts MyCustomStaff }
\context { \ChoirStaff \accepts MyCustomStaff }
\context { \GrandStaff \accepts MyCustomStaff }
\context { \PianoStaff \accepts MyCustomStaff }
\context { \StaffGroup \accepts MyCustomStaff }
}

% DEFINE THE CUSTOM STAFF CONTEXT FOR "MIDI" TOO
% to avoid warnings the context has to be defined for each type of output
\midi {
\context {
\Staff
\name MyCustomStaff
\alias Staff
% the customizations are not needed for midi
% since they are for visual output only
}
\context { \Score \accepts MyCustomStaff }
\context { \ChoirStaff \accepts MyCustomStaff }
\context { \GrandStaff \accepts MyCustomStaff }
\context { \PianoStaff \accepts MyCustomStaff }
\context { \StaffGroup \accepts MyCustomStaff }
}

% EXAMPLE
\score {
<<
\new Staff {
c' d' e' f'
}
\new MyCustomStaff {
c' d' e' f'
}
>>
\layout { }
\midi { }
}
</lilypond>

[[Category:Contexts and engravers]]
[[Category:Tweaks and overrides]]