LilyPond — Changes

This document lists changes and new features in LilyPond version 2.24.0 since 2.22.

Note: LilyPond releases can contain syntax changes, which may require modifications in your existing files written for older versions so that they work in the new version. To upgrade files, it is strongly recommended to use the convert-ly tool distributed with LilyPond, which is described in Updating files with convert-ly. convert-ly can perform almost all syntax updates automatically. Frescobaldi users can run convert-ly directly from Frescobaldi using “Tools > Update with convert-ly…”. Other editing environments with LilyPond support may provide a way to run convert-ly graphically.


Major changes in LilyPond


Known issues in LilyPond 2.24.0

On Windows, compiling very large scores (several hundreds of pages) can result in crashes.1 We hope to address this in a future 2.24.x release.


Notes for source compilation and packagers

This section is aimed at enthusiasts compiling LilyPond from source and packagers preparing LilyPond for distribution. If you are not part of either group, you can skip over this section.


New for musical notation


Pitches improvements


Rhythm improvements


Expressive mark improvements


Repeat improvements


Editorial annotation improvements


Text improvements


New for specialist notation


Fretted string instrument improvements


Percussion improvements


Wind instrument improvements


Chord notation improvements


Ancient notation improvements


World music improvements


Miscellaneous improvements


Notes on Guile 2.2

This version of LilyPond switches from Guile 1.8 to Guile 2.2. This section lists some of the most common incompatibilities that you could have to deal with in order to upgrade your Scheme code.

A full, detailed log of changes in Guile can be found in the NEWS’ file of the Guile source.

For older news, go to https://lilypond.org/doc/v2.22/Documentation/changes/, https://lilypond.org/doc/v2.20/Documentation/changes/, or go back to the Documentation index.


Footnotes

[1] Note that very large scores could already crash in LilyPond 2.22 due to restrictions imposed by the 32-bit architecture.


LilyPond — Changes v2.24.0 (stable-branch).