LilyPond

For other uses, seeLily Pond (disambiguation).

LilyPond

Developer(s)	David Kastrup, Werner Lemberg, Han-Wen Nienhuys, Jan Nieuwenhuizen, Carl Sorensen, Janek Warchoł,et al.
Initial release	1 August 1997(1 August 1997)
Stable release	2.24.4 / 21 July 2024
Preview release	2.25.19 / 24 August 2024
Repository	gitlab.com/lilypond/lilypond.git
Written in	C++,Scheme,Metafont,PostScript,Python
Operating system	Windows 2000and later Mac OS X 10.4and later Linux FreeBSD
Size	20–100 MB
Standard(s)	EPS,MIDI,MusicXML,PDF,PS,SVG
Available in	Catalan, Dutch, English, French, German, Hungarian, Italian, Japanese, Spanish
Type	Music software,scorewriter
License	GPL-3.0-or-later
Website	lilypond.org

LilyPondis acomputer programandfile formatformusic engraving.One of LilyPond's major goals is to produce scores that are engraved with traditional layout rules, reflecting the era when scores were engraved by hand.

LilyPond iscross-platform,and is available for several commonoperating systems;released under the terms of theGNU General Public License,LilyPond isfree softwareand part of theGNU Project.

History

The LilyPond project was started in 1996 by Han-Wen Nienhuys and Jan Nieuwenhuizen, after they decided to abandon work on MPP (MusiXTeXPreProcessor), a project they began collaborating on in 1995.Its name was inspired both by theRosegardenproject and an acquaintance of Nienhuys and Nieuwenhuizen named Suzanne, a name that means lily in Hebrew (שׁוֹשַׁנָּה).

Version 1.0

LilyPond 1.0 was released on July 31, 1998, highlighting the development of a custom music font, Feta, and the complete separation of LilyPond from MusiXTeX.

Version 2.0

LilyPond 2.0 was released on September 24, 2003, announcing a simplified syntax model and a much more complete set of facilities for notating various styles of music.

Design

Screenshot of LilyPond running on Linux

LilyPond is mostly written inC++and usesScheme(interpreted byGNU Guile) as its extension language, allowing for user customization.It has a relatively largecodebase;as of March 10, 2017, the source includes over 600,000 lines of C++, 140,000 lines of Scheme, and 120,000 lines ofPython code.

It uses a simple text notation for music input, which LilyPond interprets and processes in a series of stages.In the final stage,music notationis output toPDF(viaPostScript) or other graphical formats, such asSVGorPNG.LilyPond can also generateMIDIfiles that correspond to the music notation output.

LilyPond is atext-based application,so it does not contain its owngraphical user interfaceto assist with score creation. (However, a text-editor based "LilyPad" GUI for Windows and MacOS is included by default on these systems.) It does, however, have a flexible input language that strives to be simple, easing thelearning curvefor new users. LilyPond adheres to theWYSIWYMparadigm;the workflow for typesetting music notation with LilyPond is similar to that of preparing documents withLaTeX.

LilyPond supports experimentalmusical notation.Its guitar facilities supportalternative tunings,such asmajor-thirds tuning.

Software features

Beethoven'sSymphony No. 5music sheet printed from a digitally engraved PDF file produced by LilyPond; released by theMutopia Project

LilyPond's primary goal is to produce output comparable to professionally engraved scores instead of output that looks mechanical and computer-generated. An essay from the LilyPond website, written by LilyPond developers, explains some typographical issues addressed by LilyPond:

• Optical font scaling:depending on the staff size, the design of the music font is slightly altered; this is a feature thatDonald Knuth'sComputer Modernfont is known for. As a result, note heads become more rounded, and staff lines become thicker.
• Optical spacing:stem directions are taken into account when spacing subsequent notes.
• Special ledger line handling:ledger linesare shortened when accidentals are nearby, thus enhancing readability.
• Proportional spacing:notes can be positioned in such a way thatexactlyreflects their duration. For example, with this setting, the space between consecutivequarter notesis four times greater than between consecutivesixteenth notes.

Overview of input syntax

The native input language for LilyPond is comprehensive, and consists of manycommandsneeded for expressing any sort of articulation, dynamic, meter, etc. It is similar to that ofTeX.The ability to embed Scheme code within a LilyPondsource filepermits arbitrary extensions to the input language and assists withalgorithmic composition.Some general syntactic features are listed below.

• Single-linecommentsbegin with a percent sign%.
• Notesare represented inpitch-durationformat:pitchis specified withHelmholtz pitch notation,anddurationis specified with anumeralbased system. The semantics of thepitch-durationformat change depending on the active input mode; this is explained in depth in the LilyPond manual. For example, in absolute mode,a'4is an A, one octave up from the base A (A3 inscientific pitch notation), of quarter note length.
• Commands usually begin with a backslash (such as\time,or\slurUp). The function of the command in question determines where the command is placed; for example, if the command is used to indicate a fixeddynamicon a specific note, it is placedafterthe note.
• Some common commands are represented symbolically to ease typing. One example is withslurs,where(and)indicate the beginning and ending of a slur, respectively.Another example is with manualbeaming,where[and]indicate the extent of the beam.

LilyPond's interface withPangorequires the inputcharacter encodingto beUTF-8.One benefit of this is that more than one language can be included in the same source file.

Example of LilyPond input file

\version"2.22.2"

\include"english.ly"

\header{
title=\markup{"Excerpt from"\italic"fibonacci"}
composer="Patrick McCarty"
% copyright = \markup \fontsize #-5
% {
% Copyright © 2009.
% Typeset with GNU LilyPond.
% Released into public domain by the composer.
% }
}

\paper{
paper-height=4.6\in
paper-width=8.5\in
indent=#0
system-count=#2
}

\score{
\newPianoStaff="pianostaff"<<
\newStaff="RH"\relativec'{
\accidentalStyleScore.piano
\clef"treble"
\time2/4
\setScore.currentBarNumber=#51
\tempo"Slow and steady"4=60
<egs,>4\acciaccatura{cs16[ds]}<egs,>4|% m. 51
<dsgs,>4\acciaccatura{e16[ds]}<csgs>4|% m. 52
<csgs>4\acciaccatura{ds16[cs]}<cg>4|% m. 53
<csgs>4\acciaccatura{ds16[e]}<esbsgs>4|% m. 54

<egs,>4\acciaccatura{cs16[ds]}e16fgsa|% m. 55
<gsc,>8\acciaccatura{as16[gs]}
<esb>8~<esb>16dsbas|% m. 56

b16d8bf32f'g16afbfc|% m. 57
<dfdf,>16(caf)<e'e,>(dsb)<g'g,>(ds|% m. 58

\time3/4
<gsgs,>16)\noBeamd,16fgs
a16efb
c16d,(fgs|% m. 59

a16b)e,(f
gs16bc)f,(
gs16asbc)|% m. 60
}

\newDynamics="Dynamics_pf"{
s4\p\<s4|% m. 51
s4s4|% m. 52
s4\mp\>s4|% m. 53
s4s4\!|% m. 54
s4\ps4|% m. 55
s1*2/4|% m. 56
s4\<s4|% m. 57
s4s4|% m. 58
\overrideDynamicText.extra-spacing-width=#'(-0.75.0.75)
s16\mfs16\ps8s4s4|% m. 59
s2.|% m. 60
}

\newStaff="LH"\relativec,{
\clef"bass"
\time2/4
cs4.cs8|% m. 51
cs4.d8|% m. 52
f4.a8|% m. 53
f4.d8|% m. 54

cs4.cs8|% m. 55
d4ds|% m. 56
gs4.bf,8|% m. 57
f'4b,|% m. 58

\time3/4
d4.d8~d4|% m. 59
ef2f4|% m. 60
}
>>
}

Corresponding output

More complex output

Lilypond can also create extensively customised output. An example is the short extract of aKarlheinz Stockhausenpiano piece below.

Collaboration with other projects

FirstmeasuresofAdeste Fideles,generated by LilyPond.

Several graphicalscorewriters—such asRosegarden,NoteEdit,Canorus,Denemo,andTuxGuitar—can export files directly to LilyPond format. Other graphical applications serve as front ends to LilyPond, includingFrescobaldiand the LilyPondTool plugin forjEdit.Denemointegrates thePDFoutput of LilyPond in its display, allowing some editing operations on the final typeset score.

TheMutopia Project,which distributesfree contentsheet music, uses LilyPond to typeset its music, as does Musipedia, a collaborative music encyclopedia.

Emacs'org-modecontains support for embedding LilyPond scores into documents.

OOoLilyPond, aLibreOfficeextension provides support for calling LilyPond to embed scores into documents.

Integration into MediaWiki

Lilypond is available inMediaWikivia theScore extensioncode. This, for example, transforms the notation

<scoresound="1">\relativec'{
\keyd\major
fis4fisgaagfiseddefisfis4.e8e2}</score>

into

The above is an excerpt from Ludwig van Beethoven’s 9th Symphony, commonly known as "Ode to Joy". More complex scores, including lyrics, are also possible within MediaWiki wikis.SeePastime with Good Companyfor an example of this.

Integration into text usinglilypond-book

Integration of LilyPond musical elements into various document formats (bothTeX-based systems such asLaTeXandTexinfo,and alsoDocBookandHTMLpages) is natively supported through the companion programlilypond-book,developed and maintained by the LilyPond community.This allows users to embed musical elements within texts, such as musicology, song booklets, work sheets for teaching, and school examinations.

Integration into LaTeX

For integration into theLaTeXdocument preparation system, lyLuaTeX has been developed as a LuaLaTeX package to embed musical elements within texts. It includes features for matching layout and appearance of the musical elements with the surrounding text document.Music elements may consist of music symbols, song lyrics, guitar chords diagrams, lead sheets, music excerpts, guitar tablatures, or multi-page scores.

Comparison to other scorewriters

FinaleandSibeliusare twoproprietaryscorewriters often compared to LilyPond. Andrew Hawryluk, a LilyPond user, wrote a series of articles comparing output quality between Finale and LilyPond.

Another scorewriter with comparable features to LilyPond isSCORE,but SCORE relies on manual positioning more than Lilypond does.

See alsoComparison of scorewriters.

See also

• ABC notation
• Common Music Notation
• Denemo
• Frescobaldi
• GUIDO music notation
• Impro-Visor
• MuseScore
• MusicXML
• MusiXTeX
• NoteEdit
• Philip's Music Scribe
• Rosegarden
• SCORE (software)
• List of music software
• List of scorewriters

External links

• Official website
• "lyluatex – Commands to include lilypond scores within a (Lua)LATEX document".RetrievedApril 16,2020.