Time mark engraver - Revision history

Lemzwerg at 07:09, 31 December 2025

2025-12-31T07:09:12Z

← Older revision		Revision as of 07:09, 31 December 2025
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 {{Convert-ly-devel}} if used with a LilyPond version ~~larger~~ than 2.24.		''Upgrade notice'': This snippet must be updated with the {{Convert-ly-devel}} script if used with a LilyPond version newer than 2.24.

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

Lemzwerg at 06:39, 31 December 2025

2025-12-31T06:39:54Z

← Older revision		Revision as of 06:39, 31 December 2025
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 ~~needs proper convert~~-ly ~~conversion for >=~~2.~~25 ( <code>'tempoWholesPerMinute</code> -> <code>'tempoWholesPerMinuteAsMoment</code>)~~.		''Upgrade notice'': This snippet must be updated with {{Convert-ly-devel}} if used with a LilyPond version larger than 2.24.

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

Masterpaster at 22:29, 27 December 2025

2025-12-27T22:29:13Z

← Older revision		Revision as of 22:29, 27 December 2025
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.).

	~~{{Warning\|~~This snippet needs proper convert-ly conversion for >=2.25. ( <code>'tempoWholesPerMinute</code> -> <code>'tempoWholesPerMinuteAsMoment</code>)}}		''Upgrade notice'': This snippet needs proper convert-ly conversion for >=2.25 ( <code>'tempoWholesPerMinute</code> -> <code>'tempoWholesPerMinuteAsMoment</code>).

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

Masterpaster: Upgrade (convert-ly) notice

2025-12-27T22:26:22Z

Upgrade (convert-ly) notice

← Older revision		Revision as of 22:26, 27 December 2025
Line 9:		Line 9:
	* find “time since start” at a few musical key positions without counting or math, or		* find “time since start” at a few musical key positions without counting or math, or
	* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).		* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).

			{{Warning\|This snippet needs proper convert-ly conversion for >=2.25. ( <code>'tempoWholesPerMinute</code> -> <code>'tempoWholesPerMinuteAsMoment</code>)}}

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

Lemzwerg at 11:42, 27 December 2025

2025-12-27T11:42:11Z

← Older revision		Revision as of 11:42, 27 December 2025
Line 15:		Line 15:

	#(define (Elapsed_time_engraver context)		#(define (Elapsed_time_engraver context)
	(define (format-time seconds) ;; example: 2m15s		(define (format-time seconds) ; example: 2m15s
	(let ((minutes (euclidean-quotient seconds 60))		(let ((minutes (euclidean-quotient seconds 60))
	(rest (euclidean-remainder seconds 60)))		(rest (euclidean-remainder seconds 60)))

Lemzwerg: Make the snippet display its result

2025-12-27T11:38:45Z

Make the snippet display its result

← Older revision		Revision as of 11:38, 27 December 2025
Line 1:		Line 1:
	When working with LilyPond’s MIDI output, it can be tedious to find the exact ~~'''elapsed~~ time from the start of the score to an arbitrary ~~point'''—especially~~ when the music contains ~~'''~~multiple tempo changes~~'''~~. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time-consuming.		When working with LilyPond’s MIDI output it can be tedious to find the exact ‘elapsed time from the start of the score to an arbitrary point’ – especially when the music contains multiple tempo changes. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time consuming.

	~~To solve this, Jean wrote~~ a ~~small '''custom~~ engraver~~'''~~ that allows you to insert ~~'''~~time marks~~'''~~ directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond ~~will compute~~ the elapsed time up to that position and ~~display~~ it (~~2m15s e.g.~~).		This snippets introduces a Scheme engraver that allows you to insert time marks directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond computes the elapsed time up to that position and displays it (for example, ‘2m15s’).

	~~=== Use case ===~~		This is useful when you need to
	This is useful when you need to:

	* align score events with audio/video cues,		* align score events with audio or video cues,
	* locate timestamps for MIDI-driven playback or mockups,		* locate timestamps for MIDI-driven playback or mockups,
	* find “time since start” at a few key ~~musical points~~ without counting or math,		* find “time since start” at a few musical key positions without counting or math, or
	* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).		* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).

	\version "2.24.4"		<lilypond version="2.24">
	% source: https://lists.gnu.org/archive/html/lilypond-user/2024-03/msg00127.html		% LSR source: https://lists.gnu.org/archive/html/lilypond-user/2024-03/msg00127.html
	% credits: 2024 - Jean Abou Samra		% LSR credits: 2024 - Jean Abou Samra

	#(define (~~Custom_engraver!!~~ context)		#(define (Elapsed_time_engraver context)
	(define (format-time seconds) ; ~~ex.~~: 2m15s		(define (format-time seconds) ;; example: 2m15s
	(let ((minutes (euclidean-quotient seconds 60))		(let ((minutes (euclidean-quotient seconds 60))
	(rest (euclidean-remainder seconds 60)))		(rest (euclidean-remainder seconds 60)))
	(string-append (if (zero? minutes) "" (format #f "~am" minutes))		(string-append (if (zero? minutes) "" (format #f "~am" minutes))
	(format #f "~as" (round rest)))))		(format #f "~as" (round rest)))))
	(let ((wholes-per-minute 15)
	(last-time ZERO-MOMENT)		(let ((wholes-per-minute 15)
	(total-time 0)		(last-time ZERO-MOMENT)
	(marks '()))		(total-time 0)
	(make-engraver		(marks '()))
	((process-music engraver)		(make-engraver
	(let* ((new-time (ly:context-current-moment context))		((process-music engraver)
	(time-delta (ly:moment-main (ly:moment-sub new-time last-time)))		(let* ((new-time (ly:context-current-moment context))
	(new-wholes-per-minute		(time-delta (ly:moment-main
	(and=> (ly:context-property context 'tempoWholesPerMinute #f)		(ly:moment-sub new-time last-time)))
	ly:moment-main)))		(new-wholes-per-minute
	(set! total-time		(and=> (ly:context-property context
	(+ total-time (* 60 (/ time-delta wholes-per-minute))))		'tempoWholesPerMinute #f)
	(set! last-time new-time)		ly:moment-main)))
	(when new-wholes-per-minute		(set! total-time
	(set! wholes-per-minute new-wholes-per-minute))))		(+ total-time (* 60 (/ time-delta wholes-per-minute))))
	(acknowledgers		(set! last-time new-time)
	((text-mark-interface engraver grob source-engraver)		(when new-wholes-per-minute
	(set! marks (cons grob marks))))		(set! wholes-per-minute new-wholes-per-minute))))
	((process-acknowledged engraver)
	(for-each (lambda (grob)		(acknowledgers
	(when (assq-ref (ly:grob-property grob 'details) 'time-mark)		((text-mark-interface engraver grob source-engraver)
	(ly:grob-set-property! grob 'text (format-time		(set! marks (cons grob marks))))
	total-time))))
	marks)		((process-acknowledged engraver)
	(set! marks '())))))		(for-each (lambda (grob)
			(when (assq-ref (ly:grob-property grob 'details)
	\layout {		'time-mark)
	\context {		(ly:grob-set-property!
	\Score		grob 'text (format-time total-time))))
	\consists #~~Custom_engraver!!~~		marks)
	}		(set! marks '())))))
	}

	timeMark = \tweak details.time-mark ##t \tweak color "red" \textEndMark		\layout {
	"~~Abracadabra~~"		\context {
			\Score
	{		\consists #Elapsed_time_engraver
	c'1		}
	\timeMark		}
	\tempo 4 = 120
	c'4 8. 16 2		% The argument of the `\textEndMark` here is just a placeholder
	\timeMark		% that the engraver replaces with a time stamp (because the
	\tempo 4 = 180		% `time-mark` subproperty is set).
	c'2 2		timeMark = \tweak details.time-mark ##t
	\timeMark		\tweak color "red"
	\repeat unfold 180 c'4		\textEndMark ""
	\timeMark
	}		{
			c'1 \| \timeMark
			\tempo 4 = 120 c'4 8. 16 2 \| \timeMark
			\tempo 4 = 180 \repeat unfold 4 c'2 \| \timeMark
			\repeat unfold 180 c'4 \| \timeMark
			}
			</lilypond>

			[[Category:Automatic notation]]
			[[Category:Contexts and engravers]]
			[[Category:Editorial annotations]]
			[[Category:Midi]]
			[[Category:Scheme]]
			[[Category:Snippet]]

Lemzwerg: Lemzwerg moved page Time Mark Engraver to Time mark engraver without leaving a redirect

2025-12-27T11:14:22Z

Lemzwerg moved page Time Mark Engraver to Time mark engraver without leaving a redirect

← Older revision	Revision as of 11:14, 27 December 2025
(No difference)

Masterpaster: Undo revision 5979 by Masterpaster (talk)

2025-12-27T10:10:02Z

Undo revision 5979 by Masterpaster (talk)

← Older revision		Revision as of 10:10, 27 December 2025
Line 1:		Line 1:
	When working with LilyPond’s MIDI output, it can be tedious to find the exact '''elapsed time from the start of the score to an arbitrary point'''—especially when the music contains '''multiple tempo changes'''. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time-consuming.		When working with LilyPond’s MIDI output, it can be tedious to find the exact '''elapsed time from the start of the score to an arbitrary point'''—especially when the music contains '''multiple tempo changes'''. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time-consuming.

	To solve this, [[Jean]] wrote a small '''custom engraver''' that allows you to insert '''time marks''' directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond will compute the elapsed time up to that position and display it (2m15s e.g.).		To solve this, Jean wrote a small '''custom engraver''' that allows you to insert '''time marks''' directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond will compute the elapsed time up to that position and display it (2m15s e.g.).

	=== Use case ===		=== Use case ===

Masterpaster: Added link to Jean's name

2025-12-27T10:09:07Z

Added link to Jean's name

← Older revision		Revision as of 10:09, 27 December 2025
Line 1:		Line 1:
	When working with LilyPond’s MIDI output, it can be tedious to find the exact '''elapsed time from the start of the score to an arbitrary point'''—especially when the music contains '''multiple tempo changes'''. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time-consuming.		When working with LilyPond’s MIDI output, it can be tedious to find the exact '''elapsed time from the start of the score to an arbitrary point'''—especially when the music contains '''multiple tempo changes'''. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time-consuming.

	To solve this, Jean wrote a small '''custom engraver''' that allows you to insert '''time marks''' directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond will compute the elapsed time up to that position and display it (2m15s e.g.).		To solve this, [[Jean]] wrote a small '''custom engraver''' that allows you to insert '''time marks''' directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond will compute the elapsed time up to that position and display it (2m15s e.g.).

	=== Use case ===		=== Use case ===

Masterpaster: Page initially created

2025-12-27T09:53:38Z

Page initially created

New page

When working with LilyPond’s MIDI output, it can be tedious to find the exact '''elapsed time from the start of the score to an arbitrary point'''—especially when the music contains '''multiple tempo changes'''. Counting measures and doing tempo math is error-prone; inspecting the MIDI file manually is possible but time-consuming.

To solve this, Jean wrote a small '''custom engraver''' that allows you to insert '''time marks''' directly into the music. At any point in the score you can add <code>\timeMark</code>, and LilyPond will compute the elapsed time up to that position and display it (2m15s e.g.).

=== Use case ===
This is useful when you need to:

* align score events with audio/video cues,
* locate timestamps for MIDI-driven playback or mockups,
* find “time since start” at a few key musical points without counting or math,
* work reliably across complex tempo maps (rit., accel., metric modulations, etc.).

\version "2.24.4"
% source: https://lists.gnu.org/archive/html/lilypond-user/2024-03/msg00127.html
% credits: 2024 - Jean Abou Samra

#(define (Custom_engraver!! context)
(define (format-time seconds) ; ex.: 2m15s
(let ((minutes (euclidean-quotient seconds 60))
(rest (euclidean-remainder seconds 60)))
(string-append (if (zero? minutes) "" (format #f "~am" minutes))
(format #f "~as" (round rest)))))
(let ((wholes-per-minute 15)
(last-time ZERO-MOMENT)
(total-time 0)
(marks '()))
(make-engraver
((process-music engraver)
(let* ((new-time (ly:context-current-moment context))
(time-delta (ly:moment-main (ly:moment-sub new-time last-time)))
(new-wholes-per-minute
(and=> (ly:context-property context 'tempoWholesPerMinute #f)
ly:moment-main)))
(set! total-time
(+ total-time (* 60 (/ time-delta wholes-per-minute))))
(set! last-time new-time)
(when new-wholes-per-minute
(set! wholes-per-minute new-wholes-per-minute))))
(acknowledgers
((text-mark-interface engraver grob source-engraver)
(set! marks (cons grob marks))))
((process-acknowledged engraver)
(for-each (lambda (grob)
(when (assq-ref (ly:grob-property grob 'details) 'time-mark)
(ly:grob-set-property! grob 'text (format-time
total-time))))
marks)
(set! marks '())))))

\layout {
\context {
\Score
\consists #Custom_engraver!!
}
}

timeMark = \tweak details.time-mark ##t \tweak color "red" \textEndMark
"Abracadabra"

{
c'1
\timeMark
\tempo 4 = 120
c'4 8. 16 2
\timeMark
\tempo 4 = 180
c'2 2
\timeMark
\repeat unfold 180 c'4
\timeMark
}