[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 5917: ly:performance-headers and \midi { after-writing } (issu

From: nine . fierce . ballads
Subject: Re: Issue 5917: ly:performance-headers and \midi { after-writing } (issue 567450043 by address@hidden)
Date: Sat, 18 Apr 2020 04:25:51 -0700

Reviewers: lemzwerg,

On 2020/04/18 05:53:25, lemzwerg wrote:
> lily/ LY_DEFINE (ly_performance_set_header_x,
> "ly:performance-set-header!",
> Will this removal need a `convert-ly` warning?

It doesn't strike me as important, but I don't have much experience with
this kind of decision.


Change ly:performance-header into ly:performance-headers, returning a
list of visible header modules from innermost to outermost.  Before,
only the innermost header was provided, so the values of variables
defined in outer headers were not accessible.

If the \midi block defines a function called after-writing, LilyPond
calls it after writing the MIDI file.  Apart from its use in regression-
testing ly:performance-headers, it offers a way for an advanced user to
dump metadata associated with each performance.  For example, the
function could open a file and dump all header variables in YAML format
for use in a scripted workflow where the information ends up in ID3 tags
in an mp3 file.

Please review this at

Affected files (+84, -46 lines):
  A input/regression/
  M lily/
  M lily/include/performance.hh
  M lily/
  M lily/
  M scm/midi.scm

reply via email to

[Prev in Thread] Current Thread [Next in Thread]