LilyPond... muzieknotatie voor iedereen

Wat is LilyPond?

LilyPond is een muzieknotatieprogramma en beoogt het produceren van bladmuziek van de hoogst mogelijke kwaliteit. Het integreert de esthetiek van traditioneel gegraveerde bladmuziek in computer printouts. LilyPond is vrije software en is onderdeel van het GNU Project.

Lees meer in onze Inleiding!

LilyPond 2.19.5 released April 20, 2014

We are happy to announce the release of LilyPond 2.19.5. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

Lilypond 2.18.2 released! March 23, 2014

We are proud to announce the release of GNU LilyPond 2.18.2. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

This version provides a number of updates to 2.18.0, including updated manuals. We recommend all users to upgrade to this version.

LilyPond production named BEST EDITION 2014 March 11, 2014

We are thrilled to announce that the new edition of the songs of Oskar Fried (1871-1941), published recently by our fellow contributors Urs Liska and Janek Warchoł [1], will receive the "Musikeditionspreis BEST EDITION 2014" of the German Music Publishers’ Association [2]! The ceremony will take place in a few days at the Frankfurt Musikmesse [3].

We congratulate Janek and Urs for gaining such public recognition of typographical and editorial excellence of their work. We are also delighted to inform you that they intend to make their work available under a Free license as soon as the publisher expenses are covered. Please support this initiative by buying the printed volume through the publisher [4] or by pledging a contribution at the Indiegogo campaign [5]!

[1] http://lilypondblog.org/category/fried-songs
[2] http://www.best-edition.de
[3] https://musik.messefrankfurt.com/frankfurt/en/besucher/events/awards/best_edition.html
[4] http://www.sound-rel.de
[5] http://igg.me/at/free-fried

Lilypond 2.18.0 released! December 29, 2013

We are proud to announce the release of GNU LilyPond 2.18.0. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

Among the numerous improvements and changes, the following might be most visible:

  • Many items are now positioned using their actual outline rather than a rectangular bounding box. This greatly reduces the occurrence of unsightly large gaps.
  • Sets and overrides can now use the syntax
    \override Voice.TextSpanner.bound-details.left.text = "rit."
    

    instead of the previous

    \override Voice.TextSpanner #'(bound-details left text) = "rit."
    
  • Triplets with a given group length can now be written as
    \tuplet 3/2 4 { c8 c c  c c c }
    

    instead of

    \times 2/3 { c8 c c }  \times 2/3 { c8 c c }
    

A full list of noteworthy new features is given in:

http://lilypond.org/doc/v2.18/Documentation/changes/index.html

Great thanks go to the large number of LilyPond enthusiasts whose financial backing enabled one core developer, David Kastrup, to focus exclusively on LilyPond during the entire development cycle.

LilyPond 2.18 has been brought to you by

Main Developers:

Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, Janek Warchoł

Core Contributors:

Aleksandr Andreev, Frédéric Bron, Torsten Hämmerle, Marc Hohl, James Lowe, Andrew Main, Thomas Morley, David Nalesnik, Keith OHara, Benkő Pál, Anders Pilegaard, Julien Rioux, Johannes Rohrer, Adam Spiers, Heikki Tauriainen

Documentation Writers:

Frédéric Bron, Federico Bruni, Colin Campbell, Urs Liska, James Lowe, Thomas Morley, Jean-Charles Malahieude, Guy Stalnaker, Martin Tarenskeen, Arnold Theresius, Rodolfo Zitellini

Bug Squad:

Colin Campbell, Eluze, Marc Hohl, Phil Holmes, Marek Klein, Ralph Palmer

Support Team:

Colin Campbell, Eluze, Marc Hohl, Marek Klein, Kieren MacMillan, Urs Liska, Ralph Palmer

Translators:

Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric, Jean-Charles Malahieude, Till Paala, Yoshiki Sawada

and numerous other contributors.

LilyPond blog. June 2, 2013

Janek Warchoł has created a LilyPond blog. You can find it at lilypondblog.org!

LilyPond 2.16.2 released! January 4, 2013

We are happy to announce the release of LilyPond 2.16.2. This release is mainly to correct a problem with lilypond-book running on Windows. We recommend that only people requiring this functionality upgrade to this version.

The LilyPond Report #28. November 12, 2012

The October issue of the LilyPond Report focuses on the meeting of LilyPond developers and users in Waltrop, Germany last August. Of course, there are also some musings on LilyPond triggered by the release of 2.16.0 and 2.17.0 occuring from that venue.

There are also two monthly financial reports from David Kastrup whose work on LilyPond is solely paid for by financial contributions from other developer and users (thank you!), and a report about experiences from a web-based music typesetting service using LilyPond internally.

Come read LilyPond Report 28 now; comments and contributions are warmly encouraged!

LilyPond 2.16.1 released! November 9, 2012

We are happy to announce the release of LilyPond 2.16.1. This has a number of updates to the previous stable version, and should cause no problems. We recommend that everybody upgrade to this version.

Lilypond 2.16.0 released! August 24, 2012

We are proud to announce the release of GNU LilyPond 2.16.1. LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

Many improvements have been made in the past year since the previous main stable version. A few major improvements are:

  • Support for kievan square notation
  • User and programming interfaces have greatly improved
  • Music functions have become quite more versatile

A full list of new features is given in:

http://lilypond.org/doc/v2.16/Documentation/changes/index.html

Happy music typesetting! LilyPond 2.16 was brought to you by...

Main development team:

Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, Jan Warchoł

Programming contributors:

Aleksandr Andreev, Sven Axelsson, Peter Chubb, Karin Hoethker, Marc Hohl, David Nalesnik, Justin Ohmie, Benkő Pál, Julien Rioux, Patrick Schmidt, Adam Spiers, Heikki Taurainen, Piers Titus van der Torren, Jan-Peter Voigt, Janek Warchol

Documentation contributors:

James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil

Bug squad:

Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer, James Lowe

Support:

Colin Campbell, Christian Hitz, Phil Holmes

Translation contributors:

Jean-Charles Malahieude, Till Paala, Yoshiki Sawada


Inleiding

Ons Doel

flat-design

De inspiratie voor LilyPond ontstond toen twee muzikanten meer wilden dan de ontzielde aanblik van met de computer geprinte bladmuziek. Muzikanten lezen het liefst mooie muziek dus waarom zouden programmeurs geen software kunnen schrijven waarmee je prachtige partijen kunt afdrukken?

Het resultaat is een systeem waarin muzikanten geen omkijken meer hebben naar layout-details, maar zich kunnen concentreren op het maken van muziek. LilyPond biedt hen de mogelijkheid om partijen te maken van publicatiekwalteit, volgens de beste tratities van klassieke muziekgravure.


Functies

Elegantie

Prachtige klassieke muziekgravure

flat-design

Met LilyPond kunnen muzikanten elegante bladmuziek produceren die gemakkelijk leest. De community van ontwikkelaars heeft duizenden uren geïnvesteerd in het ontwikkelen van krachtige muzieknotatie-software die prachtige gegraveerde muziek oplevert. Alle stijlinstellingen, het speciaal ontworpen muziekfont en algoritmes zijn geïnspireerd op de mooiste handgegraveerde bladmuziek. De LilyPond-uitvoer ziet er net zo krachtig en harmonisch uit als de best gegraveerde klassieke partituren. Dit wordt verder uitgewerkt in ons Essay.

Effectieve layout-keuzes

Verlies minder tijd met het verfraaien van het resultaat; LilyPond verzint zelf de beste layout. Het bepaalt de spatiëring en het afbreken van regels en pagina’s, zodat een strakke en regelmatige layout ontstaat. Het voorkomt botsingen tussen liedteksten, noten en akkoorden en zet legatobogen en waardestrepen automatisch op de juiste manier!

Gebruiksgemak

lilypond-book

Tekstgebaseerde invoer

LilyPond werkt met ASCII-invoer die je kunt aanleveren met jouw favoriete teksteditor, snel en comfortabel. De invoer bevat alle informatie, dus het onthouden van ingewikkelde reeksen commando’s is niet nodig: sla gewoon je invoerbestand op en je kunt alles later opnieuw raadplegen.

Combineer muziek en tekst

Voeg muziekfragmenten aan teksten toe zonder het knippen en plakken van plaatjes. Integreer muziek naadloos in LaTeX of HTML, of voeg muziek toe aan OpenOffice.org met behulp van OOoLilyPond. Plugins zijn ook beschikbaar voor het gebruik van LilyPond-code in verschillende blogs and wiki’s, wat online-samenwerking mogelijk maakt.

Toegankelijkheid

Tekstgebaseerde invoer maakt het schrijven van partituren ook toegankelijk voor gebruikers met ernstige lichamelijke beperkingen. Gebruikers met motorische beperkingen die niet kunnen typen of een muis kunnen besturen, kunnen spraakherkenningssoftware gebruiken om LilyPond-bestanden te bewerken. Zelfs blinde gebruikers kunnen voorleessoftware gebruiken voor het schrijven van LilyPond-bestanden – een onmogelijke taak in grafisch-gebaseerde muziekprogramma’s.

Uitbreidbaar ontwerp

Alle instellingen kunnen worden aangepast aan je eigen persoonlijke typografische voorkeuren. Als dat niet voldoende is, bestaat er nog altijd de ingebouwde scriptingtaal Scheme, een dialect van de krachtige programmeertaal LISP. Instellingen, variabelen en functies zijn allemaal beschreven in de uitvoerige referentiehandleiding van het programma.

Omgeving

frescobaldi-lilypond-editor-small

Vrije software

LilyPond kan kostenloos worden gedownload! Ja hoor - het is gratis. Je kunt het downloaden van de downloadpagina.

Bovendien is het ook vrije software. Wat betekent dat je de broncode erbij krijgt, plus toestemming om deze te veranderen en te kopiëren. Dus als je je ergert aan een fout, of als er iets in het programma ontbreekt, kun je het zelf oplossen of iemand anders inhuren om het voor je te doen.

Uitstekende ondersteuning

LilyPond werkt op alle bekende besturingssystemen: GNU/Linux, MacOS X, en Windows. Er is een zeer uitgebreide handleiding met honderden voorbeeldbestandjes. Er is een actieve gebruikersgroep die antwoorden geeft op de lilypond-user mailinglijst, terwijl het ontwikkelingsteam ervoor zorgt dat problemen snel worden opgelost.

Verbeterde editors

Verscheidene ontwikkelaars, zelf actieve gebruikers van LilyPond, hebben ook gereedschappen geschreven die speciaal bedoeld zijn om het invoeren van LilyPond-bestanden sneller en effectiever te maken. Een aantal voorbeelden is te vinden in Eenvoudiger bewerken.

En nu?

Nog steeds niet overtuigd? Bekijk dan maar eens enkele specifieke Voorbeelden. Heb je al besloten LilyPond te gaan proberen, lees dan eerst over onze Tekstinvoer.


Voorbeelden

LilyPond is een krachtig en flexibel gereedschap voor uiteenlopende muzieknotatie-taken. Bekijk ter inspiratie eens onze galerij met voorbeelden!

Klassieke Muziek

Dit orgelwerk van J.S. Bach is een typisch LilyPond-project.

bach-bwv610

(Klik om te vergroten)

Ingewikkelde muzieknotatie

Dit voorbeeld uit Goyescas van Enrique Granados laat geavanceerde typesettingsfuncties zien, zoals waardestrepen met knie, stokken tussen notenbalken en melodie-volglijntjes.

granados

(Klik om te vergroten)

Vroege muziek

LilyPond geeft ook ondersteuning voor verscheidene verouderde notatievormen zoals dit Gregoriaanse liedfragment.

ancient-headword

(Klik om te vergroten)

Moderne muziek

Hedendaagse componisten vinden dat LilyPond zich goed leent voor het tonen van ongebruikelijke notatie. Hier is een fragment uit Trevor Bača’s Čáry, voor solo basfluit.

cary

(Klik om te vergroten)

Maak efficiënte, flexibele partijen voor uitvoerenden

Vanuit één en dezelfde broncode kunnen allerlei soorten partijen worden gemaakt. Dit is een fragment uit Nicolas Sceaux’s gravure van Handels Giulio Cesare, als volledige partituur, piano-zang reductie, en een vioolpartij.

sesto-full

(Klik om te vergroten)

sesto-piano

(Klik om te vergroten)

sesto-violin

(Klik om te vergroten)

Tablatuur

LilyPond ondersteunt tablatuurnotatie die kan worden aangepast aan elk intrument dat van tablatuur kan spelen. De tablatuurbalk wordt automatisch gegenereerd op basis van de noten die voor de vijf-lijns notenbalk zijn ingevoerd.

tab-example

(Klik om te vergroten)

Schenker-diagrammen

De standaard uitvoer kan ingrijpend worden veranderd. Dit is een indrukwekkende Schenker-analyse, gemaakt door Kris Schaffer, voor een artikel in in Linux Journal. Voor de duidelijkheid zijn hier kleuren toegevoegd.

bach-schenker

(Klik om te vergroten)

Vocale muziek

LilyPond blinkt uit in alle soorten vocale muziek, van psalmen en gezangen tot opera. Hier is een Middeleeuws motet met enigszins ongebruikelijke eisen. De tenorstem is in een andere maatsoort genoteerd dan de anderen, maar moet uitgelijnd zijn als ware het dezelfde maatsoort. LilyPond doet dit bijzonder elegant. Let ook op de incipits met sleutels in de Vaticana stijl, de doorgestreepte stokken die gepliceerde noten aangeven en de ligatuurhaken boven bepaalde groepen noten.

aucun-snippet

(Klik om te vergroten)

Educatieve doeleinden

LilyPond is ook perfect voor educatieve doeleinden. Hier is een voorbeeld van een eenvoudige contrapunt-oefening.

theory

(Klik om te vergroten)

Populaire muziek

Het is eenvoudig om zogenaamde pop leadsheets met melodie, songtekst, akkoordnamen, en fretboard-diagrammen te maken. In dit voorbeeld zie je enkele van de voorgedefiniëerde fretboard-diagrammen, maar ze kunnen ook ingrijpend veranderd worden voor vrijwel elke andere situatie.

chart

(Klik om te vergroten)

Grote projecten

LilyPond is uitstekend voor grote projecten zoals opera’s of werken voor groot symfonieorkest. Daarnaast levert de tekstgebaseerde invoer een grotere toegankelijkheid – dit voorbeeld is een bijdrage van Hu Haipeng, een blinde componist.

orchestra

(Klik om te vergroten)

En nu?

Nog steeds niet overtuigd? LilyPond is Vrije Software, die jou Vrijheid geeft. Heb je al besloten LilyPond te gaan proberen, lees dan eerst over onze Tekstinvoer.


Vrijheid

Vrije Software

GNU LilyPond is geschreven en wordt onderhouden door een groep enthousiaste liefhebbers. Het wordt uitgebracht onder de GNU General Public License (GNU Algemene Publieke Licentie) en de GNU Free Documentation License (GNU Vrije Documentatie Licentie), hetgeen iedereen de vrijheid geeft het programma te verbeteren, veranderen en uit te breiden. Het maken van prachtige muziek zou geen honderden euro’s aan software moeten kosten!

Wat zijn de voordelen voor gebruikers?

  • Geen kosten: download en probeer het! Wat heb je te verliezen?
  • Delen: als het programma je bevalt, geef dan een kopie aan je vrienden, docenten, studenten, en collega’s.
  • Broncode beschikbaar: als je benieuwd bent hoe LilyPond bepaalde notatie maakt, kun je precies zien hoe het in zijn werk gaat.
  • Uitbreidbaar: je kunt functies toevoegen, fouten repareren, en de functionaliteit veranderen. Als je geen programmeur bent, kun je iemand inhuren die het voor je doet.

    Dit mag misschien niet zo aantrekkelijk lijken voor sommige muzikanten, maar de mogelijkheid om software uit te breiden kan van groot belang zijn voor serieuze componisten, bedrijven en wetenschappers.

  • Veilige toekomst: als een commerciëel bedrijf bankroet gaat, wat gebeurt er dan met de elektronische muziek die afhankelijk is van hun producten? Dit bezwaar bestaat niet met LilyPond; zelfs wanneer het gehele ontwikkelteam ermee stop (bijzonder onwaarschijnlijk), zal het programma nog steeds legaal beschikbaar zijn om te kopiëren, wijzigen en te distribueren.

Waarom “geven” LilyPond-ontwikkelaars hun werk gratis “weg”?

De meesten van ons zien het ontwikkelen van LilyPond als een hobby of als vrijwilligerswerk. Dus de vraag is eigenlijk “waarom willen mensen vrijwilliger zijn”?

  • Plezier: naar een doel toewerken kan prettig zijn, vooral wanneer je het met een team doet!
  • Gedeelde doelen: we willen allemaal prachtige bladmuziek, maar weinig mensen hebben de expertise (en niemand heeft de tijd!), om een programma te maken dat alle situaties aan kan. Door samen te werken – één verbetert de automatische waardestreepcode, een ander verbetert de vorm van de legatoboogjes, en een derde schrijft documentatie waarin wordt uitgelegd hoe je deze functies kunt gebruiken – kunnen we samen onze doelen bereiken met een fractie van de individuele inzet.
  • “Geef-cultuur”: de Vrije Software beweging heeft veel geweldige software projecten opgeleverd, zoals GNU/Linux, Mozilla Firefox, en Battle for Wesnoth. Omdat ze van deze projecten geprofiteerd hebben, willen sommige ontwikkelaars iets “terug doen” voor de community.
  • Werkervaring: bijdragen aan vrije software projecten is een mooie manier om te oefenen met programmeren, het schrijven van documentatie, het vertalen van documentatie, of ontwerpen. Deze ervaring heeft sommige ontwikkelaars zelfs een baan of een beurs opgeleverd.

En nu?

Nog steeds niet overtuigd? Lees ons uitgebreide essay over onze graveerfilosofie in Achtergrond. Heb je al besloten LilyPond te gaan proberen, lees dan eerst over onze Tekstinvoer.


Achtergrond

Achtergrond essay

We hebben een uitgrebreid essay waarin we onze berekende esthetiek uiteenzetten: de kunst van de creatie van schoonheid met de computer.

Als je slechts een snelle inleiding in LilyPond wilt, is het essay wellicht wat te veel stof om nu door te lezen. Als je het leuk zou vinden het nu te lezen, ga dan verder naar Essay.

En nu?

Nog steeds niet overtuigd? Lees over Producties en bladmuziek van enkele van onze gebruikers. Heb je al besloten LilyPond te gaan proberen, lees dan eerst over onze Tekstinvoer.


Producties

Concerten

LilyPond gravures zijn wereldwijd gebruikt voor uitvoeringen. Enkele hoogtepunten:

Uitgegeven bladmuziek

  • Mutopia Project, bladmuziek voor meer dan 1500 klassieke muziekstukken vrij te downloaden, de voornaamste verzameling van LilyPond partituren.
  • Etude, “bladmuziek op steroïden” is een iPhone app die pianomuziek toont die gezet is met LilyPond, inclusief vele stukken uit Mutopia. De app heeft een virtueel pianoklavier waarop is te zien welke toetsen aangeslagen worden om beginners te helpen bladmuziek lezen.
  • Adoro Music Publishing, partituren van hoge kwaliteit van religieuze muziek, beschikbaar voor directe download of ouderwets op papier.
  • The Shady Lane Publishing, een “micro muziekuitgeverij” met als doelstelling het promoten van een nieuwe vorm van muzikale economie, die dichter bij de muzikanten en muziekliefhebbers staat.

If you are aware of any other concerten of bladmuziek which could be listed here, please let us know by following the instructions on Bug reports.

En nu?

Nog steeds niet overtuigd? Lees de Recenties van enkele van onze gebruikers. Als je het leuk zou vinden het nu te lezen, ga dan verder naar Essay.


Recenties

Gepubliceerde artikelen

  • april 2011

    Linux Magazine publiceert een artikel getiteld Projects on the Move. Het is een inleiding in MuseScore,

    LilyPond en Chordii. Auteur Carla Schroder schrijft “LilyPond wordt aangestuurd vanaf de commandoregel, maar je niet afschrikken door het ontbreken van een GUI; LilyPond is gebruiksvriendelijk en gemakkelijk te leren”, en ze geeft een direct te gebruiken voorbeeld.

    +

  • mei 2010

    Peter Kirn, op de Create Digital Music website, publiceert een LilyPond recentie. Hij neemt een evenwichtig standpunt in over gebruik, prijst LilyPonds hoge kwaliteit van notatie en stelt voor het zelf uit te proberen.

  • september 2009

    Het Duitse blad LinuxUser schrijft een artikel over LilyPond.

  • augustus 2009

    Ann Drinan, op de Polyphonic.org website, presenteert opmerkingen van twee orkestbibliothekarissen die praten over het gebruik van software om hun bibliotheken te onderhouden.

  • juni 2009

    In een artikel gepubliceerd in het Franse National Conservatory Parent Association’s jaarblad, legt de Franse componist en LilyPond-bijdrager Valentin Villenave uit waarom Vrije licenties, en in het bijzonder LilyPond-gegraveerde partituren, van instrumenteel belang zijn in het voor iedereen toegankelijk maken van genoteerde muziek.

  • februari 2008

    In artikelen op zijn persoonlijke site vergelijkt Andrew Hawryluk Finale en LilyPond in algemene termen, en evalueert muzieknotatie-mogelijkheden van beide programma’s in detail. Het tweede artikel is een leerzame analyse van muzieknotatie-kwesties in Rachmaninoff’s Piano Prelude No. 6, inclusief vergelijkingen met een hand-gegraveerde referentie-uitgave.

  • juni 2006

    DistroWatch complimenteert LilyPond en schrijft “Dames en Heren, wij zijn blij te mogen aankondingen, gebaseerd op verzoeken van lezers, dat de donatie van DistroWatch mei 2006 is toegekent aan LilyPond (€190.00) en Lua (US$250.00).”

  • december 2005

    Linux Journal publiceert een artikel getiteld Maak verbluffende Schenker gravures met GNU LilyPond. Het is een diepgaand maar praktisch uitgelicht artikel met scherp gestoken LilyPond-gravures. Auteur Kris Shaffer merkt op dat “GNU LilyPond prachtige gravures maakt die commerciële alternatieven op tweede-rangs laat lijken.”

  • 20 augustus, 2005

    Het Belgische dagblad De Standaard onderzoekt wat Free Software auteurs bezield in een artikel getiteld Delen van KENNIS zonder WINSTBEJAG in de ‘DS2-bijlage’. LilyPond wordt als een voorbeeld gebruikt en het artikel is doorlucht met citaten van een e-mail interview met Jan Nieuwenhuizen. Dit is LilyPonds eerste optreden in mainstream gedrukte pers.

  • june 2005

    Een Frans artikel over de LilyPond 2.6 uitgave verschijnt op linuxfr.org.

  • oktober 2004

    De redacteurs van of Computer!Totaal, een Nederlands computerblad, beschrijven LilyPond in het oktober 2004-nummer als: “Prachtige gratis (open source) software [..] De bladmuziek die LilyPond oplevert is inderdaad bijzonder fraai [..] een zeer krachtig systeem waarvoor bijna niets onmogelijk is.”

  • juli, augustus 2004

    Dave Phillips schrijft een inleidend artikel voor Linux Journal: Aan de klinkende rand: LilyPond, delen een en twee.

  • maart 2004

    Chris Cannam interviewt Han-Wen Nienhuys en Jan Nieuwenhuizen op linuxmusician.com (originele site opgeheven). Dit interview is gerecenceerd in een slashdot artikel.

  • februari 2004

    Jazz-zanger Gail Selkirk schrijft over Duik in LilyPond. “... je kunt make lead sheets of volledige orkestpartituren maken, en de resultaten kunnen verbluffend zijn.” Computer Music Special, nummer CMS06.

Gebruikerservaringen

carter-brey

Carter Brey, Aanvoerder van de celli, New York Philharmonic

“…Ik heb een paar toegiften geschreven voor solo-cello die ik heb afgedrukt met LilyPond en die ik aan Schirmer zal voorleggen ter publicatie. Ik weet zeker dat hun gegraveerde versie niet half zo gelikt is als de mijne!”

orm-finnendahl

Orm Finnendahl, professor in de compositieleer, Musikhochschule Freiburg

“Hoewel ik [LilyPond] nog niet zo goed ken, ben ik erg onder de indruk. Ik heb het programma gebruikt om een motet van Josquin Desprez in te voeren in mensurale notatie. Lilypond overtreft zonder twijfel en met gemak alle andere muzieknotatieprogramma’s voor wat betreft snelheid, gebruiksgemak en schoonheid!”

darius-blasband

Darius Blasband, componist (Brussels, Belgium)

“[..na de eerste orkestrepetitie] kreeg ik heel veel complimenten over de kwaliteit van de partituren. En wat nog veel mooier is: terwijl Lilypond allerlei manieren biedt om te zorgen dat de partituren er nog mooier uitzien, kreeg het orkest van mij slechts de ruwe, ongewijzigde LilyPond-output.”

Kieren MacMillan, componist (Toronto, Canada)

“Dank en lof voor het ontwikkelteam voor hun fantastische werk. Ik heb nog nooit iets gezien wat maar in de buurt komt van de output die ik bereik met Lilypond – Ik ben er zeker van dat dit fantastische programma aan al mijn muziekpublicatie-wensen kan voldoen en deze zelfs zal overtreffen. [..] hoofdzakelijk pure Lilypond output [..] ziet er beter uit dan de meeste recente ‘professionele’ uitgaven waarmee ik het heb vergeleken (q.v., zo ongeveer elke Warner Bros. partituur, en zelfs een groot deel van de meest recente partituren van de ‘de oude muziekuitgeverijen’). [..]”

“Doe ze dat maar eens na, Finale/Sibelius/Igor/of wie dan ook!!!”

Chris Cannam, hoofdontwikkelaar van het RoseGarden project

“LilyPond is overduidelijk een zwaargewicht [in de categorie prachtige muziek zetten].”

Chris Snyder, Adoro Music Publishing

“De wijze waarop muziek wordt ingevoerd voor LilyPond laat mij op een muzikalere manier denken – het is enkele malen voorgekomen dat ik vertwijfeld was hoe ik Lelie nu zou kunnen vertellen iets te graveren, om mezelf te realiseren dat zelf wanneer het me precies zo zou lukken als de componist het wilde, de muziek lastig te lezen zou zijn. LilyPond maakt het mij een stuk eenvoudiger om in mijn dubbele redacteur+graveer rol te werken.”

“Voor mijn beginnende muziekuitgeverij heb ik uitsluitend LilyPond gebruikt. Vrijwel zonder uitzondering werd elke componist overrompeld door de kwaliteit van de gravure waneer ik hem de proefdrukken van zijn muziek presenteerde. Ik verdien zelf ook een deel van deze lof – ik heb veel tijd besteed aan het verfijnen van de uitvoer, met name overbindingen (hoofdzakelijk in akkoorden) – maar LilyPond biedt me een uitstekend uitgangspunt, een erg intuïtieve interface, plus de mogelijkheid om absoluut alles te veranderen als ik daar de tijd voor wil nemen. Ik ben ervan overtuigd dat geen commercieel product hierbij ook maar enigszins in de buurt kan komen.”

David Bobroff, bastrombonist, Iceland Symphony Orchestra

“Ik vind Lilypond fantastisch [..] Hoe beter ik het programma leer kennen, hoe mooier ik het vind!”

Vaylor Trucks, elektrische gitaar (Ja, verwant aan)

“Ik ben zwaar onder de indruk van LilyPond [..]”

“DIT IS HET BESTE PROGRAMMA OOIT!!!”

“ENORM bedankt allemaal voor jullie fantastische werk en toewijding!”

Nicolas Sceaux, Mutopia bijdrager

“Ik had een soort haat/liefde-verhouding met LilyPond. Liefde omdat de eerste partituur die ik zag er zo fantastisch uit zag! De beschrijving van de elegantie van LilyPond klopt niet, het is nog veel mooier! [..] aangezien LilyPond nog altijd beter wordt, en naarmate ik beter doorzie hoe dingen worden gedaan in scheme, heb ik steeds minder last van frustraties. Nouja, wat ik eigenlijk wil zeggen is: dank jullie wel voor LilyPond, het is prachtig.”

Werner Lemberg, Dirigent bij het Theater van Koblenz in Duitsland en een befaamde GNU-hacker

“Hoe dan ook, LilyPond levert een verbazingwekkend goed resultaat!”

Paul Davis, ontwikkelaar van JACK en Ardour

“Ik vind [LilyPond] een ongelofelijk programma, en het produceert prachtige, schitterende output. Toen ik vorig jaar een interview over LilyPond las, kon ik niet wachten om aan een paar vrienden van mij te laten zien hoeveel potentie het wel niet heeft.”

Dr. Mika Kuuskankare, onderzoeker aan de Sibelius Academy Finland, componist en auteur van Expressive Notation Package (ENP)

“Ik heb het diepste respect voor LilyPond en haar scheppers en beheerders omdat ik uit persoonlijke ervaring weet hoe moeilijk dit soort software kan zijn.”

David Cameron, Muzikant, professioneel typesetter en sinds lang SCORE-gebruiker

“Mijn hartelijke dank aan iedereen die bijdraagt​aan dit project. Ik was een power SCORE-gebruiker voor grote zetwerk huizen lang geleden in de jaren ’90, maar voor mijn gevoel maakt LilyPond het mogelijk om precies datgene op papier te krijgen wat ik wil, in het bijzonder als het niet "standaard" praktijk is.”

If you are aware of any other nieuwsberichten of gebruikerservaringen which could be listed here, please let us know by following the instructions on Bug reports.

En nu?

Lees over onze Tekstinvoer.


Tekstinvoer

Muziek “Compileren”

nereid-shot-small

(klik om te vergroten)

LilyPond is een batch programma: het wordt uitgevoerd op een tekstbestand waarin de muziek wordt beschreven. Het resultaat kan op het beeldscherm worden bekeken of worden afgedrukt. In bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma.

Je schrijft de muziek niet door noten van een grafische werkbalk naar een zichzelf dynamisch verversende partituur te slepen; je schrijft muziek door het intypen van tekst. Deze tekst word geïnterpreteerd (of “gecompileerd”) door LilyPond, die hiervan prachtig gegraveerde bladmuziek maakt.

Mensen die gewend zijn aan een grafische gebruikersinterface moeten wellicht een nieuwe manier van werken aanleren, maar de resultaten zijn de moeite meer dan waard!

Nota bene : We presenteren een kort overzicht van onze tekstinvoer – het is niet zo ingewikkeld als het klinkt! Maak je geen zorgen, je hoeft niet elk detail in deze voorbeelden te begrijpen; in onze beginnershandleiding wordt alles stap voor stap uitgelegd.

Waarom moeilijk doen als het ook makkelijk kan?

Noten worden gecodeerd met letters en nummers. Speciale commando’s worden ingevoerd met een backslash.

text-input-1-annotate-nltext-input-1-output

Verplaatsingen worden gevormd met verschillende benamingen: voeg -is toe voor een kruis en -es voor een mol. LilyPond bepaalt zelf waar de toevallige tekens geplaatst worden.

text-input-2-annotate-nltext-input-2-output

Popmuziek

Combineer akkoorden en songteksten om zogenaamde leadsheets te maken:

text-input-pop-annotate-nltext-input-pop-output

Orkestpartijen

Het invoerbestand bevat de noten van het muziekstuk. Partituur en partijen kunnen vanuit dit zelfde invoerbestand worden gemaakt. Dus het veranderen van een noot heeft altijd invloed op partijen en partituur, zodat beide altijd up-to-date zijn. Om dezelfde muziek op verschillende plaatsen te kunnen invoegen, moet aan de noten een “variable” (een naam) worden toegekend.

text-input-parts-both-annotate-nl

Deze variabele wordt vervolgens in één partij gebruikt (hier getransponeerd en met samengevoegde rusten):

text-input-parts-single-annotate-nltext-input-parts-single-output

Dezelfde variabele wordt ook in de volledige partituur gebruikt (hier klinkend en met uitgeschreven rusten):

text-input-score-annotate-nltext-input-score-output

Beginnershandleiding

We realiseren ons dat veel gebruikers deze manier van muziek invoeren een beetje vreemd vinden. Daarom hebben we een uitgebreide handleiding geschreven om nieuwe gebruikers op weg te helpen, te beginnen met Beginnen. Het beste kun je beginnen met deze beginnershandleiding omdat hierin de meeste vragen worden beantwoord.

Lees liever eerst de beginnershandleiding alvorens eventuele fouten in het programma aan ons te melden! Nieuwe gebruikers denken soms dat LilyPond niet goed werkt, terwijl het in feite precies werkt zoals de bedoeling is.

Verdere informatie is beschikbaar in Handleidingen.

Omgevingen voor eenvoudiger bewerken

Tunefl

pictures/logo-linux pictures/logo-freebsd pictures/logo-macosx pictures/logo-windows

http://www.tunefl.com

Met tunefl kun je partituren direct online zetten, zonder LilyPond op je computer te installeren. Het is mogelijk om alle functies van het programma te proberen in een eenvoudige web interface.

lilykde-screenshot-small

(klik om te vergroten)

LilyPond gaat hoofdzakelijk over het produceren van gegraveerde bladmuziek van topkwaliteit; het maken van een Grafische Gebruikers Interface (GUI) zou ons enkel van dit doel afleiden. Er zijn wel andere projecten die als doel hebben het maken van LilyPond-invoer gemakkelijker te maken.

Sommige omgevingen hebben syntax highlighting, automatische commando aanvulling, en voorbereide sjablonen. Andere programma’s bieden een GUI die directe manipulatie van een grafische partituur mogelijk maakt. Voor meer informatie, zie Eenvoudiger bewerken.

En nu?

Je bent nu zover om LilyPond te downloaden. Nog steeds niet overtuigd? Lees over Eenvoudiger bewerken.


Eenvoudiger bewerken

LilyPondTool

lilypondtool-2.12-screenshot-400wide

(klik om te vergroten)

pictures/logo-linux pictures/logo-freebsd pictures/logo-macosx pictures/logo-windows

http://lilypondtool.organum.hu

Gemaakt als een plugin voor de jEdit teksteditor, is LilyPondTool één van de tekstgebaseerde gereedschappen met de meeste functies voor het bewerken van LilyPond-partituren. Functies omvatten een Document-wizard met liedtekstondersteuning om documenten eenvoudiger op te stellen, en geïntegreerde PDF-viewer met geavanceerde point-and-click ondersteuning.

Frescobaldi

frescobaldi-lilypond-editor-small

(klik om te vergroten)

pictures/logo-linux pictures/logo-freebsd pictures/logo-windows

http://www.frescobaldi.org

Frescobaldi is een LilyPond bladmuziek-editor. Krachtig, lichtgewicht en gemakkelijk te gebruiken en met ingebouwde PDF viewer. Het draait op alle belangrijke platformen (GNU/Linux, Mac OS X en Windows).

Grafische omgeving: Denemo

screenshot-denemo-small

(klik om te vergroten)

pictures/logo-linux pictures/logo-windows

http://denemo.org

Denemo is een grafische editor die LilyPond-broncode genereert, en ook audio afspeelt. Hiermee kunnen gebruikers LilyPond-broncode parallel weergeven met het grafische beeld. Extra LilyPond-verfijningen (tweaks) kunnen aan noten, akkoorden enz. worden gekoppeld en worden opgeslagen in het Denemo-bestand, zodat gebruikers toch grafisch verder kunnen bewerken.

Het verplaatsen van de cursor in de LilyPond-tekst verplaatst ook de cursor in het grafische beeld, en syntaxfouten in LilyPond-verfijningen (tweaks) worden gehighlight in het tekstvenster.

Tekst omgeving

pictures/logo-linux pictures/logo-freebsd pictures/logo-macosx pictures/logo-windows

http://elysium.thsoft.hu

Elysium is een LilyPond-omgeving (IDE) voor Eclipse met een geïntegreerd beeld voor broncode en partituur naast elkaar. Het heeft snelle visuele en auditieve terugkoppeling zonder te hoeven schakelen, en heeft veel wizard-gebaseerde sjablonen.

http://www.gnu.org/software/emacs/

Emacs is een teksteditor met taalgevoelige functies voor veel verschillende computertalen. Emacs is een in hoge mate uitbreidbare editor en kan gebruikt worden als een Geïntegreerde Ontwikkel Omgeving (IDE). Er is een ‘lilypond mode’ die de taaldefinities voor het werken met LilyPond-broncodebestanden levert. Verder heeft een van onze ontwikkelaars lyqi geschreven, een Emacs major mode.

http://www.vim.org

Vim is een minimale teksteditor en is een uitbreiding van de oudere Unix vi-editor. Het is uitbreidbaar en configureerbaar.

Als algemene regel geldt dat, wanneer je nog niet bekend bent met Emacs of Vim, je waarschijnlijk liever een andere editor verkiest voor het schrijven van LilyPond-invoerbestanden.

Meer informatie over instellingen voor Emacs en Vim is te vinden in Text editor support.

pictures/logo-macosx

http://www.uoregon.edu/~koch/texshop

De TexShop-editor voor MacOS X kan uitgebreid worden voor het uitvoeren van LilyPond, lilypond-book en convert-ly vanuit de editor, door gebruik te maken van de uitbreidingen die beschikbaar zijn op:

http://users.dimi.uniud.it/~nicola.vitacolonna/home/content/lilypond-scripts

Programma’s die LilyPond-code kunnen exporteren

Score, tab en MIDI-editors:

Gereedschappen voor de commandoregel

Andere programma’s die niet actief worden ontwikkeld

En nu?

Je bent nu zover om LilyPond te downloaden.

Nog steeds niet overtuigd? Veel componisten, muzikanten en drigenten hebben geleerd muziek te schrijven in ons invoerformaat. Ervaren gebruikers melden dat ze een volledige partituur sneller kunnen invoeren in LilyPond dan met een pianoklavier of muis+GUI! Misschien wil je de Functies, Voorbeelden of Vrijheid herlezen, of wil je lezen over Producties en Recenties van gebruikers. Onze aanpak van berekende esthetiek van klassieke muziekgravure wordt beschreven in Achtergrond.

Legalese


Download

Downloads voor LilyPond 2.19.5

Nota bene : Links voor de stabiele versie van LilyPond staan op lilypond.org

Nota bene : LilyPond is een tekstgebaseerd muzieknotatieprogramma; in bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma. Voordat je LilyPond download, lees dan eerst de informatie over onze Tekstinvoer.

Software-licentie

LilyPond is uitgegeven onder de GNU General Public License (GNU Algemene Publieke Licentie).

Sponsors

Hartelijk dank aan Virginia Tech en linuxaudio.org voor het sponsoren van onze bandbreedte.

pictures/VTlogo_ITF pictures/lao_banner_06_on_white_demo

Legalese


Unix

Nota bene : LilyPond is een tekstgebaseerd muzieknotatieprogramma; in bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma. Voordat je LilyPond download, lees dan eerst de informatie over onze Tekstinvoer.

Generieke pakketten of distributie-pakketten?

Veel Linux-distributies (zoals Fedora, openSUSE, Ubuntu) leveren LilyPond mee als onderdeel van hun normale software-pakketsysteem. Zo’n LilyPond-pakket is eenvoudiger te installeren en verwijderen dan een generiek pakket, maar het kan een verouderde versie zijn. Als je liever één van onze generieke pakketten wilt gebruiken, verwijder dan eerst de officiële versie van LilyPond met het normale pakketbeheer van je distributie (softwarecentrum). Zie de documentatie van je distributie voor hoe je het pakketbeheer of softwarecentrum gebruikt.

Generieke pakketten

Download

Installeren

Op de commandoregel, typ:

cd PAD-NAAR-DOWNLOAD-MAP # waarschijnlijk: cd Downloads
sh lilypond-2.18.2-OS-TYPE.sh

Verwijderen

Op de commandoregel, typ:

uninstall-lilypond

Hulp

Op de commandoregel, typ:

sh lilypond-2.18.2-OS-TYPE.sh --help

Een bestand compileren

Nota bene : Deze instructies veronderstellen dat je vertrouwd bent met het gebruik van de commandoregel. Als je een van de andere programma’s gebruikt die beschreven staan in Eenvoudiger bewerken, raadpleeg dan de documentatie voor dat programma als je problemen hebt met het compileren van een bestand.

Stap 1. Maak je ‘.ly’-bestand

Maak een tekstbestand met de naam ‘test.ly’ en vul het met:

\version "2.18.2"
{
  c' e' g' e'
}

Stap 2. Compileren (op de commandoregel)

Om het ‘test.ly’-bestand te compileren, typ op de commandoregel:

lilypond test.ly

Je ziet dan iets dat lijkt op:

GNU LilyPond 2.18.2
Verwerken van `test.ly'
Ontleden...
Vertolken van muziek...
Voorbewerken van grafische objecten...
Berekenen van 1 pagina-afbreek brokken...[1: 1 pagina's]
Tekenen van systemen...
Opmaakuitvoer naar `test.ps'...
Converteren naar `./test.pdf'...
Success: compilation successfully completed

Stap 3. Bekijk de uitvoer

Je kunt het resulterende ‘test.pdf’-bestand bekijken of printen.

Distributie-pakketten

Gebruik het pakketbeheer (softwarecentrum) van je distributie voor het upgraden naar deze versies.

Legalese


MacOS X

Nota bene : LilyPond is een tekstgebaseerd muzieknotatieprogramma; in bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma. Voordat je LilyPond download, lees dan eerst de informatie over onze Tekstinvoer.

Pakketten

Download

Installeren

Dubbelklik het gedownloade bestand, sleep het dan naar de plaats waar je het wilt hebben.

Verwijderen

Verwijder de LilyPond.app map.

Een bestand compileren

Nota bene : Deze instructies veronderstellen dat je de de LilyPond applicate gebruikt. Als je een van de andere programma’s gebruikt die beschreven staan in Eenvoudiger bewerken, raadpleeg dan de documentatie voor dat programma als je problemen hebt.

Stap 1. Maak je ‘.ly’-bestand

Dubbelklik de LilyPond.app, een voorbeeldbestand wordt geopend.

pictures/Learning_Macos_welcome

Uit de menu’s links bovenaan je scherm, kies Bestand > Opslaan.

pictures/Learning_Macos_Save_menu

Kies een naam voor je bestand, bijvoorbeeld ‘test.ly’.

pictures/Learning_Macos_Save_file_with_name

Stapp 2. Compileer (met LilyPad)

Uit dezelfde menu’s, kies Compile > Tyepset.

pictures/Learning_Macos_Typeset_menu

Een nieuw venster opent en toont een voortgangslog van de compilatie van het bestand dat je zojuist hebt opgeslagen.

pictures/Learning_Macos_Compiling_log

Stap 3. Bekijk de uitvoer

Zodra de compilatie klaar is, wordt een PDF-bestand gemaakt met dezelfde naam als het originele bestand en dat wordt automatisch geopend in de standaard PDF-viewer en op je scherm getoond.

pictures/Learning_Macos_pdf_output

Andere commando’s

Een nieuw LilyPond bestand maken, doe je door het kiezen van Bestand > Nieuw

pictures/Learning_Macos_New_menu

of je opent met Bestand > Openen een bestaand bestand om te bewerken.

pictures/Learning_Macos_Open_menu

Als je een bestand bewerkt hebt, moet je het eerst opslaan voordat je Compile > Typeset doet en als het PDF-bestand niet wordt getoond, controleer dan het venster met de voortgangslog op foutmeldingen.

Als je geen gebruik maakt van de standaard Preview PDF-viewer die onderdeel is van het Mac Operating systeem en je hebt het PDF-bestand van een vorige compilatie nog open staan, dan kan het zijn dan alle volgende compileerpogingen niet slagen in het genereren van een nieuwe PDF totdat je het originele venster sluit.

Uitvoeren op de commandoregel

Nota bene : Als je liever de GUI gebruikt, sla deze instructies dan over.

MacOS X op de commandoregel

De handigste manier om LilyPond-scripts uit te voeren is door middel van het maken van je eigen “hulp”scripts.

  1. Maak een map en sla deze scripts op,
    mkdir -p ~/bin
    cd ~/bin
    
  2. Maak een bestand genaamd lilypond met als inhoud
    #! /bin/bash
    exec MAP/LilyPond.app/Contents/Resources/bin/lilypond "$@"
    

    Nota bene : MAP is normaal gesproken /Applications/

  3. Maak gelijksoortige bestanden lilypond-book, convert-ly, en andere scripts die je wilt gebruiken, door het commando bin/lilypond te vervangen met bin/convert-ly (of een andere programmanaam).
  4. Maak het bestand executeerbaar,
    chmod u+x lilypond
    
  5. Voeg nu deze map toe aan je pad. Wijzig het bestand genaamd .profile in je persoonlijke map (of maak een nieuwe aan) zodat het het volgende bevat
    export PATH=$PATH:~/bin
    

    Het bestand moet eindigen met een lege regel.

Afzonderlijke scripts uitvoeren

De scripts — zoals lilypond-book, convert-ly, abc2ly, en zelfs lilypond — worden meegeleverd met het .app bestand voor MacOS X.

Scripts kunnen ook worden uitgevoerd op de commandoregel door ze direct aan te roepen:

pad/naar/LilyPond.app/Contents/Resources/bin/lilypond

Dat geldt ook voor alle andere scripts in die map, zoals lilypond-book en convert-ly.

Legalese


Windows

Nota bene : LilyPond is een tekstgebaseerd muzieknotatieprogramma; in bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma. Voordat je LilyPond download, lees dan eerst de informatie over onze Tekstinvoer.

Pakketten

Download

Installeren

  1. Zoek het gedownloade bestand en dubbelklik het om het te installeren. Volg de instructies op die de installer je geeft; wij raden je aan alle installatiekeuzes aangevinkt te laten en de standaard aangegeven locatie te gebruiken. Klik op de ‘Finish’ knop als de installer klaar is. LilyPond is nu geïnstalleerd.

Verwijderen

Om LilyPond te verwijderen:

  1. Zoek de LilyPond-map in het menu ‘Start’ en klik op het ‘Uninstall’ icoon. Klik op de ‘Finish’ knop als de uninstaller klaar is.
  2. Ofwel: vanuit het Configuratiescherm, kies Programma’s en onderdelen, zoek en selecteer LilyPond en kies de optie verwijderen/wijzigen. Klik op de ‘Finish’ knop als de uninstaller klaar is.

Een bestand compileren

Nota bene : Deze instructies veronderstellen dat je gebruik maakt van de ingebouwde LilyPad-editor. Als je een van de andere programma’s gebruikt die beschreven staan in Eenvoudiger bewerken, raadpleeg dan de documentatie voor dat programma als je problemen hebt met het compileren van een bestand.

Stap 1. Maak je ‘.ly’-bestand

Dubbelklik het LilyPond ikoon op je Bureaublad, een voorbeeldbestand wordt geopend.

pictures/LilyPad

Kies uit de menu’s bovenaan het voorbeeldbestand Bestand > Opslaan als. De optie Bestand > Opslaan kun je voor dit voorbeeldbestand niet gebruiken als je het nog geen geldige LilyPond-naam hebt gegeven.

pictures/FileSave

Kies een naam voor je bestand, bijvoorbeeld ‘test.ly’.

pictures/SaveAs

Stap 2a. Compileer (door slepen en neerzetten - drag and drop)

Afhankelijk van wat je voorkeur heeft, compileer je je bestand door ofwel:

te slepen en neer te zetten bovenop het LilyPond ikoon, ofwel

pictures/DragDrop

met de tweede muisknop op het bestand te klikken en uit het popup-contextmenu Open met > LilyPond te kiezen.

pictures/GenPDF

Stap 2b. Compileer (door te dubbelklikken)

Of dubbelklik het ‘test.ly’ bestand.

Stap 3. Bekijk de uitvoer

Tijdens het compileren van het ‘test.ly’ bestand, wordt een commandovenster geopend dat zich na korte tijd weer sluit. Tijdens dit proces worden drie extra bestanden aangemaakt.

Het PDF-bestand bevat het gegraveerde ‘test.ly’ bestand.

pictures/GenPDF

Andere commando’s

Om een nieuw bestand te maken, kies Bestand > Nieuw vanuit een eerder gemaakt bestand of gebruik Bestand > Openen om een eerder gemaakt bestand te openen en te bewerken.

Als je een bestand bewerkt hebt, moet je het eerst opslaan voordat je het compileert en als het PDF-bestand niet wordt aangemaakt, controleer dan het venster met de voortgangslog op foutmeldingen.

pictures/BadLog

Dit logbestand wordt elke keer overschreven als je je LilyPond-bestand compileert.

Het PS-bestand wordt LilyPond intern gebruikt als tussenstap om het PDF-bestand aan te maken, je kunt het verder negeren. Dit bestand wordt ook elke keer overschreven als je je LilyPond-bestand compileert.

Als je je bestand bekijkt met een PDF-viewer, dan moet je de PDF sluiten als je een nieuwe compilatie wilt doen omdat het genereren van een nieuwe PDF kan mislukken zolang je de oude nog aan het bekijken bent.

Uitvoeren op de commandoregel

Nota bene : Als je liever de GUI gebruikt, sla deze instructies dan over.

Windows on the command line

De handigste manier om LilyPond uit te voeren is door de map die de LilyPond programmabestanden bevat, toe te voegen aan de omgevingsvariabele “Path”.

  1. In het Configuratiescherm, open “Systeem”, selecteer Geavanceerde systeeminstellingen of het Tab Geavanceerd en klik op de knop ‘Omgevingsvariabelen’.
  2. Selecteer de Variabele “Path” uit de lijst Systeemvariabelen en klik op de knop ‘Bewerken’. Een dialoogvenster met de titel “Systeemvariabele bewerken” verschijnt; voeg aan de “Waarde van variable” de naam van de map toe waarin de LilyPond programmabestanden staan:
    [vooringestelde paden];MAP\LilyPond\usr\bin
    

    Nota bene : MAP is normaal gesproken C:Program Files.

    en klik op de “OK” knop om het dialoogvenster te sluiten.

Afzonderlijke programmabestanden uitvoeren

LilyPond pogrammabestanden – zoals lilypond, lilypond-book, convert-ly, enz. – kunnen op de commandoregel worden uitgevoerd door ze aan te roepen:

lilypond test.ly

Legalese


Broncode

Nota bene : LilyPond is een tekstgebaseerd muzieknotatieprogramma; in bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma. Voordat je LilyPond download, lees dan eerst de informatie over onze Tekstinvoer.

Nota bene : Het zelf proberen te bouwen van LilyPond wordt afgeraden; het is voor vrijwel iedere gebruiker aan te raden om de voorgebouwde versie gebruiken.

Broncode tarball

Broncode: lilypond-2.18.2.tar.gz

Voor een uitgebreide lijst van alle versies (zowel oude als nieuwe), zie onze download site.

Compileerinstructies

Instructies worden beschreven in Compiling.


Oude downloads

Nota bene : LilyPond is een tekstgebaseerd muzieknotatieprogramma; in bepaalde opzichten lijkt LilyPond meer op een programmeertaal dan op een grafisch muziekprogramma. Voordat je LilyPond download, lees dan eerst de informatie over onze Tekstinvoer.

Alle versies

Voor een uitgebreide lijst van alle versies (zowel oude als nieuwe), zie onze download site.


GPL

Software licentie

GNU LilyPond wordt uitgebracht onder de GNU General Public License (GNU Algemene Publieke Licentie). Een inleiding op deze licentie en de redenen om voor deze keuze, wordt gegeven in Vrijheid.

GNU General Public License

Version 3, 29 June 2007

 
Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Preamble

The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program—to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers’ and authors’ protection, the GPL clearly explains that there is no warranty for this free software. For both users’ and authors’ sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users’ freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS

  1. Definitions.

    “This License” refers to version 3 of the GNU General Public License.

    “Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

    “The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

    To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.

    A “covered work” means either the unmodified Program or a work based on the Program.

    To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

    To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

    An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

  2. Source Code.

    The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.

    A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

    The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

    The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work’s System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

    The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

    The Corresponding Source for a work in source code form is that same work.

  3. Basic Permissions.

    All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

    You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

    Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

  4. Protecting Users’ Legal Rights From Anti-Circumvention Law.

    No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

    When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures.

  5. Conveying Verbatim Copies.

    You may convey verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

    You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

  6. Conveying Modified Source Versions.

    You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

    1. The work must carry prominent notices stating that you modified it, and giving a relevant date.
    2. The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
    3. You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
    4. If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.

    A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

  7. Conveying Non-Source Forms.

    You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

    1. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
    2. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
    3. Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
    4. Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
    5. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

    A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

    A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

    “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

    If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

    The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

    Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

  8. Additional Terms.

    “Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

    When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

    Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

    1. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
    2. Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
    3. Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
    4. Limiting the use for publicity purposes of names of licensors or authors of the material; or
    5. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
    6. Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.

    All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

    If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

    Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

  9. Termination.

    You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

    However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

    Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

    Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

  10. Acceptance Not Required for Having Copies.

    You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

  11. Automatic Licensing of Downstream Recipients.

    Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

    An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party’s predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

    You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

  12. Patents.

    A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor’s “contributor version”.

    A contributor’s “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

    Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor’s essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

    In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

    If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient’s use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

    If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

    A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

    Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

  13. No Surrender of Others’ Freedom.

    If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

  14. Use with the GNU Affero General Public License.

    Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

  15. Revised Versions of this License.

    The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

    Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

    If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

    Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

  16. Disclaimer of Warranty.

    THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  17. Limitation of Liability.

    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

  18. Interpretation of Sections 15 and 16.

    If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.

 
one line to give the program's name and a brief idea of what it does.
Copyright (C) year name of author

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or (at
your option) any later version.

This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see http://www.gnu.org/licenses/.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

 
program Copyright (C) year name of author
This program comes with ABSOLUTELY NO WARRANTY; for details type ‘show w’.
This is free software, and you are welcome to redistribute it
under certain conditions; type ‘show c’ for details.

The hypothetical commands ‘show w’ and ‘show c’ should show the appropriate parts of the General Public License. Of course, your program’s commands might be different; for a GUI interface, you would use an “about box”.

You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see http://www.gnu.org/licenses/.

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html.


Handleidingen

Handleidingen voor LilyPond 2.19.5


Beginnen

Beginnershandleiding

Deze handleiding behandelt de eerste stappen van LilyPond en legt in eenvoudige taal enkele belangrijke concepten uit. Deze hoofdstukken kun je in chronologische volgorde doorlezen.

Er is een alinea Zie ook aan het eind van elke paragraaf met kruisverwijzingen naar andere paragrafen: deze kruisverwijzingen kun je beter niet volgen bij de eerste keer lezen. Als je de gehele beginnershandleiding een keer hebt gelezen, wil je wellicht bepaalde stukken herlezen en kun je deze kruisverwijzingen bijvoorbeeld volgen voor meer informatie.

Read it

  • Beginnen (split HTML) - the manual is split between many HTML pages.
      (small download for each page)
  • Beginnen (big HTML) - read this manual as one huge HTML page.
      (large single download, 1.5 MB)
  • learning.pdf - download as a PDF file.
      (large single download, 3 MB)

Terminologie

Terminologie

Dit verklaart muziektermen en bevat vertalingen in verschillende talen. Als je niet zo bekend bent met muzieknotatie of muziektermen (en vooral als Engels niet je moedertaal is), is het aan te raden deze termijnlijst te raadplegen.

Read it


Essay

Essay

Deze essay geeft een kort overzicht van de geschiedenis van de muziektypografie, gevolgd door een beschouwing van LilyPonds graveertechnieken. Ook wordt er een vergelijking gegeven tussen LilyPond en andere muzieknotatiesystemen.

Nota bene : de gedetailleerde typografische voorbeelden zijn beter te analyseren in de PDF-versie vanwege de veel hogere resolutie.

Read it

  • Essay (split HTML) - the manual is split between many HTML pages.
      (small download for each page)
  • Essay (big HTML) - read this manual as one huge HTML page.
      (large single download, 2 MB)
  • essay.pdf - download as a PDF file.
      (large single download, 2.5 MB)

Notatie

Notatie-handleiding

Deze handleiding behandelt alle LilyPond-commando’s die notatie produceren.

Nota bene : de notatie-handleiding veronderstelt dat de lezer bekend is met het basismateriaal dat besproken is in de beginnershandleiding en met de Engelse termen in de terminologielijst.

Read it


Gebruik

Gebruikshandleiding

Deze handleiding laat zien hoe de programma’s moeten worden uitgevoerd, hoe LilyPond-notatie kan worden gecombineerd en geïntegreerd met andere programma’s, en geeft “goede gebruiken” voor een efficiënt gebruik. Dit is aanbevolen lectuur indien je een groot project wilt beginnen.

Read it

  • Gebruik (split HTML) - the manual is split between many HTML pages.
      (small download for each page)
  • Gebruik (big HTML) - read this manual as one huge HTML page.
      (large single download, 400 KB)
  • usage.pdf - download as a PDF file.
      (large single download, 600 KB)

Snippers

Snippers

Dit toont een geselecteerde set LilyPond-snippers (codefragementen) uit de LilyPond Snippet Repository (LSR). Al deze snippers zijn publiek domein.

Let op dat dit document geen exacte deelverzameling is van de LSR. LSR draait een stabiele versie van LilyPond, dus elke snipper die nieuwe functies demonstreert van een ontwikkelversie moet apart worden toegevoegd. Deze worden opgeslagen in ‘Documentation/snippets/new/’ in de LilyPond source tree.

De lijst met snippers voor elke subsectie van de notatie zijn ook gekoppeld vanuit het Zie ook gedeelte.

Read it

  • Snippers (split HTML) - the manual is split between many HTML pages.
      (small download for each page)
  • Snippers (big HTML) - read this manual as one huge HTML page.
      (large single download, 2.5 MB)
  • snippets.pdf - download as a PDF file.
      (large single download, 8 MB)

FAQ

Vragen bij het begin

Waar zijn het grafische notenwerkblad, de menu’s en de werkbalken?

In LilyPond schrijf je muziek door het invoeren van tekst. Lees alsjeblieft over onze Tekstinvoer.

Er is zo veel documentatie! Moet ik dat allemaal lezen?

Je moet de Beginnershandleiding lezen. Wat betreft de rest van de documentatie, dat is een naslagwerk: je leest alleen die onderdelen die gaan over het soort notatie dat jij wilt produceren.

Maar dat is nog steeds heel veel leeswerk! Is het dat wel de moeite waard?

Oordeel zelf; redenen waarom je LilyPond zou willen gebruiken, worden besproken in de Inleiding.

Gebruikersvragen

Iets werkt er niet! Hoe kan ik dat oplossen?

Dit wordt uitgelegd in Troubleshooting.

Waarom veranderen jullie de syntax?

Dit wordt uitgelegd in change? Why does the syntax change?.


Web

Web

Deze handleiding geeft algemene informatie over LilyPond. Het bevat ook informatie over verschillende gebruikersgroepen en -forums, het sturen van foutrapporten (bug reports) en ontwikkeling.

Lees het

Meest recente handleiding

Web-handleiding in 2.19.5

  • Web (split HTML) - the manual is split between many HTML pages.
      (small download for each page)
  • Web (big HTML) - read this manual as one huge HTML page.
      (large single download, 1 MB)
  • web.pdf - download as a PDF file.
      (large single download, 2 MB)

Veranderingen

Veranderingen

Dit is een overzicht van de belangrijkste veranderingen en nieuwe functies in LilyPond sinds de vorige stabiele versie.

Read it


Uitbreidingen

LilyPond uitbreiden

Deze handleiding laat zie hoe je uitbreidingen maakt voor LilyPond.

Read it


Internals

Internals handleiding

Dit is een set van zwaar kruisgekoppelde pagina’s die de kleinste details van werkelijk elke klasse, object en functie in LilyPond documenteren. Het wordt direct vanuit de layout-definities in de broncode gegenereerd.

Bijna alle layout-functionaliteit die intern wordt gebruikt, is ook direct beschikbaar voor de gebruiker. Bijvoorbeeld, de meeste variabelen die diktes, afstanden enz. bepalen, kunnen in het invoerbestand worden veranderd. Er is een ernorm aantal layout-opties en deze staan allemaal beschreven in dit document. Elk onderdeel van de notatie-handleiding heeft een Zie ook subonderdeel dat verwijst naar deze gegenereerde documentatie.

Read it

  • Internals (split HTML) - the manual is split between many HTML pages.
      (small download for each page)
  • Internals (big HTML) - read this manual as one huge HTML page.
      (large single download, 2.5 MB)
  • internals.pdf - download as a PDF file.
      (large single download, 2.8 MB)

Vertaald

Status van de vertaling

Meest recente update Wed Dec 18 12:23:14 UTC 2013

LilyPond beginnershandleidingVertalersRevisie vertalingVertaaldActueelAndere informatie
Paragraaftitels
124
Jan Nieuwenhuizenjajana-GDP
LilyPond – \TITLE\
1139
Jan Nieuwenhuizenjajavoor-GDP
1 Leerboek
2578
Jan Nieuwenhuizengedeeltelijk (48 %)gedeeltelijkvoor-GDP
2 Algemene muzieknotatie
4396
Jan Nieuwenhuizengedeeltelijk (35 %)gedeeltelijkvoor-GDP
3 Fundamentele concepten
11144
Jan Nieuwenhuizenjagedeeltelijkvoor-GDP
4 Tweaking output
16191
Jan Nieuwenhuizengedeeltelijk (98 %)gedeeltelijkvoor-GDP
A Templates
372
Jan Nieuwenhuizenjajavoor-GDP
LilyPond – Muzieknotatie voor iedereenVertalersRevisie vertalingVertaaldActueelAndere informatie
Paragraaftitels
616
Jan NieuwenhuizenTineke de Munnikjajana-GDP
LilyPond – \TITLE\
1139
Jan NieuwenhuizenTineke de Munnikjajavoor-GDP
Inleiding
4937
Jan NieuwenhuizenTineke de Munnikjagedeeltelijkvoor-GDP
Download
1201
Jan NieuwenhuizenTineke de Munnikjagedeeltelijkvoor-GDP
Handleidingen
1284
Jan NieuwenhuizenTineke de Munnikjagedeeltelijkvoor-GDP

Alles

Te downloaden versies

Tarballen voor downloaden uitsluitend beschikbaar op http://lilypond.org

Previous stable versions


FDL

Documentatie-licentie

De documentatie voor GNU LilyPond is uitgegeven onder de GNU Free Documentation License. Een inleiding op deze licentie en onze redenen om hiervoor te kiezen, wordt gegeven in Vrijheid.

GNU Free Documentation License 1.1

Version 1.3, 3 November 2008

 
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
http://fsf.org/

Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
  1. PREAMBLE

    The purpose of this License is to make a manual, textbook, or other functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

    This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

    We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

  2. APPLICABILITY AND DEFINITIONS

    This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

    A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

    A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

    The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

    The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

    A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”.

    Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

    The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.

    The “publisher” means any person or entity that distributes copies of the Document to the public.

    A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition.

    The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

  3. VERBATIM COPYING

    You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

    You may also lend copies, under the same conditions stated above, and you may publicly display copies.

  4. COPYING IN QUANTITY

    If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

    If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

    If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

    It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

  5. MODIFICATIONS

    You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

    1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
    2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
    3. State on the Title page the name of the publisher of the Modified Version, as the publisher.
    4. Preserve all the copyright notices of the Document.
    5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
    6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
    7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice.
    8. Include an unaltered copy of this License.
    9. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
    10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
    11. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
    12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
    13. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version.
    14. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section.
    15. Preserve any Warranty Disclaimers.

    If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.

    You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

    You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

    The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

  6. COMBINING DOCUMENTS

    You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

    The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

    In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.”

  7. COLLECTIONS OF DOCUMENTS

    You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

    You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

  8. AGGREGATION WITH INDEPENDENT WORKS

    A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

    If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

  9. TRANSLATION

    Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

    If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

  10. TERMINATION

    You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.

    However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

    Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

    Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.

  11. FUTURE REVISIONS OF THIS LICENSE

    The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

    Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Document.

  12. RELICENSING

    “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site.

    “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.

    “Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document.

    An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.

    The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.

ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

 
  Copyright (C)  year  your name.
  Permission is granted to copy, distribute and/or modify this document
  under the terms of the GNU Free Documentation License, Version 1.3
  or any later version published by the Free Software Foundation;
  with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
  Texts.  A copy of the license is included in the section entitled ``GNU
  Free Documentation License''.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with…Texts.” line with this:

 
    with the Invariant Sections being list their titles, with
    the Front-Cover Texts being list, and with the Back-Cover Texts
    being list.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.


Community


Contact

User Discussions and Help

User mailing list: lilypond-user@gnu.org

This mailing list is the main place for users to discuss and help each other.

lilypond-user subscribe and info

user archive1 archive2 archive3

send to lilypond-user with gmane

Nota bene : When asking questions, please use Tiny examples!

LilyPond Snippet Repository

The LilyPond Snippet Repository is a large collection of user-submitted examples, which can freely be copied and used in your own works. See what other people have written, and add your own!

http://lsr.dsi.unimi.it

Particularly instructive examples from LSR are included in our official documentation, in Snippers.

IRC

Some level of support is provided on our IRC channel,

#lilypond@irc.freenode.net

This channel has no public archive, so any question that may be useful for others would better be posted to one of the mailing lists.

irc name:

Other languages

Spanish mailing list

German forum

Portuguese group

French mailing list

Dutch forum

Stay Informed

LilyPond Report

The easiest way to keep touch is by reading our community newsletter, the LilyPond Report:

http://news.lilynet.net

Releases mailing list: info-lilypond@gnu.org

This mailing list is a low-volume, read-only list which receives notifications of new releases.

info-lilypond subscribe and info

info archive1 archive2 archive3

Developer Discussion

Developer mailing list: lilypond-devel@gnu.org

Most developer discussion takes place on this list. Patches should be sent here.

lilypond-devel subscribe and info

devel archive1 archive2 archive3

send to lilypond-devel with gmane

Bug mailing list: bug-lilypond@gnu.org

Bug-specific discussion takes place here.

bug-lilypond subscribe and info

bug archive1 archive2 archive3

Nota bene : Before sending a message to the bug list, please read our guidelines for Bug reports.

Sensitive emails

Private matters should be sent to Graham Percival (project manager), who will discuss it with those concerned.


Tiny examples

What are “Tiny examples”?

A tiny example is an example from which nothing can be removed.

Why create them?

  • The simpler the example is, the quicker potential helpers can understand it and help you.
  • A tiny example demonstrates that you have put effort towards solving the problem yourself. When people send huge portions of input, it looks like they don’t care if we help them or not.
  • Creating a tiny example helps you to understand what is happening. Many false problem reports can be avoided by attempting to create a tiny example; if you cannot replicate a “bug” in a tiny example, then the problem was probably an insufficient understanding of LilyPond, not an actual bug!

How to create them?

  • Include the \version number.
  • Make it small! Examples about spacing or page layout might require many bars of music, but most issues can be reproduced using less than a single measure.
  • When trying to create an example, try commenting out (% or %{ … %}) sections of your file. If you can comment something while still demonstrating the main idea, then remove the commented-material.
  • Avoid using complicated notes, keys or time signatures, unless the bug is about the behavior of those items.
  • Do not use \override or \set commands unless the bug is about those specific commands.
  • Optionally, attach an image showing the desired graphical output.

How tiny should they be?

Is the code below a minimal example?

\version "2.14.1"
\include "english.ly"

\score {
  \new Staff {
    \key d \major
    \numericTimeSignature
    \time 2/4
    <cs' d'' b''>16 <cs' d'' b''>8.
    %% Here: the tie on the D's looks funny
    %% Too tall? Left-hand endpoint is not aligned with the B tie?
    ~
    <cs' d'' b''>8 [ <b d'' a''> ]
  }
}

Well, it is not very big, but a truly minimal example is here:

\version "2.14.1"
{
  % middle tie looks funny here:
  <c' d'' b''>8. ~ <c' d'' b''>8
}

Very few tiny examples exceed 10 lines of code - quite often 4 lines are enough to demonstrate the problem!


Bug reports

If you have input that results in a crash or wrong output, then that is a bug.

Step 1: Known bugs

We may already know about this bug. Check here:

http://code.google.com/p/lilypond/issues/list

Nota bene : Please DO NOT add bug reports directly to the bug tracker. Once an issue has been added to the tracker, feel free to add more information to that report.

Step 2: Creating a bug report

If you have discovered a bug which is not listed, please help us by creating a bug report.

Nota bene : We only accept reports in the form of Tiny examples. We have very limited resources, so any non-minimal example will be rejected. Almost every bug can be demonstrated in four notes or less!

Here is an example of a good bug report:

% Accidentals should be printed for only
% the first note in a tie, but this version
% prints flats on both notes.
\version "2.10.1"

\relative c'' {
 bes1 ~
 bes1
}

Step 3: Sending a bug report

Once you have verified that the issue is not already known and created a bug report, please send it to us!

  • If you are subscribed to the bug-lilypond@gnu.org mailing list, send an email like normal.
  • If you are not subscribed, you can still post a bug report with the gmane lilypond.bugs web interface.

    However, there is a strict “no top-posting” check on the gmane interface, which is often incorrectly triggered by lilypond files. To avoid this, please add:

    > I'm not top posting.
    

    (you must include the > ) to the top of your bug report.

Step 4: Wait for a response

Once your bug report has been sent to the list, our Bug Squad will examine it; they may ask you for more information. You will be notified when the report will be added to the bug tracker. Please allow up to 4 days, as we have a limited number of volunteers for this task.

Once a bug has been added to the tracker, you can comment it to add more information about it. You may also mark the bug so that you automatically receive emails when any activity on the bug occurs. This requires you have a google account.

Optional help: show the desired behavior

Once an issue has been added to the tracker, it can be very helpful if we can see the desired output. Feel free to add input code and/or images (possibly created with other tools) which demonstrate what you think it should look like!


Help us

We need you!

Thank you for your interest in helping us — we would love to see you get involved! Your contribution will help a large group of users make beautifully typeset music.

Even working on small tasks can have a big impact: taking care of them allows experienced developers work on advanced tasks, instead of spending time on those simple tasks.

For a multi-faceted project like LilyPond, sometimes it’s tough to know where to begin. In addition to the avenues proposed below, you can send an e-mail to the lilypond-devel@gnu.org mailing list, and we’ll help you to get started.

Simple tasks

No programming skills required!

  • Mailing list support: answer questions from fellow users.
  • Bug reporting: help users create proper Bug reports, and/or join the Bug Squad to organize Issues.
  • Documentation: small changes can be proposed by following the guidelines for Documentation suggestions.
  • LilyPond Snippet Repository (LSR): create and fix snippets following the guidelines in Adding and editing snippets.
  • Discussions, reviews, and testing: the developers often ask for feedback about new documentation, potential syntax changes, and testing new features. Please contribute to these discussions!

Advanced tasks

These jobs generally require that you have the source code and can compile LilyPond.

Nota bene : We suggest that contributors using Windows or MacOS X do not attempt to set up their own development environment; instead, use Lilydev as discussed in Quick start.

Contributors using Linux or FreeBSD may also use Lilydev, but if they prefer their own development environment, they should read Working with source code, and Compiling.

Begin by reading Summary for experienced developers.


Sponsoring

Bounties

In the past,

  • some users have paid for new features
  • some developers have added new features for hire

The LilyPond project does not organize such efforts; we neither endorse nor discourage such agreements. Any contracts between private individuals is the business of those individuals, not ours.

Guidelines

Any user wanting to offer money in exchange for work should bear in mind the following points:

  • LilyPond developers may advertise their services on the lilypond email lists from time to time.
  • Any agreements between private individuals should include the normal precautions when conducting business: who pays, how much do they pay, with what method of payment, and upon what set of conditions. We suggest that any ambiguity or uncertainty in these questions should be resolved before any work begins.

Interested developers

Here is a list of people who have expressed an interest in bounties. Note that the amount of work done by individuals varies quite a bit throughout the years. We do not guarantee that this list is up-to-date, nor do we guarantee that the people listed here have any ability. The only criteria is "XYZ asked to be listed on this page".

Looking at the git history is a good way to determine who the most active and experienced developers are. Statistics up to version 2.19.5:

overall historypast yearpast three months

Interested developers:

David Kastrup

Donations are required to let me continue my current fulltime work on LilyPond. I focus on user and programmer interface design, coherence, implementation, simplification, documentation, and debugging.


Development

Development for LilyPond 2.19.5

Nota bene : These are unstable development versions. If you have the slightest doubt about how to use or install LilyPond, we urge you to use the stable Download, and read the stable Manuals.

Release numbers

There are two sets of releases for LilyPond: stable releases, and unstable development releases. Stable versions have an even-numbered ‘minor’ version number (e.g., 2.8, 2.10, 2.12). Development versions have an odd-numbered ‘minor’ version number (e.g., 2.7, 2.9, 2.11).

Download

Instructions for git and compiling are in the Contributor’s Guide.

lilypond git repository

Documentation writers and testers will generally want to download the latest binary:

GNU/Linux x86: LilyPond 2.19.5-1

GNU/Linux 64: LilyPond 2.19.5-1

GNU/Linux PPC: LilyPond 2.19.5-1

FreeBSD i386: LilyPond 2.19.5-1

FreeBSD amd64: LilyPond 2.19.5-1

MacOS X x86: LilyPond 2.19.5-1

MacOS X PPC: LilyPond 2.19.5-1

Windows: LilyPond 2.19.5-1

Source: lilypond-2.19.5.tar.gz

Contributor’s Guide

LilyPond development is a fairly complicated matter. In order to help new contributors, and to keep the whole system (mostly) stable, we have written a manual for development tasks.

Regression tests

All versions

Manuals

Nota bene : These manuals are for LilyPond 2.19.5; the latest manuals can be found at http://lilypond.org


GSoC 2012

What is Google Summer of Code?

It is a global program run by Google that offers students stipends for working on open source software projects during summer vacations.

The LilyPond Team decided that this is an excellent opportunity to find new contributors and encourage students already participating in LilyPond development to become more involved. One of our contributors was accepted for 2012 edition of the program as part of the GNU project; we hope to participate in future editions as well.

Our 2012 Ideas List

Below is a list of projects that we suggested for GSoC 2012 students. Although the application period is over, we decided to keep this webpage online as an inspiration for anyone who is interested in developing LilyPond. Some members of the development team are willing to help people who would like to tackle these projects.

Of course, there are many more things to improve in LilyPond, including very small ones. A full list of all known issues can be found here.

Grace notes

Fix problems with synchronization of grace notes, together with all underlying architecture (see issue 34 in our tracker). Grace notes are confusing to LilyPond’s timing because they’re like going back in time. This causes weird effects, especially when one staff has a grace note and the other doesn’t.

Difficulty: medium

Requirements: C++, MIDI

Recommended: familiarity with LilyPond internals

Mentor(s): Mike Solomon, Carl Sorensen

MusicXML

Adding comprehensive MusicXML export and improving import, together with tests checking that it works. Depending on time available, implement some or all of the following:

  • Handle basic musical content export like the MIDI export (i.e. using dedicated exporter classes, derived from the translator class)
  • Build the XML tree of the basic musical content, add a connection from music event to XML tag
  • Let all LilyPond engravers do their job
  • Add ability to link each output object (basically each stencil / group of stencils) to the music cause (and thus to the XML tag in the XML tree)
  • Add a XML output backend, which can then add the layout information for each output object to the XML tags

The goal will be considered achieved when a (previously chosen) score could be imported from MusicXML and exported back with no unintentional loss of data.

Difficulty: medium

Requirements: MusicXML, Python, basic LilyPond knowledge

Mentor(s): Reinhold Kainhofer, Mike Solomon

Familiarity with other scorewriters (for cross-testing) would be a nice bonus.

Improve slurs and ties

The default shape of slur and tie curves is often unsatisfactory. Ties on enharmonic notes { cis'~ des' } are not supported, ties "broken" by clef or staff change aren’t supported well. The project includes collecting and sorting examples of bad output, deciding on the intended output and writing the actual code.

Difficulty: hard

Requirements: C++, experience with writing heuristics

Recommended knowledge: LilyPond knowledge, aesthetic sense

Mentor(s): Mike Solomon

Adding special variant of font glyphs

Adding on-staff-line, between-staff-line, shorter and narrower variants of some glyphs, for example accidentals, together with a generic infrastructure to support them. An example is ancient notation breve notehead coming in two variants, with smaller and bigger hole.

Difficulty: easy

Requirements: MetaFont, C++, good eye for details

Recommended knowledge: basic LilyPond knowledge

Mentor(s): Werner Lemberg

Improve beaming

Default positioning of regular, cross-staff, broken and kneed beams should be improved. Beaming should depend on context and neighbor notes (see section 2.2 here). If possible, reduce beaming computation time.

Difficulty: medium

Requirements: C++, experience with writing heuristics

Recommended knowledge: aesthetic sense

Mentor(s): Mike Solomon, Carl Sorensen

Clean up various compilation warnings

Clean up compiler warnings, static code analysis, and valgrind warnings. Automatic code analysis tools (warnings in g++ and clang) and analysis tools like valgrind memory leak detection and callgrind code profilers provide valuable information about possible flaws in C++ code. Cleaning these warnings would allow us to automatically reject any patch which introduced extra warnings.

Difficulty: medium

Requirements: C++

Mentor(s): Joe Neeman, Reinhold Kainhofer


Authors

Current Development Team

Previous Development Team

Current Contributors

Programming

Aleksandr Andreev, Frédéric Bron, Torsten Hämmerle , Marc Hohl, James Lowe, Andrew Main, Thomas Morley, David Nalesnik, Keith OHara, Benkő Pál, Anders Pilegaard, Julien Rioux, Johannes Rohrer, Devon Schudy, Adam Spiers, Heikki Tauriainen

Font

Documentation

Frédéric Bron, Federico Bruni, Colin Campbell, Urs Liska, James Lowe, Thomas Morley, Jean-Charles Malahieude, Guy Stalnaker, Martin Tarenskeen, Arnold Theresius, Rodolfo Zitellini

Bug squad

Federico Bruni, Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer

Support

Colin Campbell, Eluze, Marc Hohl, Marek Klein, Alex Loomis, Kieren MacMillan, Urs Liska, Ralph Palmer

Translation

Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric, Jean-Charles Malahieude, Till Paala, Yoshiki Sawada

Previous Contributors

Programming

Erlend Aasland, Maximilian Albert, Aleksandr Andreev, Guido Amoruso, Sven Axelsson, Kristof Bastiaensen, Pál Benkő, Frédéric Bron, Juliusz Chroboczek, Peter Chubb, Angelo Contardi, Vicente Solsona Della, Hajo Dezelski, Michael Welsh Duggan, David Feuer, Bertalan Fodor, Richard Gay, Mathieu Giraud, Lisa Opus Goldstein, Yuval Harel, Andrew Hawryluk, Christian Hitz, Karin Hoethker, Marc Hohl, Bernard Hurley, Yoshinobu Ishizaki, Chris Jackson, David Jedlinsky, Heikki Junes, Michael Käppler, Marek Klein, Michael Krause, Jean-Baptiste Lamy, Jonatan Liljedahl, Peter Lutek, Kieren MacMillan, Hendrik Maryns, Thomas Morgan, David Nalesnik, Matthias Neeracher, Keith OHara, Justin Ohmie, Tatsuya Ono, Benkő Pál, Benjamin Peterson, Guy Gascoigne-Piggford, Henning Hraban Ramm, Nathan Reed, Julien Rioux, Stan Sanderson, Andreas Scherer, Johannes Schindelin, Patrick Schmidt, Boris Shingarov, Kim Shrier, Edward Sanford Sutton, Adam Spiers, David Svoboda, Heikki Taurainen, Piers Titus van der Torren, Owen Tuz, Sebastiano Vigna, Jan-Peter Voigt, Arno Waschk, John Williams, Andrew Wilson, Milan Zamazal, Rune Zedeler, Rodolfo Zitellini

Font

Tom Cato Amundsen, Marc Hohl, Chris Jackson, Alexander Kobel, Keith OHara, Carsten Steger, Arno Waschk, Rune Zedeler

Documentation

Erlend Aasland, Trevor Bača, Alard de Boer, Colin Campbell, Jay Hamilton, Joseph Harfouch, Andrew Hawryluk, Cameron Horsburgh, Geoff Horton, Heikki Junes, Kurtis Kroon, James Lowe, Dave Luttinen, Kieren MacMillan, Christian Mondrup, Mike Moral, Eyolf Østrem, Ralph Palmer, François Pinard, David Pounder, Michael Rasmussen, Till Rettig, Pavel Roskin, Patrick Schmidt, Alberto Simoes, Anh Hai Trinh, Eduardo Vieira, Stefan Weil, Rune Zedeler

Support

Colin Campbell, Anthony Fok, Christian Hitz, Phil Holmes, Chris Jackson, Heikki Junes, David Svoboda

Translation

Alard de Boer, Federico Bruni, Abel Cheung, Frédéric Chiasson, Simon Dahlbacka, Orm Finnendahl, David González, Nicolas Grandclaude, Dénes Harmath, Damien Heurtebise, Bjoern Jacke, Matthieu Jacquot, Neil Jerram, Heikki Junes, Nicolas Klutchnikoff, Jean-Charles Malahieude, Adrian Mariano, Christian Mondrup, Tineke de Munnik, Steven Michael Murphy, Till Paala, François Pinard, Gauvain Pocentek, Till Rettig, Ludovic Sardain, Yoshiki Sawada, Thomas Scharkowski, Clytie Siddall, August S. Sigov, Roland Stigge, Risto Vääräniemi, Andrea Valle, Ralf Wildenhues, Olcay Yıldırım


Acknowledgements

Acknowledgements


Publications

What we wrote about LilyPond

  • Server Acim. GNU/LilyPond (Turkish Language). 2013. (PDF 2100k).
  • Graham Percival. Sustainability in F/OSS: developers as a non-renewable resource. In Rencontres Mondiales du Logiciel Libre 2010 (RMLL2010), 2010. (PDF 333k).
  • Han Wen Nienhuys and Jan Nieuwenhuizen. LilyPond, a system for automated music engraving. In Colloquium on Musical Informatics (XIV CIM 2003), May 2003. (PDF 95k).
  • Han Wen Nienhuys. LilyPond, Automated music formatting and the Art of Shipping. In Forum Internacional Software Livre 2006 (FISL7.0), 2006. (PDF 1095k).
  • Margarethe Maierhofer Lischka & Florian Hollerweger. Lilypond: music notation for everyone!. In Linux Audio Conference 2013 (LAC2013), 2013. (PDF 890k).
  • Reinhold Kainhofer. OrchestralLily: A Package for Professional Music Publishing with LilyPond and LATEX. In The Linux Audio Conference 2010 (LAC2010), 2010. (PDF 767k).
  • Erik Sandberg. Separating input language and formatter in GNU LilyPond. Master’s thesis, Uppsala University, Department of Information Technology, March 2006. (PDF 750k).

What people did with LilyPond

  • Kevin C. Baird. Real-time generation of music notation via audience interaction using python and GNU LilyPond. In New Interfaces for Music Expression, May 2005.
  • Alexandre Tachard Passos, Marcos Sampaio, Pedro Kröger, and Givaldo de Cidra. Functional Harmonic Analysis and Computational Musicology in Rameau. In Proceedings of the 12th Brazilian Symposium on Computer Music, pages 207–210, 2009.
  • Graham Percival, Tosten Anders, and George Tzanetakis. Generating Targeted Rhythmic Exercises for Music Students with Constraint Satisfaction Programming. In International Computer Music Conference, 2008.
  • Alberto Simões, Anália Lourenço, and José João Almeida. (J. Neves et al., editor). Using Text Mining Techniques for Classical Music Scores Analysis. In New Trends in Artificial Intelligence, 2007.

If you are aware of any other academic papers which could be listed here, please let us know by following the instructions on Bug reports.


Old news

Nota bene : Many old announcements and changelogs can be found in the Attic

LilyPond 2.19.5 released April 20, 2014

We are happy to announce the release of LilyPond 2.19.5. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

Lilypond 2.18.2 released! March 23, 2014

We are proud to announce the release of GNU LilyPond 2.18.2. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

This version provides a number of updates to 2.18.0, including updated manuals. We recommend all users to upgrade to this version.

LilyPond production named BEST EDITION 2014 March 11, 2014

We are thrilled to announce that the new edition of the songs of Oskar Fried (1871-1941), published recently by our fellow contributors Urs Liska and Janek Warchoł [1], will receive the "Musikeditionspreis BEST EDITION 2014" of the German Music Publishers’ Association [2]! The ceremony will take place in a few days at the Frankfurt Musikmesse [3].

We congratulate Janek and Urs for gaining such public recognition of typographical and editorial excellence of their work. We are also delighted to inform you that they intend to make their work available under a Free license as soon as the publisher expenses are covered. Please support this initiative by buying the printed volume through the publisher [4] or by pledging a contribution at the Indiegogo campaign [5]!

[1] http://lilypondblog.org/category/fried-songs
[2] http://www.best-edition.de
[3] https://musik.messefrankfurt.com/frankfurt/en/besucher/events/awards/best_edition.html
[4] http://www.sound-rel.de
[5] http://igg.me/at/free-fried

Lilypond 2.18.0 released! December 29, 2013

We are proud to announce the release of GNU LilyPond 2.18.0. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

Among the numerous improvements and changes, the following might be most visible:

A full list of noteworthy new features is given in:

http://lilypond.org/doc/v2.18/Documentation/changes/index.html

Great thanks go to the large number of LilyPond enthusiasts whose financial backing enabled one core developer, David Kastrup, to focus exclusively on LilyPond during the entire development cycle.

LilyPond 2.18 has been brought to you by

Main Developers:

Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, Janek Warchoł

Core Contributors:

Aleksandr Andreev, Frédéric Bron, Torsten Hämmerle, Marc Hohl, James Lowe, Andrew Main, Thomas Morley, David Nalesnik, Keith OHara, Benkő Pál, Anders Pilegaard, Julien Rioux, Johannes Rohrer, Adam Spiers, Heikki Tauriainen

Documentation Writers:

Frédéric Bron, Federico Bruni, Colin Campbell, Urs Liska, James Lowe, Thomas Morley, Jean-Charles Malahieude, Guy Stalnaker, Martin Tarenskeen, Arnold Theresius, Rodolfo Zitellini

Bug Squad:

Colin Campbell, Eluze, Marc Hohl, Phil Holmes, Marek Klein, Ralph Palmer

Support Team:

Colin Campbell, Eluze, Marc Hohl, Marek Klein, Kieren MacMillan, Urs Liska, Ralph Palmer

Translators:

Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric, Jean-Charles Malahieude, Till Paala, Yoshiki Sawada

and numerous other contributors.

LilyPond blog. June 2, 2013

Janek Warchoł has created a LilyPond blog. You can find it at lilypondblog.org!

LilyPond 2.16.2 released! January 4, 2013

We are happy to announce the release of LilyPond 2.16.2. This release is mainly to correct a problem with lilypond-book running on Windows. We recommend that only people requiring this functionality upgrade to this version.

The LilyPond Report #28. November 12, 2012

The October issue of the LilyPond Report focuses on the meeting of LilyPond developers and users in Waltrop, Germany last August. Of course, there are also some musings on LilyPond triggered by the release of 2.16.0 and 2.17.0 occuring from that venue.

There are also two monthly financial reports from David Kastrup whose work on LilyPond is solely paid for by financial contributions from other developer and users (thank you!), and a report about experiences from a web-based music typesetting service using LilyPond internally.

Come read LilyPond Report 28 now; comments and contributions are warmly encouraged!

LilyPond 2.16.1 released! November 9, 2012

We are happy to announce the release of LilyPond 2.16.1. This has a number of updates to the previous stable version, and should cause no problems. We recommend that everybody upgrade to this version.

Lilypond 2.16.0 released! August 24, 2012

We are proud to announce the release of GNU LilyPond 2.16.1. LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

Many improvements have been made in the past year since the previous main stable version. A few major improvements are:

A full list of new features is given in:

http://lilypond.org/doc/v2.16/Documentation/changes/index.html

Happy music typesetting! LilyPond 2.16 was brought to you by...

Main development team:

Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, Jan Warchoł

Programming contributors:

Aleksandr Andreev, Sven Axelsson, Peter Chubb, Karin Hoethker, Marc Hohl, David Nalesnik, Justin Ohmie, Benkő Pál, Julien Rioux, Patrick Schmidt, Adam Spiers, Heikki Taurainen, Piers Titus van der Torren, Jan-Peter Voigt, Janek Warchol

Documentation contributors:

James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil

Bug squad:

Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer, James Lowe

Support:

Colin Campbell, Christian Hitz, Phil Holmes

Translation contributors:

Jean-Charles Malahieude, Till Paala, Yoshiki Sawada

LilyPond 2.19.4 released April 6, 2014

We are happy to announce the release of LilyPond 2.19.4. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

LilyPond 2.19.3 released March 2, 2014

We are happy to announce the release of LilyPond 2.19.3. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

LilyPond 2.18.1 February 16, 2014

We have released updated manuals for LilyPond’s stable version, 2.18. The manuals are now for 2.18.1 and have a number of updates and improvements over 2.18.0. There will be a further release of 2.18 in the future (2.18.2), and this will include the updates to the manuals as well as some minor enhancements to the LilyPond core functionality.

To summarise the current situation: stable LilyPond application: 2.18.0; stable LilyPond manuals: 2.18.1; development for both: 2.19.2.

LilyPond 2.19.2 released February 2, 2014

We are happy to announce the release of LilyPond 2.19.2. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

LilyPond 2.19.1 released January 19, 2014

We are happy to announce the release of LilyPond 2.19.1. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

LilyPond 2.19.0 released January 5, 2014

We are happy to announce the release of LilyPond 2.19.0. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.18 version.

LilyPond 2.17.97 released! December 8, 2013

We are excited to announce the release of LilyPond 2.17.97 as a potential final beta release for the upcoming stable release 2.18. The developers believe this to be feature-complete, the documentation to be accurate, and no important issues to be overlooked. For upgrading the syntax of your input files to the latest version, see Updating files with convert-ly. Please test this release and report back any problems, see Bug reports.

LilyPond 2.17.96 released! November 24, 2013

We are excited to announce the release of LilyPond 2.17.96 as a further beta release for the upcoming stable release 2.18. The developers believe the release to be feature-complete, the documentation to be accurate, and no important issues to be overlooked. For upgrading the syntax of your input files to the latest version, see Updating files with convert-ly. Please test this release and report back any problems, see Bug reports.

LilyPond 2.17.95 released! November 3, 2013

We are excited to announce the release of LilyPond 2.17.95 as beta release for the upcoming stable release 2.18. The developers are still busy finding solutions for some last-minute problems, but the release is supposed to be feature-complete, the documentation to be accurate, and no important issues to be overlooked. For upgrading the syntax of your input files to the latest version, see Updating files with convert-ly. Please test this release and report back any problems, see Bug reports.

LilyPond 2.17.29 released! October 20, 2013

We are happy to announce the release of LilyPond 2.17.29. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.28 released! October 6, 2013

We are happy to announce the release of LilyPond 2.17.28. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.27 released! September 26, 2013

We are happy to announce the release of LilyPond 2.17.27. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.26 released! September 8, 2013

We are happy to announce the release of LilyPond 2.17.26. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.25 released! August 25, 2013

We are happy to announce the release of LilyPond 2.17.25. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.24 released! August 11, 2013

We are happy to announce the release of LilyPond 2.17.24. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.23 released! July 28, 2013

We are happy to announce the release of LilyPond 2.17.23. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.22 released! July 14, 2013

We are happy to announce the release of LilyPond 2.17.22. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

This update cures the issue with the Windows version crashing with a problem with positioning text.

LilyPond 2.17.21 released! June 30, 2013

We are happy to announce the release of LilyPond 2.17.21. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.20 released! June 9, 2013

We are happy to announce the release of LilyPond 2.17.20. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.19 released! May 26, 2013

We are happy to announce the release of LilyPond 2.17.19. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.18 released! May 11, 2013

We are happy to announce the release of LilyPond 2.17.18. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.17 released! April 27, 2013

We are happy to announce the release of LilyPond 2.17.17. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.16 released! April 13, 2013

We are happy to announce the release of LilyPond 2.17.16. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.15 released! March 30, 2013

We are happy to announce the release of LilyPond 2.17.15. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.14 released! March 10, 2013

We are happy to announce the release of LilyPond 2.17.14. This release contains the usual number of bugfixes (including putting span bars back where they should be) and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.13 released! February 23, 2013

We are happy to announce the release of LilyPond 2.17.13. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.12 released! February 8, 2013

We are happy to announce the release of LilyPond 2.17.12. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.11 released! January 26, 2013

We are happy to announce the release of LilyPond 2.17.11. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.10 released! January 12 2013

We are happy to announce the release of LilyPond 2.17.10. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.9 released! December 15, 2012

We are happy to announce the release of LilyPond 2.17.9. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.8 released! December 1, 2012

We are happy to announce the release of LilyPond 2.17.8. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.7 released! November 17, 2012

We are happy to announce the release of LilyPond 2.17.7. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.16.1 released! November 9, 2012

We are happy to announce the release of LilyPond 2.16.1. This has a number of updates to the previous stable version, and should cause no problems. We recommend that everybody upgrade to this version.

LilyPond 2.17.6 released! November 3, 2012

We are happy to announce the release of LilyPond 2.17.6. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.5 released! October 20, 2012

We are happy to announce the release of LilyPond 2.17.5. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of Lilypond, we recommend using the 2.16 version.

LilyPond 2.17.4 released! October 6, 2012

We are happy to announce the release of LilyPond 2.17.4. This release contains the usual number of bugfixes. It is strongly recommended that normal users do not use this release, and instead use the stable 2.16 version.

LilyPond 2.17.3 released! September 23, 2012

We are happy to announce the release of LilyPond 2.17.3. This release contains the usual number of bugfixes. It is strongly recommended that normal users do not use this release, and instead use the stable 2.16 version.

LilyPond 2.17.2 released! September 10, 2012

We are happy to announce the release of LilyPond 2.17.2. This release contains the usual number of bugfixes. It is strongly recommended that normal users do not use this release, and instead use the stable 2.16 version.

LilyPond 2.17.1 released! August 28, 2012

We are happy to announce the release of LilyPond 2.17.1. This release contains the usual number of bugfixes. It is strongly recommended that normal users do not use this release, and instead use the stable 2.16 version.

LilyPond 2.17.0 released! August 26, 2012

We are happy to announce the release of LilyPond 2.17.0. This release contains the usual number of bugfixes. It is strongly recommended that normal users do not use this release, and instead use the stable 2.16 version.

Lilypond 2.16.0 released! August 24, 2012

We are proud to announce the release of GNU LilyPond 2.16.0. LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

Many improvements have been made in the past year since the previous main stable version. A few major improvements are:

A full list of new features is given in:

http://lilypond.org/doc/v2.16/Documentation/changes/index.html

Happy music typesetting! LilyPond 2.16 was brought to you by...

Main development team:

Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, Jan Warchoł

Programming contributors:

Aleksandr Andreev, Sven Axelsson, Peter Chubb, Karin Hoethker, Marc Hohl, David Nalesnik, Justin Ohmie, Benkő Pál, Julien Rioux, Patrick Schmidt, Adam Spiers, Heikki Taurainen, Piers Titus van der Torren, Jan-Peter Voigt, Janek Warchol

Documentation contributors:

James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil

Bug squad:

Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer, James Lowe

Support:

Colin Campbell, Christian Hitz, Phil Holmes

Translation contributors:

Jean-Charles Malahieude, Till Paala, Yoshiki Sawada

Lilypond 2.15.95 released! August 11, 2012

We are excited to announce the release of LilyPond 2.15.95. With this release, development on version 2.15 is frozen for the upcoming 2.16 stable release and only open to bug fixes.

All users are urged to try this version to ensure the best quality of the upcoming stable release. If you discover any problems, please send us Bug reports.

New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

LilyPond 2.15.42 released! August 02, 2012

We are happy to announce the release of LilyPond 2.15.42. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

The LilyPond Report #27. August 2, 2012

The LilyPond Report is back, with some interesting insights on new Scheme-related features recently added by our community’s only paid developer David Kastrup (thanks to your continuing donations). Also to be found in this issue are an overview of some lesser-known LilyPond companion projects, and a handful of more shallow factoids.

Come read LilyPond Report 27 now; comments and contributions are warmly encouraged!

Release candidate withdrawn July 11, 2012

We have discovered a regression since 2.14.2, so lilypond 2.15.41 is no longer a candidate for the 2.16.0 release. However, please continue testing it – we would like to discover (and fix!) any more regressions as soon as possible. If you discover any problems, please send us Bug reports.

Release candidate 8 of 2.16 - LilyPond 2.15.41 released! July 4, 2012

LilyPond 2.15.41 is out; this is the eighth release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 18 July 2012. If you discover any problems, please send us Bug reports.

LilyPond 2.15.40 released! June 05, 2012

We are happy to announce the release of LilyPond 2.15.40. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

Release candidate withdrawn June 01, 2012

We have discovered a regression since 2.14.2, so lilypond 2.15.39 is no longer a candidate for the 2.16.0 release. However, please continue testing it – we would like to discover (and fix!) any more regressions as soon as possible. If you discover any problems, please send us Bug reports.

Release candidate 7 of 2.16 - LilyPond 2.15.39 released! May 22, 2012

LilyPond 2.15.39 is out; this is the seventh release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 05 June 2012. If you discover any problems, please send us Bug reports.

The LilyPond Report #26. May 22, 2012

The LilyPond Report is back, with a new editor on board - Pavel Roskin, who tells us about his adventures in strange lands of compiler bugs! There is also a detailed report about current development status, and an analysis of example LilyPond output - see for yourself how close (or how far?) are we from matching the quality of hand-engraved scores.

Come read LilyPond Report 26 now; comments and contributions are warmly encouraged!

Release candidate 6 of 2.16 - LilyPond 2.15.38 released! May 3, 2012

LilyPond 2.15.38 is out; this is the sixth release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

Update: Due to a few Critical bugs, another release candidate will be required.

LilyPond takes part in Google Summer of Code 2012! April 25, 2012

Being a part of GNU project, we are participating in Google Summer of Code program, which offers students stipends for working on open source software.

Our contributor Janek Warchoł was accepted for 2012 edition of GSoC. He will be working on advanced lyrics positioning in LilyPond.

Release candidate 5 of 2.16 - LilyPond 2.15.37 released! April 19, 2012

LilyPond 2.15.37 is out; this is the fifth release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 03 May 2012. If you discover any problems, please send us Bug reports.

Release candidate 4 of 2.16 - LilyPond 2.15.36 released! April 6, 2012

LilyPond 2.15.36 is out; this is the fourth release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 20 April 2012. If you discover any problems, please send us Bug reports.

The LilyPond Report #25. Apr 1st, 2012

The LilyPond Report is back, with a rather unusual issue featuring our young Polish contributor Janek Warchoł! Also included in this issue are quite a few unexpected items, including (but not limited to)… a cooking recipe!

Come read LilyPond Report 25 now; comments and contributions are warmly encouraged!

LilyPond 2.15.35 released! Mar 28, 2012

We are happy to announce the release of LilyPond 2.15.35. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.34 released! Mar 19, 2012

We are happy to announce the release of LilyPond 2.15.34. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.33 released! Mar 08, 2012

We are happy to announce the release of LilyPond 2.15.33. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

The LilyPond Report #24. Mar 5, 2012

A new issue of the LilyPond Report is now available for reading; topics include a request for funding, an article about exciting new features in LilyPond grammar, and an overview of LilyPond-based web applications.

Come read LilyPond Report 24 now; comments and contributions are warmly encouraged!

LilyPond 2.15.32 released! Mar 03, 2012

We are happy to announce the release of LilyPond 2.15.32. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.31 released! Feb 29, 2012

We are happy to announce the release of LilyPond 2.15.31. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

Release candidate 3 of 2.16 - LilyPond 2.15.30 released! Feb 17, 2012

LilyPond 2.15.30 is out; this is the third release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 02 March 2012. If you discover any problems, please send us Bug reports.

LilyPond 2.15.29 released! Feb 9, 2012

We are happy to announce the release of LilyPond 2.15.29. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.28 released! Feb 3, 2012

We are happy to announce the release of LilyPond 2.15.28. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.27 released! Jan 24, 2012

We are happy to announce the release of LilyPond 2.15.27. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

The LilyPond Report #23. Jan 20, 2012

The LilyPond Report is back, with developer David Kastrup as a new editor! This issue features an exposé on some of the new, handy commands recently added to LilyPond, as well as an interview with LilyPond contributor and composer Mike Solomon.

Come read LilyPond Report 23 now; comments and contributions are warmly encouraged!

LilyPond 2.15.26 released! Jan 16, 2012

We are happy to announce the release of LilyPond 2.15.26. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

The 2.15.25 has been skipped due to build problems.

LilyPond 2.15.24 released! Jan 07, 2012

We are happy to announce the release of LilyPond 2.15.24. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.23 released! Dec 21, 2011

We are happy to announce the release of LilyPond 2.15.23. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.22 released! Dec 15, 2011

We are happy to announce the release of LilyPond 2.15.22. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.21 released! Dec 6, 2011

We are happy to announce the release of LilyPond 2.15.21. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.20 released! Nov 24, 2011

We are happy to announce the release of LilyPond 2.15.20. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.19 released! Nov 18, 2011

We are happy to announce the release of LilyPond 2.15.19. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.18 released! Nov 12, 2011

We are happy to announce the release of LilyPond 2.15.18. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.17 released! Nov 10, 2011

We are happy to announce the release of LilyPond 2.15.17. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.16 released! October 28, 2011

We are happy to announce the release of LilyPond 2.15.16. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.15 released! October 24, 2011

We are happy to announce the release of LilyPond 2.15.15. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.14 released! October 7, 2011

We are happy to announce the release of LilyPond 2.15.14. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.13 released! September 27, 2011

We are happy to announce the release of LilyPond 2.15.13. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate.

Release candidate 2 cancelled Sep 23, 2011

The release countdown is cancelled due to the discovery of a Critical regression.

Release candidate 2 of 2.16 - LilyPond 2.15.12 released! Sep 20, 2011

LilyPond 2.15.12 is out; this is the second release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 27 Sep 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.15.11 released! September 11, 2011

We are happy to announce the release of LilyPond 2.15.11. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to the possibility of a few Critical bugs, this is not the next release candidate.

LilyPond 2.15.10 released! September 6, 2011

We are happy to announce the release of LilyPond 2.15.10. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few outstanding Critical bugs, this is not the next release candidate.

LilyPond 2.15.9 released! August 30, 2011

We are happy to announce the release of LilyPond 2.15.9. This release contains the usual number of bugfixes, and also adds support for MacOS X 10.7.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few outstanding Critical bugs, this is not the next release candidate.

Release candidate 1 of 2.16 - LilyPond 2.15.8 released! Aug 01, 2011

LilyPond 2.15.8 is out; this is the first release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 08 Aug 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.15.7 released! July 29, 2011

We are happy to announce the release of LilyPond 2.15.7. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.15.6 released! July 26, 2011

We are happy to announce the release of LilyPond 2.15.6. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.14.2 released! July 25, 2011

We are happy to announce the release of LilyPond 2.14.2. This fixes a few minor bugs in the stable version, and should cause no problems. We recommend that everybody upgrade to this version.

LilyPond 2.15.5 released! July 12, 2011

We are happy to announce the release of LilyPond 2.15.5. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.15.4 released! July 4, 2011

We are happy to announce the release of LilyPond 2.15.4. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.15.3 released! June 27, 2011

We are happy to announce the release of LilyPond 2.15.3. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.15.2 released! June 18, 2011

We are happy to announce the release of LilyPond 2.15.2. This release contains the usual number of bugfixes.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.14.1 released! June 12, 2011

We are happy to announce the release of LilyPond 2.14.1. This fixes a few minor bugs in the stable version, and should cause no problems. We recommend that everybody upgrade to this version.

LilyPond 2.15.1 released! June 11, 2011

We are happy to announce the release of LilyPond 2.15.1. This is the beginning of a new unstable development effort, and adds the usual number of bugs.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.15.0 released! June 7, 2011

We are happy to announce the release of LilyPond 2.15.0. This is the beginning of a new unstable development effort, and adds the usual number of bugs.

It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version.

LilyPond 2.14.0 released! June 6, 2011

We are proud to announce the release of GNU LilyPond 2.14. LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.

Many improvements have been made in the past two and a half years since the previous main stable version. A few major improvements are:

A full list of new features is given in:

http://lilypond.org/doc/v2.14/Documentation/changes/index.html

Happy music typesetting! LilyPond 2.14 was brought to you by...

Main development team:

Trevor Daniels, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave.

Programming contributors:

Sven Axelsson, Pál Benkő, Bertrand Bordage, Frédéric Bron, Peter Chubb, Hajo Dezelski, Richard Gay, Keith OHara, Andrew Hawryluk, Christian Hitz, Marc Hohl, Henning Hraban Ramm, Ian Hulin, Michael Käppler, Marek Klein, Kieren MacMillan, Thomas Morgan, Benjamin Peterson, Nathan Reed, Julien Rioux, Boris Shingarov, Patrick Schmidt, Owen Tuz, Jan Warchoł, Andrew Wilson, Rodolfo Zitellini.

Font contributors:

Keith OHara, Marc Hohl, Alexander Kobel, Carsten Steger.

Documentation contributors:

Colin Campbell, Andrew Hawryluk, James Lowe, Mike Moral, Ralph Palmer, David Pounder, Patrick Schmidt.

Bug squad:

James E. Bailey, Colin Campbell, Phil Holmes, Urs Liska, Ralph Palmer, Kieren MacMillan, Dmytro O. Redchuk.

Binaries support contributors:

Christian Hitz.

Translation contributors:

Federico Bruni, Dénes Harmath, Jean-Charles Malahieude, Tineke de Munnik, Till Paala, Ralf Wildenhues, Yoshiki Sawada.

Release candidate 7 of 2.14 - LilyPond 2.13.63 released! May 30, 2011

LilyPond 2.13.63 is out; this is the seventh release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on June 6, 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.13.62 released! May 24, 2011

We are happy to announce the release of LilyPond 2.13.62. This release contains the usual number of bugfixes.

Please note that this is not the next release candidate, due to a few remaining Critical bugs.

LilyPond 2.13.61 released! May 1, 2011

We are happy to announce the release of LilyPond 2.13.61. This release contains the usual number of bugfixes.

Please note that this is not the next release candidate, due to a few remaining Critical bugs.

LilyPond 2.13.60 released! April 16, 2011

We are happy to announce the release of LilyPond 2.13.60. This release contains the usual number of bugfixes.

Please note that this is not the next release candidate, due to a few remaining Critical bugs.

Linux Journal Magazine article - April 2011

Linux Magazine publishes an article in the May 2011 issue titled Projects on the Move. It is an introduction to MuseScore, LilyPond and Chordii. Author Carla Schroder states “LilyPond is driven from the command line, but don’t let the lack of a GUI scare you away; LilyPond is user-friendly and easy to learn”, and provides a hands-on example.

LilyPond 2.13.59 released! April 10, 2011

We are happy to announce the release of LilyPond 2.13.59. This release contains the usual number of bugfixes.

Please note that this is not the next release candidate, due to a few remaining Critical bugs.

Release candidate 6 of 2.14 - LilyPond 2.13.58 released! April 7, 2011

LilyPond 2.13.58 is out; this is the sixth release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on April 14, 2011. If you discover any problems, please send us Bug reports.

Release candidate 5 of 2.14 - LilyPond 2.13.57 released! April 3, 2011

LilyPond 2.13.57 is out; this is the fifth release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on April 10, 2011. If you discover any problems, please send us Bug reports.

Release candidate 4 of 2.14 - LilyPond 2.13.56 released! Mar 29, 2011

LilyPond 2.13.56 is out; this is the fourth release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on April 5, 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.13.55 released! Mar 22, 2011

We are happy to announce the release of LilyPond 2.13.55. This release contains the usual number of bugfixes.

Please note that this is not the fourth release candidate, due to a few remaining Critical bugs.

Release candidate 3 withdrawn Mar 15, 2011

We have discovered a regression since 2.12.3, so lilypond 2.13.54 is no longer a candidate for the 2.14.0 release. However, please continue testing it – we would like to discover (and fix!) any more regressions as soon as possible. If you discover any problems, please send us Bug reports.

Release candidate 3 of 2.14 - LilyPond 2.13.54 released! Mar 13, 2011

LilyPond 2.13.54 is out; this is the third release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on March 27, 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.13.53 released! Mar 6, 2011

We are happy to announce the release of LilyPond 2.13.53. This release contains the usual number of bugfixes.

Please note that this is not the third release candidate, due to a few remaining Critical bugs.

LilyPond 2.13.52 released! Mar 1, 2011

We are happy to announce the release of LilyPond 2.13.52. This release contains the usual number of bugfixes.

Please note that this is not the third release candidate, due to a few remaining Critical bugs.

LilyPond 2.13.51 released! Feb 22, 2011

We are happy to announce the release of LilyPond 2.13.51. This release contains the usual number of bugfixes.

Please note that this is not the third release candidate, due to a few remaining Critical bugs.

LilyPond 2.13.50 released! Feb 13, 2011

We are happy to announce the release of LilyPond 2.13.50. This release contains the usual number of bugfixes.

Please note that this is not the third release candidate. Due to a number of untested changes to our build process, we cannot be at all confident about the quality of this release.

New Chinese and Czech translations of the web page! Feb 11,2011

Two new languages are added to our web page: Chinese by Ben Luo, and Czech by Pavel Fric. It is a work in progress but they are fully functional. That makes ten languages to choose from!

Release candidate 2 of 2.14 - LilyPond 2.13.49 released! Feb 9, 2011

LilyPond 2.13.49 is out; this is the second release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on Feb 23, 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.13.48 released! Feb 5, 2011

We are happy to announce the release of LilyPond 2.13.48. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.47 released! Jan 28, 2011

We are happy to announce the release of LilyPond 2.13.47. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Release candidate 1 withdrawn Jan 13, 2011

We have discovered a regression since 2.12.3, so lilypond 2.13.46 is no longer a candidate for the 2.14.0 release. However, please continue testing it – we would like to discover (and fix!) any more regressions as soon as possible. If you discover any problems, please send us Bug reports.

Release candidate 1 of 2.14 - LilyPond 2.13.46 released! Jan 12, 2011

LilyPond 2.13.46 is out; this is the first release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on 26 Jan 2011. If you discover any problems, please send us Bug reports.

LilyPond 2.13.45 released! Jan 3, 2011

We are happy to announce the release of LilyPond 2.13.45. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Beta test three of 2.14 – LilyPond 2.13.44 released! Dec 25, 2010

LilyPond 2.13.44 is out; this is the third beta test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There is still one Critical problem with this release: in one case, the vertical spacing is much too compressed. If you decide to test this version, do not be surprised to discover problems; just send us polite Bug reports.

Beta test two of 2.14 – LilyPond 2.13.43 released! Dec 14, 2010

LilyPond 2.13.43 is out; this is the second beta test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There is still one Critical problem with this release: in one case, the vertical spacing is much too compressed. If you decide to test this version, do not be surprised to discover problems; just send us polite Bug reports.

LilyPond 2.13.42 released! Dec 8, 2010

We are happy to announce the release of LilyPond 2.13.42. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Please note that this is not the second beta test. Due to a number of untested changes to our build process, we cannot be at all confident about the quality of this release.

LilyPond 2.13.41 released! Dec 4, 2010

We are happy to announce the release of LilyPond 2.13.41. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Please note that this is not the second beta test. Due to a number of untested changes to our build process, we cannot be at all confident about the quality of this release.

LilyPond 2.13.40 released! Nov 21, 2010

We are happy to announce the release of LilyPond 2.13.40. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Please note that this is not the second beta test. Due to a number of untested changes to our build process, we cannot be at all confident about the quality of this release.

Beta test one of 2.14 – LilyPond 2.13.39 released! Nov 15, 2010

LilyPond 2.13.39 is out; this is the first beta test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are still some Critical problems with this release: the vertical spacing is suspicious in two cases, and lilypond can crash with some odd input. If you decide to test 2.13.39, do not be surprised to discover problems; just send us polite Bug reports.

The LilyPond Report #22. Nov 3, 2010

The LilyPond Report is back, with some surprises and exciting news for the whole LilyPond community! To be found in this issue is an up-to-date, complete list of all LilyPond mailing lists and forums around the world. Also, for the very first time our special guest today is LilyPond’s co-founder and core developer Jan Nieuwenhuizen, who has been busy these past months – read on to find out what for!

Come read LilyPond Report 22 now; comments and contributions are warmly encouraged!

Alpha test four of 2.14 – LilyPond 2.13.38 released! Oct 31, 2010

LilyPond 2.13.38 is out; this is the fourth alpha test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are still some Critical problems with this release: the vertical spacing is suspicious in two cases, and lilypond can crash with some odd input. If you decide to test 2.13.38, do not be surprised to discover problems; just send us polite Bug reports.

Alpha test three of 2.14 – LilyPond 2.13.37 released! Oct 25, 2010

LilyPond 2.13.37 is out; this is the third alpha test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

There are still some Critical problems with this release: the vertical spacing is suspicious in two cases, and lilypond can crash with some odd input. If you decide to test 2.13.37, do not be surprised to discover problems; just send us polite Bug reports.

LilyPond 2.13.36 released! Oct 19, 2010

We are happy to announce the release of LilyPond 2.13.36. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Please note that this is not the third alpha test. Due to a number of untested changes to our build process, we cannot be at all confident about the quality of this release.

The LilyPond Report #21. Oct 3, 2010

The LilyPond Report is back, with its two “grumpy-and-fluffy” editors! This issue mainly deals with microtonal notation in LilyPond, but does also include a how-to about running LilyPond from an USB key, not to forget the regular release news, the bug report of the Report, and some news from the frog pond!

Come read LilyPond Report 21 now; comments and contributions are warmly encouraged!

Alpha test two of 2.14 – LilyPond 2.13.35 released! Sep 29, 2010

LilyPond 2.13.35 is out; this is the second alpha test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

Three known regressions against 2.12.3 still exist: Issue 1173 MetronomeMarks cannot be aligned on a note if a multi-measure rest exists in another voice, and two spacing bugs: Issue 1240 and Issue 1252. If you decide to test 2.13.35, do not be surprised to discover problems; just send us polite Bug reports.

Alpha test of 2.14 – LilyPond 2.13.34 released! Sep 21, 2010

LilyPond 2.13.34 is out; this is the first alpha test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about Development.

One known regression against 2.12.3 still exist: Issue 1173 MetronomeMarks cannot be aligned on a note if a multi-measure rest exists in another voice, but we expect to find more. If you decide to test 2.13.34, do not be surprised to discover problems; just send us polite Bug reports.

LilyPond 2.13.33 released! Sep 10, 2010

We are happy to announce the release of LilyPond 2.13.33. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.32 released! Sep 3, 2010

We are happy to announce the release of LilyPond 2.13.32. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond Report #20. Sep 2, 2010

The LilyPond Report is back, with its two “grumpy-and-fluffy” editors! This issue contains a review of an online notation editor using lilypond, along with the regular release news, snippet of the report, news from the frog pond, and the bug report of the report!

Come read LilyPond Report 20 now; comments and contributions are warmly encouraged!

LilyPond 2.13.31 released! Aug 24, 2010

We are happy to announce the release of LilyPond 2.13.31. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.30 released! Aug 13, 2010

We are happy to announce the release of LilyPond 2.13.30. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond Report #19. Aug 9, 2010

The LilyPond Report is back, with its two “grumpy-and-fluffy” editors! This issue contains some conference news, along with the regular release news, snippet of the report, news from the frog pond, and the bug report of the report!

Come read LilyPond Report 19 now; comments and contributions are warmly encouraged!

LilyPond 2.13.29 released! Aug 4, 2010

We are happy to announce the release of LilyPond 2.13.29. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

This release radically changes the autobeaming rules, so use extra caution and expect breakage.

LilyPond 2.13.28 released! July 13, 2010

We are happy to announce the release of LilyPond 2.13.28. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

This release includes some major untested changes to the windows lilypad editor. Windows users should not be using this release because it is intended for developers only, but you ignore these warnings and try it anyway, use extra caution.

LilyPond 2.13.27 released! July 5, 2010

We are happy to announce the release of LilyPond 2.13.27. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Testing our new website! June 29, 2010

We’re testing our new website! For the next 24 hours, the new website will be the default website; after that, we will switch back to the old website while we examine feedback and make improvements to the new website.

Please send feedback to lilypond-user; you can find more information on our page about Contact.

Nota bene : There are a few known problems with translations. If you are a non-English speaker, you may prefer to view the old lilypond website at: http://lilypond.org/web/

LilyPond 2.13.26 released! June 26, 2010

We are happy to announce the release of LilyPond 2.13.26. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.25 released! June 20, 2010

We are happy to announce the release of LilyPond 2.13.25. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.24 released! June 14, 2010

We are happy to announce the release of LilyPond 2.13.24. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.23 released! June 3, 2010

We are happy to announce the release of LilyPond 2.13.23. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.22 released! May 27, 2010

We are happy to announce the release of LilyPond 2.13.22. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.21 released! May 12, 2010

We are happy to announce the release of LilyPond 2.13.21. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

This release should be of particular interest to package maintainers: we have made a few changes to the configure script and the required libraries. Barring any urgent bug reports, this is the build system and libraries that will be used for the next stable release.

LilyPond Report #18. May 11, 2010

The LilyPond Report is back, with its two “grumpy-and-fluffy” editors! This issue will be filled with emotion and coolness, paper bags and zigzag-ending staves, plus the usual Frogs and Bugs.

Come read LilyPond Report 18 now; comments and contributions are warmly encouraged!

LilyPond 2.13.20 released! May 5, 2010

We are happy to announce the release of LilyPond 2.13.20. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only.

Minor syntax change: the undocumented \cresc and \decresc have changed. In addition, the [options] for the LaTeX mode of lilypond-book now comes after the {lilypond}, following normal LaTeX practice. As always, see the Changes document for more information.

LilyPond 2.13.19 released! April 24, 2010

We are happy to announce the release of LilyPond 2.13.19. This release contains the usual number of bugfixes. However, 11 critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.18 released! April 16, 2010

We are happy to announce the release of LilyPond 2.13.18. This release contains the usual number of bugfixes, along with improved website translations. However, 14 critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.17 released! April 2, 2010

We are happy to announce the release of LilyPond 2.13.17. This release includes bugfixes for 4 critical issues. However, 15 critical issues still remain, so this release is intended for developers only.

LilyPond 2.13.16 released! March 15, 2010

We are happy to announce the release of LilyPond 2.13.16. This release is intended for developers only, and includes the usual round of bugfixes.

LilyPond 2.13.15 released! March 4, 2010

We are happy to announce the release of LilyPond 2.13.15. This release is intended for developers only, and includes a few updates to the binary build process in addition to the usual round of bugfixes.

LilyPond Report #17. March 1, 2010

Yay, the Report is back, with a new team! It has been said that two heads are better than one — does it apply to newsletters as well? Read on and let us know! In this issue we’ll talk about websites and poetry, frogs and bugs, not to mention an extensive review of the Frescobaldi editor!

What are you waiting for? Come read LilyPond Report 17 now!

LilyPond 2.13.14 released! February 27, 2010

We are happy to announce the release of LilyPond 2.13.14. This release is intended for developers only, and includes a large translation update in addition to the usual round of bugfixes.

LilyPond 2.13.13 released! February 13, 2010

We are happy to announce the release of LilyPond 2.13.13. This release is intended for developers only, and fixes various problems with documentation build system as well as adding an output-preview-framework for our SVG backend. In addition, the binaries are now approximately 6 megabytes smaller.

LilyPond 2.13.12 released! February 2, 2010

We are happy to announce the release of LilyPond 2.13.12. This release is intended for developers only, and brings more stability and fewer bugs to the build system and Contributor’s Guide.

LilyPond 2.13.11 released! January 16, 2010

We are happy to announce the release of LilyPond 2.13.11. This release is intended for developers only, and brings a number of improvements to the build system, Contributor’s Guide, and fixes 4 critical regressions against earlier versions.

LilyPond 2.13.10 released! December 31, 2009

We are happy to announce the release of LilyPond 2.13.10. This release is intended for developers only, and brings a number of improvements such as predictable regression test output filenames and English names for feta filenames.

LilyPond 2.12.3 released! December 20, 2009

We are happy to announce the release of LilyPond 2.12.3. This version contains the long-awaited fix for our GUI on MacOS X 10.5 and 10.6. In addition to the GUI fixes, this version contains dozens of bugfixes backported from the unstable development version.

We recommend that all users upgrade to this version. This is the last planned release in the 2.12 stable series; development now shifts towards the upcoming 2.14 series.

LilyPond 2.13.9 released! December 12, 2009

LilyPond 2.13.9 is now out. From 2.13.9 onwards, LilyPond is licensed under the GNU GPL v3+ for code, and the GNU FDL 1.3+ for documentation. In addition to the usual round of bugfixes, this release adds a shortcut for repeated chords.

Please note that 2.13 is an unstable development branch; normal users should continue to use 2.12.

New Website! October 3, 2009

As you can see, we have a new website design. Many thanks to texi2html and CSS for being so flexible!

LilyPond Report #16. September 6, 2009

The LilyPond Report is back! This short, informal opinion column is about the LilyPond project: its team, its world, its community. Read issue 16 now!

LilyPond 2.13.3. July 2, 2009

This unstable release contains working menus in OSX 10.5; many thanks to Christian Hitz for fixing this long-standing problem! This release also contains numerous other bugfixes and features such as ties with variable thickness, partially dashed slurs, and eyeglasses.
We are planning another 2.12 release in the next week or two, which will include the menu fixes for OSX 10.5. Normal users may wish to wait for this release rather than using an unstable release.
Veranderingen, Development.

A LilyPond weboldala magyarul. May 22, 2009

Elkészült a lilypond.org nagy részének magyar fordítása a LilyPond honosítási projekt első lépéseként. A projekt célja a LilyPond szabad kottaszedő szoftver minél széleskörűbben elérhetővé tétele a magyar felhasználók számára a teljes weboldal és dokumentáció lefordítása révén. A teljes dokumentáció lefordításához közreműködőket keresünk. Ha részt vennél a honosításban, küldj egy e-mailt a harmathdenes AT gmail.com címre!
Harmath Dénes, a LilyPond honosítási projekt vezetője

The LilyPond Report #15. May 18, 2009

The LilyPond Report is a short, informal opinion column about the LilyPond project: its team, its world, its community. Follow this link to read the full issue...

The LilyPond Report #14. April 13, 2009

The LilyPond Report is back, on a new website! This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community. Follow this link to read the full issue...

LilyPond 2.12.2 and 2.13.0 — March 21, 2009

As a very belated announcement, the stable version of LilyPond is now 2.12.2, and the next development version has begun with 2.13.0.

LilyPond 2.12.0 “Rune” — December 27, 2008

A new stable release of LilyPond is available.
Announcement, Veranderingen, Download.

LilyPond 2.11.65 — Release Candidate. December 2, 2008

This release has improvements to MusicXML import, contributed by Reinhold Kainhofer, and adds support for splitting a book in several book parts, contributed by Nicolas Sceaux. Nested contexts of the same type are now allowed with any depth, and overriding nested properties can be done with list syntax, thanks to Neil Puttock. This is hopefully the last Release Candidate before stable release 2.12, so you are welcome to test this release if you can to report new issues.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.64. November 18, 2008

LilyPond 2.11.64 is available. MusicXML import has been improved, including church modes support, and a few bugs in the compilation and documentation building processes are fixed. The three documentation manuals are now fully translated in Spanish, thanks to Francisco Vila. The font cache problem in Windows binaries which used to cause excessive slowness should be fixed.
Veranderingen, Oude downloads.

LilyPond 2.11.63. October 29, 2008

LilyPond 2.11.63 is available. This release has lots of updates to the documentation and translations. Oude downloads.

LilyPond 2.11.62 – Release Candidate. October 11, 2008

LilyPond 2.11.62 is available. This is is one of the last releases before 2.12, so testing it is encouraged. In addition to a bugfix in \tempo command, this release has lot of updates to Spanish and German documentation translations, and the stylesheet for HTML documentation has been improved.
Bugfixes, Oude downloads.

LilyPond 2.11.61 available. October 1, 2008

LilyPond 2.11.61 has been released. It has updates to documentation translations, and a new automatic accidentals style (teaching) has been added.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.60 available. September 25, 2008

LilyPond 2.11.60 has been released. A new style of double repeat bar line has been added, and printallheaders variable in score block has been renamed to print-all-headers. Oude downloads.

LilyPond 2.11.59 available. September 20, 2008

Release 2.11.59 is out. LilyPond now uses 64 bit integers for rational numbers, which allows typesetting more complex polymetric music. This release also has updates to German and Spanish translations of the documentation. Oude downloads.

LilyPond 2.11.58 available. September 13, 2008

LilyPond 2.11.58 is a beta release, which means the next stable release is expected in a few weeks. This release is also special, as it includes code which supports more flexible automatic accidentals rules, written several months ago by Rune Zedeler, deceased since then. All the development team express their condolences to his family and his friends. Besides this, automatic beaming has been improved by Carl Sorensen, support for creating stem flags in a new style has been contributed by Reinhold Kainhofer, and a few bugs have been fixed.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.57 available. August 27, 2008

LilyPond 2.11.57 is out. This release adds support for harp pedal diagrams, contributed by Reinhold Kainhofer, and some changes in markup command names have been made.
Veranderingen, Oude downloads.

LilyPond 2.11.56 available. August 17, 2008

LilyPond 2.11.56 is out. This release features transposable fret diagrams, contributed by Carl Sorensen. Translations status pages are now available from the documentation start page. Two predefined commands \pointAndClickOn, \pointAndClickOff have also been added.
Veranderingen, Oude downloads.

LilyPond 2.11.55 available. August 6, 2008

LilyPond 2.11.55 is out. This release fixes several bugs, and for octavation brackets set-octavation has been replaced by a more user-friendly command, \ottava.
Bugfixes, Oude downloads.

LilyPond 2.11.54 available. July 30, 2008

LilyPond 2.11.54 is out. This release fixes a bug in tie formatting following a line break, and changes the behavior of short-indent so that short instrument names are no longer indented in the margin.
Bugfixes, Oude downloads.

LilyPond 2.11.53 available. July 23, 2008

LilyPond 2.11.53 is out. This release fixes a lot of bugs.
Bugfixes, Oude downloads.

LilyPond 2.11.52 available. July 14, 2008

Release 2.11.52 fixes wrong offset of a bar number when it follows a breath mark, and syntax changes made in recent development releases are now fully listed on the News page.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.51 available. July 8, 2008

Release 2.11.51 has a couple of bugfixes, and a lot of changes in predefined command names. Fret diagrams formatting has been improved by Carl Sorensen, it is now controlled by fret-diagram-details property.
Bugfixes, Oude downloads.

LilyPond 2.11.50 available. July 2, 2008

Release 2.11.50 adds support for metronome marks with text, and backslashed numbers for figured bass, contributed by Reinhold Kainhofer.
Bugfixes, Oude downloads.

The LilyPond Report #13. June 23, 2008

This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community. Follow this link to read the full issue...

The LilyPond Report #12. June 16, 2008

This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community. Follow this link to read the full issue...

LilyPond 2.11.49 released. June 12, 2008

LilyPond 2.11.49 is out. It fixes a number of bugs, including bugs in beams formatting.
Bugfixes, Oude downloads.

LilyPond 2.11.48 released. June 9, 2008

LilyPond 2.11.48 is out. This release fixes a few bugs, and \compressMusic has been renamed to \scaleDurations.
Bugfixes, Oude downloads.

The LilyPond Report #11. June 9, 2008

This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community. Follow this link to read the full issue...

The LilyPond Report #10. June 2, 2008

Welcome to this special tenth issue of the LilyPond Report, entirely dedicated to Algorithmic Composition systems.
Follow this link to read the full issue...

LilyPond 2.11.47 released. May 28, 2008

LilyPond now allows all text context properties to be markups, except in \lyricmode. This release also fixes regression tests maintenance for developers.
Bugfixes, Oude downloads.

LilyPond 2.11.46 available. May 22, 2008

Release 2.11.46 fixes a lot of bugs and includes a rewrite of dynamics engravers. Support for slur-shaped arpeggios has been added.
Bugfixes, Veranderingen, Oude downloads.

RSS feed - May 21, 2008

A RSS feed is now available on lilypond.org. It contains all news announced on the web site start page: releases, LilyPond report, new translations of the site and publications. Feed URL. The info mailing list (see Contact) is still used to announce releases and special events.

The LilyPond Report #9. May 05, 2008

Welcome to this ninth issue of the LilyPond Report!
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community. Follow this link to read the full issue...

LilyPond 2.11.45 available. April 26, 2008

Release 2.11.45 fixes a couple of bugs in the formatting engine. lilypond-book has been improved, with better performance, a bugfix about included files, and more flexibility for preprocessing documents with LaTeX variants. Support for enclosing text in a rounded box has been contributed by Valentin Villenave.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.44 available. April 14, 2008

Release 2.11.44 is available. Support for figured bass and chord names has been added to the MusicXML converter.
Bugfixes, Oude downloads.

lilypond.org日本語訳 (lilypond.org Japanese translation). 2008年4月8日 (April 4, 2008)

lilypond.orgのいくつかのページの日本語訳が出来ました。

LilyPond 2.11.43 available. March 31, 2008

Release 2.11.43 has been available since March 27. It fixes a couple of formatting bugs, and the font cache problem with MS-Windows binaries which caused excessive slowness has been fixed.
Bugfixes, Oude downloads.

LilyPond 2.11.42 available. March 9, 2008

Release 2.11.42 is out. It fixes some formatting and spacing bugs.
Bugfixes, Oude downloads.

Comparison of music engraving with Finale and LilyPond. February 25, 2008

In three articles, Andrew Hawryluk compares Finale and LilyPond in general terms, and evaluates in detail engraving capabilities of both pieces of software. The second article is an instructive analysis of Rachmaninoff’s Piano Prelude 6 engraving, including comparisons with a reference hand-engraved edition. Read the articles.

LilyPond 2.11.41 available. February 25, 2008

Release 2.11.41 is available. It has a few bugfixes, updated program messages in French, German, Spanish and Vietnamese, and updates to the MusicXML converter.
Bugfixes, Oude downloads.

LilyPond 2.11.37 available. January 3, 2008

Release 2.11.37 is available. It has a few bugfixes, and documentation changes. (Oude downloads)

LilyPond 2.11.36 available. December 13, 2007

Release 2.11.36 is now available. It has many bugfixes, updates for MusicXML import, and it includes major documentation changes from Grand Documentation Project.
Bugfixes, Oude downloads.

LilyPond 2.10.33 and 2.11.33 available. September 20, 2007

Release 2.11.33 is now available.
Bugfixes 2.10, Bugfixes 2.11, Oude downloads.

LilyPond 2.11.32 available. September 2, 2007

Release 2.11.32 is now available.
Bugfixes, Oude downloads.

LilyPond 2.11.31 available. August 31, 2007

Release 2.11.31 is now available. It has more bugfixes, updates for MusicXML import and lots of updates for the translations.
Bugfixes, Oude downloads.

LilyPond 2.11.30 available. August 20, 2007

Release 2.11.30 is now available. It has various bugfixes among others in the new spacing code, MusicXML import and lots of updates for the translations.
Bugfixes, Oude downloads.

LilyPond 2.10.29 and 2.11.29 available. August 11, 2007

Release 2.11.29 is now available. 2.10.29 has a few small fixes. 2.11.29 has several bugfixes, among others in the new spacing code, and lots of updates for the translations.
Bugfixes 2.10, Bugfixes 2.11, Oude downloads.

LilyPond 2.11.28 for FreeBSD x86_64. August 10, 2007

Release 2.11.28 is now available as a binary installer for FreeBSD x86_64. Download the installer and do sh lilypond-2.11.28-1.freebsd-64.sh in a command window.

LilyPond 2.11.28 available - July 25, 2007

Release 2.11.28 has several updates to the manual and its translations, an plethora of bugfixes and a complete cleanup of the spacing engine code.
Bugfixes, Oude downloads.

LilyPond 2.11.26 available - June 8, 2007

Release 2.11.26 supports page markers, eg. for use in tables-of-contents. In addition, it fixes a number of bugs. Enjoy!
Bugfixes, Oude downloads.

LilyPond 2.10.25 and 2.11.25 available - May 20, 2007

Release 2.11.25 has support for toplevel page breaking commands, and page breaking as a whole has been sped up significantly. Enjoy!
Bugfixes 2.10, Bugfixes 2.11, Oude downloads.

LilyPond 2.10.23 and 2.11.23 available - May 1, 2007

This has lots of bugfixes.
Bugfixes 2.10, Bugfixes 2.11, Oude downloads.

Übersetzung der Dokumentation - 10. April 2007

Die Kapitel 1-5 (der Abschnitt für Anfänger) des LilyPond-Benutzerhandbuchs sind auf deutsch übersetzt — sie sind erhältlich für die Veranderingen online und Oude downloads.

LilyPond 2.11.22 available - April 10, 2007

This release has updates of the dot collision code.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.21 available - March 24, 2007

This release has some documentation updates.
Bugfixes, Veranderingen, Oude downloads.

Traduction de la documentation en français - 25 février 2007

Les chapitres 1 à 4 et 6 du manuel de l’utilisateur sont désormais traduits, et disponibles en ligne — version 2.10, version 2.11. Les traductions sont également incluses dans la documentation téléchargeable.

LilyPond 2.10.20 and 2.11.20 available - February 25, 2007

This release fixes many bugs.
Bugfixes 2.10, Bugfixes 2.11, Veranderingen, Oude downloads.

LilyPond 2.10.19 and 2.11.19 available - February 18, 2007

This release fixes many bugs.
Bugfixes 2.10, Bugfixes 2.11, Veranderingen, Oude downloads.

LilyPond 2.11.18 available - February 12, 2007

This release fixes still more bugs, and included singing support through festival contributed by Milan Zamazal.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.17 available - February 9, 2007

This release fixes still more bugs.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.16 and 2.11.16 available - February 4, 2007

This release fixes many bugs. (Bugfixes 2.10, Bugfixes 2.11, Veranderingen, Oude downloads)

LilyPond 2.10.15 and 2.11.15 available - February 1, 2007

This release will stretch piano staves on a system-by-system basis and add a few glyphs: a black harmonic note head and the slashed mirrored flat.
Bugfixes 2.10, Bugfixes 2.11, Veranderingen, Oude downloads.

LilyPond 2.10.14 and 2.11.14 available - January 26, 2007

This release has a rewrite of the line-spanner code, responsible for among other glissandi and text-crescendos, making them more flexible.
Bugfixes, Veranderingen, Oude downloads

LilyPond 2.10.13 and 2.11.13 available - January 17, 2007

This release fixes a few minor but irritating bugs. In addition, the 2.11 release has updates of the tutorial.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.12 available - January 17, 2007

This release fixes lots of bugs. In particular, the tie formatting has been further improved, and memory usage has been improved enormously.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.12 available - January 17, 2007

This release mirrors 2.11.12. Notably, it has the same memory usage improvements.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.11 available - January 12, 2007

This release mostly has the same fixes as 2.11.11.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.11 available - January 11, 2007

This release has further fixes for popular bugs. Timing of the MIDI output won’t get confused by tuplets and grace notes anymore. Some fat has also been trimmed of the skyline code performance.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.10 available - January 8, 2007

LilyPond 2.11.10 has further review of the test-suite, performance and code coverage. This brought to light several problems that were fixed. Notably, 2.11.10 fixes lots of regressions in optical correction spacing and MIDI dynamics. Also, this version is 20 to 50 % faster than previous 2.11 releases.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.10 available - January 8, 2007

This release fixes several popular bugs, among others: MIDI files that go silent after (de)crescendi, and tuplets problems with quoting and part-combining.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.9 and 2.10.9 available - January 3, 2007

This release has a couple of bugfixes, and —in 2.11.9— further improvements in the regression test suite
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.8 and 2.10.8 available - January 3, 2007

New! Improved! With even more bugfixes!
Bugfixes, Veranderingen, Oude downloads.

lilypond.org auf deutsch - 31. Dezember 2006

Die LilyPond-Webseiten sind jetzt auch auf deutsch übersetzt!

lilypond.org en español - December 29, 2006

¡Ya está disponible la versión en español del sitio web de LilyPond!

LilyPond 2.11.7 and 2.10.7 available - January 1, 2007

New! Improved! With even more bugfixes!
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.6 available - December 30, 2006

This release supports arbitrary fractional alterations, allowing music with different microtonal conventions to be typeset.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.6 available - December 30, 2006

New! Improved! With even more bugfixes!
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.5 available - December 24, 2006

These releases complete the translation infrastructure for Documentation.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.5 available - December 24, 2006

New! Improved! With even more bugfixes!
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.4 available - December 21, 2006

The vertical spacing improvements that were introduced in 2.11.0 now work within a system as well as between systems.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.11.3 available - December 19, 2006

This release has graphical test results and several website build improvements.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.3 available - December 19, 2006

This release fixes several bugs.
Bugfixes, Oude downloads.

LinuxPPC binaries available! - December 19, 2006

From now on, our GUB binary builds include support for Linux/PPC. (Oude downloads)

Traduction du tutoriel en français. December 13, 2006

Fruit du travail d’une équipe de traducteurs, le tutoriel en français est maintenant disponible en ligne. Version 2.10, Version 2.11.

LilyPond 2.11.2 available - December 12, 2006

This release supports glissandi and harmonics in tablature.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.2 available - December 12, 2006

A new stable release of LilyPond is available.
Bugfixes, Oude downloads.

LilyPond 2.11.1 available - December 4, 2006

This release has improved support for horizontal spacing.
Bugfixes, Veranderingen, Oude downloads.

LilyPond 2.10.1 available - December 3, 2006

A new stable release of LilyPond is available.
Bugfixes, Oude downloads.

LilyPond 2.11.0 available - November 27, 2006

This release has improved support for vertical spacing. (Veranderingen, Oude downloads)

LilyPond 2.10.0 available - November 11, 2006

A new stable release of LilyPond is available. (Announcement, Veranderingen, Oude downloads)

GIT repository online - November 11, 2006

LilyPond development has moved over its source code to GIT, the fast version control system. Check out our repository at gnu.org.

LilyPond 2.9.29 available - November 5, 2006

This release has many more bugfixes.
Bugfixes, Oude downloads.

LilyPond 2.9.28 available - November 3, 2006

This release has many more bugfixes.
Bugfixes, Oude downloads.

LilyPond 2.9.27 available - October 28, 2006

This release has a new FretBoards context, and some further bugfixes.
Bugfixes, Veranderingen, Oude downloads.

Music streams thesis available - October 21, 2006

The last months, Erik Sandberg has been overhauling the internals of Lily. This change introduces a new intermediate format, Music Streams, which will make it easier get music data out of LilyPond. A copy of the thesis is now available from lilypond.org (Publications).

LilyPond 2.9.26 available - October 20, 2006

This release has further bugfixes.
Bugfixes, Oude downloads.

LilyPond 2.9.25 available - October 18, 2006

This release has more bugfixes; from now on, binaries are also available for x86/64.
Bugfixes, Oude downloads.

LilyPond 2.9.24 available - October 15, 2006

This release has support for right hand guitar fingerings, and offers some bugfixes. (Veranderingen, Bugfixes, Oude downloads)

LilyPond 2.9.23 available - October 12, 2006

This release cuts fragments of EPS directly from your finished score, and makes it easier to insert ties into lyrics. (Veranderingen, Oude downloads)

LilyPond 2.9.22 available - October 9, 2006

Test this release candidate for LilyPond 2.10! (Oude downloads)

LilyPond 2.9.21 available - October 4, 2006

Test this release candidate for LilyPond 2.10! (Oude downloads)

LilyPond 2.9.20 available - October 3, 2006

Test this release candidate for LilyPond 2.10! (Oude downloads)

LilyPond 2.9.17 available - September 2, 2006

This release fixes many bugs. Among others, MacOS X QuickTime now honors tempo changes are in the MIDI output. (Veranderingen, Oude downloads)

LilyPond 2.9.16 available - August 25, 2006

In this release, chords may be partially tied and lyric extenders have tunable padding. Moreover, many bugs were fixed (Veranderingen, Oude downloads)

LilyPond 2.9.15 available - August 20, 2006

This releases fixes many bugs in the 2.9.14 release. (Oude downloads)

LilyPond 2.8.6 available - August 8, 2006

This release contains a few minor bugfixes; the source tarball is also available. (Oude downloads)

LilyPond 2.9.14 available - August 4, 2006

This release supports instrument name changes, dotted barlines and better spacing for floating grace notes. In addition, it contains ongoing work by Erik Sandberg to extend the interpretation phase with stream support. (Veranderingen, Oude downloads)

LilyPond 2.9.13 available - July 23, 2006

This release supports doits and falls, and more tuning options for grace note spacing and tuplet brackets. (Veranderingen, Oude downloads)

LilyPond 2.9.12 available - July 18, 2006

This release supports pdftex for lilypond-book, and uses PdfTeX for generating manuals, so page numbers and references are now clickable. (Veranderingen, Oude downloads)

LilyPond 2.9.11 available - July 12, 2006

This release wraps improvements of the last two weeks. As a new feature, it supports tunable tuplet number formatting for nested tuplets. (Veranderingen, Oude downloads)

LilyPond 2.9.10 available - June 15, 2006

This releases fixes a couple of bugs in 2.9.9. (Veranderingen, Oude downloads)

LilyPond 2.9.9 available - June 15, 2006

This releases fixes many bugs in 2.9.8 and earlier. (Veranderingen, Oude downloads)

LilyPond 2.9.8 available - June 6, 2006

2.9.8 has support for different spacing sections within a single score, and better infrastructure for automated regression testing. (Veranderingen, Oude downloads)

LilyPond 2.8.4 available - June 4, 2006

2.8.4 fixes some minor bugs, and includes a backport of the infrastructure for automated regression testing. (Oude downloads)

First test results available - June 4, 2006

After a week of frantic tweaking, the first automated testing results are available. You can now see in full glory what features are broken in the development release

LilyPond 2.9.7 available - May 30, 2006

2.9.7 has improvements in the formatting for figured bass, and includes a new framework for detecting bugs earlier, which will make the development releases even better

LilyPond 2.9.6 available - May 24, 2006

This release has new features in beam formatting: beams may now be put on single stems, and obey the beatGrouping property. MusicXML converter. (Veranderingen, Oude downloads)

New essay pages! - May 22, 2006

The Automated Engraving essay has been updated with material from the FISL talk, with pages on modeling notation and algorithms for esthetics. Happy reading!

LilyPond 2.9.5 available - May 17, 2006

This release supports object rotation, hairpins with circled tips, hairpins that run to barlines before notes and improvements in the MusicXML converter. (Veranderingen, Oude downloads)

LilyPond 2.9.4 available - May 12, 2006

This release has support for feathered beaming, and note head styles in the markup \note command. In addition, it has a lot of updates of the manual and a clean up of the spring spacer. (Veranderingen, Oude downloads)

LilyPond 2.8.2 available - May 12, 2006

This release has fixes for minor bugs and compilation issues. (Oude downloads)

LilyPond 2.9.3 is out! - May 7, 2006

This new release has lots of updates of the manual, courtesy Graham and the contributors of the mailing. It handles formatting for ties in arpegiated chords better (feature sponsored by Steve Doonan), it has al niente hairpins, courtesy of Erlend Aasland, and some cleanups of the PostScript output, courtesy David Feuer. (Veranderingen, Oude downloads)

FISL7.0 slides available - April 22, 2006

The slides for Han-Wen’s talk at FISL 7 are now online. (Publications)

LilyPond 2.8.1 is out! - April 3, 2006

Important bugfixes include CJK font handling and a Darwin/x86 port. (Veranderingen, Oude downloads)

LilyPond 2.9.1 is out! - April 3, 2006

It’s mostly a bugfix release, and it’s almoste the same as 2.8.1. This release mainly fixes problems with CJK font loading. (Veranderingen, Oude downloads)

LilyPond on MacOS X/Intel - March 31, 2006

LilyPond now also runs on Intel based macs, offering a 400% speedup over the emulated PowerPC binaries. (Oude downloads)

LilyPond 2.8.0 is out! - March 22, 2006

Version 2.8 is here! Read the release announcement. (Veranderingen, Oude downloads)

LilyPond 2.7.39 is out - March 17, 2006

This release has even more bug fixes. Please test before 2.8 is released. (Veranderingen, Oude downloads)

LilyPond 2.7.38 is out - March 12, 2006

This is likely to be the last release candidate before we release 2.8, so report any bugs that you might find. New attractions include: lilypond postscript files now work with GSView, cut & pasting lily code from PDF files should now work, and spacing fixes for multi-measure rests. (Veranderingen, Oude downloads)

LilyPond 2.7.37 is out - March 4, 2006

This release has more bug fixes. Please help us by testing it! (Veranderingen, Oude downloads)

LilyPond 2.7.36 is out - February 24, 2006

This is another release candidate for 2.8. It has lots of bug fixes and polishes to the documentation. It also contains support for creating ties that are only on their right side connected to note heads, which is handy for repeats (feature sponsored by Steve Doonan). The documentation suite can now be downloaded as a separate tarball from lilypond.org. (Veranderingen, Oude downloads)

LilyPond 2.7.35 is out - February 19, 2006

This release has lots of bugs fixes. The plan is to release 2.8 at the end of this month, so bug reports are very welcome. By definition a bug is release critical if it wasn’t present in version 2.6. (Veranderingen, Oude downloads)

LilyPond 2.7.34 is out - February 16, 2006

This release has a bunch of bugfixes, and new features. Newly created contexts may also be named with \new Voice = "alto". Thicknesses of tie and slurs may be tuned separately for the endings and the middle part. (Veranderingen, Oude downloads)

LilyPond 2.7.33 is out - February 10, 2006

Items directly connected with a music input element may be parenthesized, for example,

{
  c4 -\parenthesize -.
  <d \parenthesize fis a>
}

This feature was sponsored by Ramana Kumar. (Veranderingen, Oude downloads)

LilyPond 2.7.32 is out - February 7, 2006

This release contains some syntax changes: words inside the \paper and \layout block are henceforth written with dashes, for instance:

{
  \layout {
    ragged-right = ##t
  }
}

Furthermore, in this release, we have dropped some legacy code from our library. Now, lily uses standard C++ strings and the STL vector. (Veranderingen, Oude downloads)

LilyPond 2.7.31 is out - February 2, 2006

This release fixes a load of bugs, and has some internal cleanups. Exported C++ members are now named ly:class-name::function-name in Scheme instead of Class_name::function_name. We are now using C++ vectors and strings instead of our own. The Linux/FreeBSD builds now include wrappers for Python scripts too, so you can run convert-ly and midi2ly. (Veranderingen, Oude downloads)

LilyPond 2.7.30 is out - January 30, 2006

This release has a few bug fixes, like the solfa note head shape and collisions, the \epsfile command, and in getting No. ligature in normal words. (Veranderingen, Oude downloads)

LilyPond 2.7.29 is out - January 27, 2006

This release has the following new features. Alignments of staves may be tuned per system (feature sponsored by Trevor Baca), individual systems may be positioned manually (feature sponsored by Trevor Baca and Nicolas Sceaux), a linebreaking configuration can now be saved as a ‘.ly’ file automatically. This allows vertical alignments to be stretched to fit pages in a second formatting run (feature sponsored by Trevor Baca and Nicolas Sceaux). (Veranderingen, Oude downloads)

LilyPond 2.7.28 is out - January 22, 2006

This release contains numerous small fixes that were already in our GUB binaries. In addition, it has further polish for formatting of tied chords. Theses improvements were sponsored by Steve Doonan. (Veranderingen, Oude downloads)

LilyPond 2.7.27, release 4 - January 13, 2006

The fourth release of our Grand Unified Binary for 2.7.27 is available. This release uses Pango 1.11.1, which has support for ligatures and kerning. Enjoy! (Oude downloads)

LilyPond 2.7.27, release 3 - January 12, 2006

The third release of our Grand Unified Binaries is available. This release fixes external font-support, the decompression flag for Linux. Also, we have support for FreeBSD as well! Jump to the Oude downloads get them!

LilyPond 2.7.27 binaries are out - January 7, 2006

Starting with 2.7.26, the development team has been working on the installers. We’re proud to announce another version of these: they are now available for Linux/x86, MacOS X and Windows.

LilyPond 2.7.27 is out - January 7, 2006

This release allows you to switch staff lines on and off individually (feature sponsored by Andrea Valle). (Veranderingen, Oude downloads)

Linux Journal article - January 2006

Linux Journal publishes an article on Make Stunning Schenker Graphs with GNU LilyPond. It is a in-depth but hands-on feature article with crisp LilyPond graphics.
Author Kris Shaffer remarks “GNU LilyPond generates beautiful graphics that make commercial alternatives seem second-rate.” This article is now available on-line.

New binaries for LilyPond 2.7.26 - January 4, 2006

The Development team has been working around the clock to improve to fix the first wave bugs reported by you. The new results for MacOS and Windows are up on the Oude downloads page. Let us know how you fare!

LilyPond 2.7.26 is out - December 31, 2005

This release has an improvement in the MusicXML importer (feature sponsored by Mark vd Borre’s Music Academy): now, staves and voices are also setup, so you can readily run LilyPond on the .ly output. The important occasion for this release is our new build environment: we have completely revamped it, which means that binaries for all platforms (including MacOS, Windows, Linux/x86, but probably FreeBSD too) will be more quickly available for download. A happy 2006 from the LilyPond Development Team! (Veranderingen, Oude downloads)

LilyPond 2.7.25 is out - December 24, 2005

This release has various bugfixes. Also, stems on the center line now have their directions interpolated to minimize the number of direction changes (feature sponsored by Basil Crow and Mike Rolish). (Veranderingen, Oude downloads)

LilyPond 2.7.24 is out - December 20, 2005

This release fixes a couple of bugs, but more importantly, slurs now avoid TupletNumbers, and tuplet numbers may enter the staff (feature sponsored by Trent Johnston), tuplet brackets and numbers are implemented as separate grobs, TupletBracket and TupletNumber (rewrite sponsored by Trent Johnston), string arguments for music functions may be specified without # marks. This allows syntactical constructs (like \clef and \bar) to be expressed in generic music functions. (Veranderingen, Oude downloads)

LilyPond 2.7.23 is out - December 19, 2005

This release has the following new features:

(Veranderingen, Oude downloads)

LilyPond 2.7.22 is out - December 9, 2005

This release has better support for MusicXML: it also supports ties, beams and editorial accidentals. It also has more options for spacing Lyrics; it is now possible to separately specify minimum distances for normal and hyphenated syllables. These features were sponsored by Mark van den Borre and Bertalan Fodor. (Veranderingen, Oude downloads)

LilyPond 2.7.21 is out - December 5, 2005

Saint Nicholas brings you ... a MusicXML convertor for LilyPond! The convertor is basic, but working. Check out the LilyPond Software Design pages for MusicXML features that can be sponsored.

LilyPond 2.7.20 is out - December 2, 2005

This release contains the following improvements: Texts set in a TrueType font are now kerned. Using the TeX no longer requires linking or dynamically opening the kpathsea library, making the backend more easily usable on various systems (feature sponsored by Christian Ebert of Black Trash Productions). (Veranderingen, Oude downloads)

LilyPond 2.6.5 is out - December 1, 2005

This release updates the bugreporting address and reorganizes the documentation tree. (Oude downloads)

LilyPond 2.7.19 is out - November 26, 2005

This version contains a few bugfixes, and now allows the type of brackets in system start bracket hierarchies to be specified. Also, the horizontal alignment of rehearsal marks may be changed: marks can be put on key signatures, clefs, time signatures, etc. (Veranderingen, Oude downloads)

LilyPond 2.7.18 is out - November 21, 2005

This version features nestable system start delimiters, like bracket, brace. It also adds "square" line bracket (feature sponsored by Trevor Baca). It also has refactored routines for tie formatting. This will make it easier to get better tie formatting for chords (feature sponsored by Steve Doonan). It also has a few bug fixes. (Veranderingen, Oude downloads)

LilyPond 2.7.17 is out - November 17, 2005

This version has refactored routines for tie formatting. This will make it easier to get better tie formatting for chords (feature sponsored by Steve Doonan). It also has a few bug fixes. (Veranderingen, Oude downloads)

LilyPond 2.7.16 is out - November 11, 2005

This release fixes a large number of bugs. Please upgrade before reporting bugs in the 2.7 series. (Veranderingen, Oude downloads)

LilyPond 2.7.15 is out - November 3, 2005

This release has another massive cleanup of the backend. Each grob property may also be a "grob closure". This means that it is possible to combine functions. Calculation of extent and offset of grob is now controlled via the ‘X-extent’, ‘Y-extent’, ‘X-offset’ and ‘Y-offset’ properties. (Veranderingen, Oude downloads)

LilyPond 2.7.14 is out - October 23, 2005

This release has more cleanup in the layout-engine. Now, properties that have Procedure values are thought to be procedures that compute said property, i.e.

\override Beam #'direction = #(lambda (grob)
(if (> (random 10) 5) UP DOWN))

will set a random direction for beams. (Veranderingen, Oude downloads)

LilyPond 2.7.13 is out - October 18, 2005

This release features slashed numerals, plus signs and interruptible extender lines for figured bass. Merging of Figured bass lines has been made switchable with the figuredBassCenterContinuations property. For each grob, a subproperty in ‘callbacks’ property defines the procedure which computes it. This is major internal cleanup, which also provides advanced tweakability for power users. (Veranderingen, Oude downloads)

LilyPond 2.6.4 is out - October 11, 2005

This release fixes a few minor problems with the stable series. (Veranderingen, Oude downloads)

LilyPond 2.7.12 is out - October 07, 2005

It features more annotations for the page layout engine and some more sponsored features. Beamlets may stick out of the side of beams (feature sponsored by Trevor Baca); new support for figured bass with support for continuation lines and tuning of figures, brackets, and alignments (feature sponsored by Trent Johnston); vertical alignments of staves can now be tuned easily for individual systems (feature sponsored by Nicolas Sceaux). (Veranderingen, Oude downloads)

LilyPond 2.7.11 is out - October 02, 2005

Vertical spacing for page layout can now be tuned for each system individually (feature sponsored by Trevor Baca and Nicolas Sceaux). The slope of a stem-tremolo may be set manually (feature sponsored by Sven Axelsson). There are a number of cleanups in the handling and representation of systems, among other features and bug fixes. (Veranderingen, Oude downloads)

LilyPond 2.7.10 is out - September 13, 2005

This version adds proper support for "laissez vibrer ties", just enter \laissezVibrer after a chord. This feature was sponsored by Henrik Frisk. It also has a couple of minor bugfixes. (Veranderingen, Oude downloads)

LilyPond 2.7.9 is out - September 5, 2005

This is mainly a bugfix release. (Veranderingen, Oude downloads)

Traduction française du site - September 03, 2005

Grâce à l’équipe des traducteurs, de nombreuses pages du site sont maintenant disponibles en français, notamment l’essai sur la gravure musicale.

LilyPond 2.7.8 is out - August 29, 2005

This release has support for right-to-left text formatting in markup commands (sponsored by Aaron Mehl). In addition, it fixes a great number of bugs, among others, support for writing MIDI files. (Veranderingen, Oude downloads)

Article in ‘De Standaard’ - August 20, 2005

The Belgian newspaper De Standaard investigates what drives Free Software authors in an article titled Delen van KENNIS zonder WINSTBEJAG (Non-profit sharing of knowlegde) using LilyPond as an example. This marks LilyPond’s first appearance in mainstream printed press.

LilyPond 2.7.7 is out - August 22, 2005

This release has a rewriting of tie formatting which was sponsored by Bertalan Fodor, Jay Hamilton, Kieren MacMillan, Steve Doonan, Trevor Baca, and Vicente Solsona Dellá. (Veranderingen, Oude downloads)

LilyPond 2.7.6 is out - August 19, 2005

This release adds support for numbered percent repeats, a feature sponsored by Yoshinobu Ishizaki. It also has bugfixes for clashes between slurs and symbols, like fingers dynamic signs. (Veranderingen, Oude downloads)

LilyPond 2.7.5 is out - August 16, 2005

Lily 2.7.5 has a large number of bugfixes, among others, in slur formatting, spacing, rest collisions and tuplet bracket formatting. (Veranderingen, Oude downloads)

LilyPond 2.7.4 is out - August 7, 2005

LilyPond 2.7.4 has support for proportional notation, where the space for a note is proportional to the time it takes. (Veranderingen, Oude downloads)

LilyPond 2.6.3 is out - August 4, 2005

This release fixes a memory corruption bug that was triggered by \override’ing Beam settings. (Oude downloads)

LilyPond 2.6.2 is out - August 2, 2005

This release has a few bugfixes, among them: the autopackage will run in more platforms, LilyPond will be much quicker for large lilypond-book documents, and the up and down Fa note heads for shaped heads have been swapped. (Veranderingen, Oude downloads)

LilyPond 2.7.3 is out - July 25, 2005

LilyPond 2.7.3 has improvements in performance which should result in faster operations (15 to 20 percent). It also contains the new "\displayLilyMusic" function. (Veranderingen, Oude downloads)

LilyPond 2.7.2 is out - July 21, 2005

LilyPond 2.7.2 has support for suggested accidentals for musica ficta notation, easy entry for lyric melismata and improvements for quicker entry of scores. (Veranderingen, Oude downloads)

LilyPond 2.6 released - June 27, 2005

Version 2.6 is the latest stable release of LilyPond. It now installs in a snap on Windows, MacOS X, and any version of Linux (x86). Get up and running in minutes! Pango text formatting lets you print Unicode lyrics in your favorite script and font. Create SVG files, and edit them in Inkscape. (Announcement, Oude downloads, Veranderingen)

LilyPond 2.7.1 is out - July 20, 2005

LilyPond 2.7.1 has no user-visible changes. However, due to restructuring “under the hood”, this version will be 10 to 20 % faster. (Oude downloads)

LilyPond 2.6.1 is out - July 11, 2005

This version fixes a few minor bugs found in 2.6.0, and also works on DOS-based Windows versions. (Veranderingen, Oude downloads)

LilyPond 2.7 is out - July 9, 2005

LilyPond 2.7.0 is out. It has support for paragraph text and pitched trill notation. (Veranderingen, Oude downloads)

2.5.31 released - June 22, 2005

LilyPond 2.5.32 is now available for download (binaries for Fedora + MacOS only). It has a few very minor bugfixes, and a rewrite of the TTF embedding code, which should be a lot more robust now. (Oude downloads)

Traduction du site de LilyPond - 15 juin 2005

L’équipe des traducteurs vous présente le site de LilyPond en français. Nous travaillons sur la traduction des pages encore non traduites. Bon surf !

2.5.31 for Windows and MacOS - June 15, 2005

2.5.31 is now available for both Windows and MacOS X. The Windows version should now work with embedding TTF fonts, and the MacOS X has better help functionality. (Oude downloads)

2.5.31 released - June 15, 2005

This release has a few bugfixes. In the MacOS X version, ClickEdit has been renamed to LilyPond, and you can now upgrade your files and compile them directly from LilyPond. (Oude downloads)

2.5.30 released - June 10, 2005

This is (hopefully) the last Release Candidate before 2.6. Give it a good shake to find those last bugs! (Oude downloads)

2.5.29 released - June 7, 2005

In this release the documentation also has pictures. In addition, the Mac version can also read native mac fonts (.dfonts and fonts in resource forks). (Oude downloads)

2.5.27 released - May 31, 2005

It has a big bunch of minor bugfixes. This is another release candidate for version 2.6, which should be released within the next 2 weeks. Please send a bug report if you find a critical problem with this release. (Oude downloads)

Windows and MacOS installers available - May 26, 2005

There are now a native, standalone installers for Windows and MacOS. They also support PDF point & click. (Oude downloads)

2.5.26 released - May 26, 2005

This release has a couple of small bugfixes.

2.5.25 released - May 20, 2005

This release has many small bugfixes and updates to the documentation. (Oude downloads)

2.5.24 released - May 12, 2005

2.5.24 fixes a bunch of bugs; in particular, chord symbols (such as slashed o) should now work on all platforms. This release has a new feature: it is now possible to make staves appear in a different order from the order that they were defined. (Oude downloads)

2.5.23 released - May 6, 2005

This release has a couple of small bugfixes, and a new feature. It is now possible to start and stop the StaffSymbol, during a piece of music, by doing \stopStaff \startStaff. This can be used to produce Ossia staves. (Veranderingen, Oude downloads)

2.5.22 released - May 3, 2005

2.5.22 is a bugfix release. The most visible improvement is in the PDF : this release will produce smaller PDF files, with symbols that look better on screen. (Oude downloads)

April 25, 2005 - 2.5.21 released!

2.5.21 has more bugfixes. It also has support for "grid lines", bar like vertical line, which are aligned with the notes. The auto-beam engraver was rewritten, so it also works with irregular time signatures like 5/8. (Veranderingen, Oude downloads)

April 18, 2005

LilyPond 2.5.20 has lots of bugfixes, in particular, MIDI files of multi-movement pieces don’t overwrite each other. Version 2.5.20 also supports putting arrows on lines, such as glissandi. More details are in the the Veranderingen file, or go straight to Oude downloads.

April 15, 2005

LilyPond 2.5.19 was released. The command ‘\epsfile’ allows inclusion of EPS graphics into markup texts and the music function ‘\musicDisplay’ will display a music expression as indented Scheme code. Take a look at the Veranderingen file and Oude downloads.

April 6, 2005

2.5.18 is a bugfix release. It has many small cleanups in the web-based documentation, and many small cleanups all over the place. Oude downloads

March 31, 2005

2.5.17 is out. This release features many small bugfixes. In addition, it has support for string number notation for guitar. This feature was sponsored by Gunther Strube. Oude downloads

March 20, 2005

LilyPond 2.5.16 is out. This release fixes a few minor but irritating errors. A Fedora Core 3 binary is also available. Oude downloads

March 14, 2005

LilyPond 2.5.15 is out. This release has clean ups in the SVG output, and now uses the LilyPond number font for time signatures. It is now possible to add text before and after music. This can be used to add verses after a music. Take a look at the Veranderingen file and Oude downloads!

March 7, 2005

LilyPond 2.5.14 is out. It is now possible (and in fact, encouraged), to build LilyPond either without the Kpathsea TeX library or with the Kpathsea dynamically loaded, but only for the -btex backend. This means that packages do not have to depend on TeX anymore. With this, the Windows download size will go down significantly. Take a look at the Veranderingen file and download Oude downloads!

March 7, 2005

LilyPond 2.4.5 is out. This release backports the tieWaitForNote feature and has support for tetex-3.0. Oude downloads

February 28, 2005

LilyPond 2.5.13 is available for Fedora Core 3. You need to install ESP Ghostscript 8.15rc3. Unfortunately, this version of Ghostscript lacks the IJS dynamic library, which means that it will conflict with the gimp-print package. You may install it with –nodeps. Use at your own risk.

February 28, 2005

LilyPond 2.5.13 is out. This release has Point and click support for PDF output. You can read more about it here. Take a look at the Veranderingen file and download Oude downloads!

February 26, 2005

The LilyPond Snippet Repository (LSR) is a searchable database of LilyPond code snippets. You can add snippets too, so join the LSR project, and contribute creative ideas for using LilyPond.

February 21, 2005

LilyPond 2.5.12 is out. The big news is that this release supports TrueType fonts. This means that it is now possible to use all fonts available via FontConfig. Also, arpeggios may be written out using ties and individual objects may have colors! Take a look at the Veranderingen file and Oude downloads!

February 4, 2005

LilyPond 2.5.11 is out. In this release, foreign character sets are now supported in lilypond-book too, and it is possible to put system separators between systems. Oude downloads!

January 31, 2005

LilyPond 2.5.10 is out. This release sports as new EPS backend, based on the PS backend. This backend is used in the new and improved lilypond-book script. Oude downloads

January 26, 2005

LilyPond 2.5.9 is out. This release fixes a couple of annoying bugs in the direct PS output for piano braces. Oude downloads

January 16, 2005

LilyPond 2.5.8 is out. This release has many internal code cleanups. In addition, accuracy of error reporting has been improved. See the change log and Oude downloads!

January 11, 2005

LilyPond 2.5.7 is out. This release has a completely usable Pango integration for the PS backend. The default font is Century Schoolbook from the PS font suite. It also has small updates to the tablature settings by Erlend Aasland, assorted manual updates by Graham, and an overhaul of the font code by Werner. Oude downloads and check out the changes in the ChangeLog.

January 02, 2005

LilyPond 2.5.6 was released. This is a "technology preview" release, which means that it has all kinds of nifty features, but is not actually usable for producing nicely printed scores. For this reason, an RPM of this release was not produced. The PS backend is now completely switched over to Pango/FontConfig: for -f ps, LilyPond only accepts UTF8 input, all text fonts are loaded through Pango, the TeX backend now offloads all metric computations to LaTeX, the SVG and GNOME backends are broken, most probably. Oude downloads and check out the changes in the ChangeLog.

December 28, 2004

LilyPond 2.5.5 is out. It is the first one to link against FontConfig and Pango, although it is only available in the "-f ps" output. The default output format has been changed back TeX while we stabilize the Pango/FontConfig integration. Oude downloads and check out the changes in the ChangeLog.

December 20, 2004

LilyPond 2.5.4 is out. This release has some major brainsurgery in the font handling. As of now, LilyPond loads the music fonts in OpenType font format using FreeType. This has made a lot of things simpler, including font handling for the GNOME backend and SVG backend. Oude downloads and check out the changes in the ChangeLog.

December 3, 2004

LilyPond 2.5.3 was released. A new script, ‘\espressivo’ has been added, for a combination of crescendo and decrescendo on a single note. In markups, expressions stacked with ‘\column’, ‘\center-align’, etc, are not grouped with ‘< ... >’ anymore, but with ‘{ ... }’. LilyPond will now avoid line breaks that cause long texts to stick outside of the page staff. Grace notes following a main note, used to be entered by letting the grace notes follow a skip in a parallel expression. Oude downloads and check out the changes in the ChangeLog.

November 26, 2004

LilyPond 2.5.2 was released. It has several goodies, including solfa-notation (shaped noteheads), and an easier mechanism for customizing title, footer and header layout. Don’t forget to rebuild the fonts, as they have been changed to accomodate the solfa-notation. Oude downloads and check out the changes in the ChangeLog.

November 20, 2004

LilyPond 2.5.1 is out. This is an experimental release, containing some proof-of-concept code for our graphical layout editor. You can add and remove things from the file, and the tweaks will still work, as long as the tweaked notes remain in the place (ie. start at the same time-wise and be part of the same context). Further attractions are: the gnome backend now also draws beams and slurs, updates to the SVG backend, support for the lmodern font set for TeX, various bugfixes. Oude downloads and check out the changes in the ChangeLog.

November 12, 2004

The LilyPond development is OPEN once again! The first release of the 2.5 series has the following new Features: Positioning of slurs can now be adjusted manually, Grace notes are correctly quoted and formatted when using cue notes, Cue notes can now be created with

\cueDuring #VOICE-NAME #DIRECTION { MUSIC }

Stemlets (short stems over beamed rests) have been added. In addition, Jan hacked together some highly experimental code where you can use the mouse to drag and drop objects in the -f gnome backend. These tweaks can be saved and are applied to the PS and TeX output as well. Oude downloads and check out the changes in the ChangeLog.

November 11, 2004

LilyPond 2.4.2 is out. This release fixes a number of security problems with –safe, and adds a lot of polishing fixes. Oude downloads

November 4, 2004

LilyPond 2.4.1 is out. This release includes a number of small fixes that were made to 2.4.0 last week. Oude downloads and check out the changes in the ChangeLog.

October 31, 2004

LilyPond 2.4.0 was just released! This new stable version has support for page-layout, completely rewritten slur formatting and many other improvements. Read about them in the Veranderingen file. Oude downloads

October 29, 2004

LilyPond 2.3.26 is out. This is another 2.4 release candidate. This release fixes a number of minor bugs, and some problems with the conversion scripts. Oude downloads and check out the changes in the ChangeLog.

October 29, 2004

2.3.25 is the final release candidate for LilyPond 2.4. Werner has been overhauling the TeX macros and lilypond-book. In addition, this release contains an important fix for raggedbottom page-layout. Oude downloads and check out the changes in the ChangeLog.

October 27, 2004

LilyPond 2.3.24 is a further polished 2.4 release candidate. This release has more improvements by Werner for the TeX backend, and a bunch of other small fixes. Oude downloads and check out the changes in the ChangeLog.

October 24, 2004

LilyPond 2.3.23 has bugfixes in the documentation, lilypond-book and –preview output. This release can be considered as a release candidate for LilyPond 2.4. Oude downloads and check out the changes in the ChangeLog.

October 10, 2004

LilyPond 2.3.22 fixes a bunch more bugs, to make 2.4 a really stable release. In addition, it renames the \paper{} block to \layout{}. The \bookpaper{} block is now called \paper{}. Oude downloads and check out the changes in the ChangeLog.

October 09, 2004

LilyPond 2.3.21 is out. It is a serious release candidate for the next stable release LilyPond. This version has a cleanup and some small formatting improvements of the slur code. Oude downloads and check out the changes in the ChangeLog.

October 02, 2004

LilyPond 2.3.20 was released. It fixes the biggest problems with encoding and the TeX backend. As a result, latin1 characters (like the german SS) show up correctly in the output once again. Also it has the usual bugfixes and updates in the documentation. Oude downloads and check out the changes in the ChangeLog.

September 29, 2004

The LilyPond development team will be present at the Free Software Bazaar of the NLUUG SANE 2004 conference today. If you are in the neighborhood, drop by for live contact with the Team or just a friendly chat. Registration is not required to attend.

September 26, 2004

LilyPond 2.3.19 is out. It’s mainly a bugfix release. Oude downloads and check out the changes in the ChangeLog.

September 20, 2004

LilyPond 2.3.18 was released. It has further improvements in the slur formatting, and a small syntax change: the mode changing commands (‘\chords’, ‘\lyrics’, etc.) have been renamed to ‘\chordmode’, ‘\lyricmode’, etc. The command ‘\chords’ is an abbreviation for \new ChordNames \chordmode ... ‘\drums’, ‘\lyrics’, ‘\chords’, ‘\figures’ function similarly. Oude downloads and check out the changes in the ChangeLog.

September 11, 2004

LilyPond 2.3.16 was released. It fixes a couple of annoying bugs, and has an important addition in the slur-formatter. Slurs that pass note heads much closer than the average distance get an extra penalty. This fixes a lot of difficult slurring cases. See input/regression/new-slur for some examples. Please consider this release as a 3.0 pre-release so try to find as many bugs as possible. A report including a small .ly example can be filed at bug-lilypond@gnu.org In this case, a bug is defined as something that the current 2.3 does worse than the latest 2.2 release. We want to be sure that no output will get uglier by upgrading to 3.0, so that once 3.0 is out, nothing will hold users back in switching. Oude downloads and check out the changes in the ChangeLog.

September 10, 2004

LilyPond 2.3.15 was released. It fixes for some gaffes with the new vertical spacing engine, has lots of documentation updates, and has support for landscape output in the direct postscript output. Also, the types of events quoted with ‘\quote’ can now be tuned with ‘quotedEventTypes’. By default, only notes and rests end up in quotes. Oude downloads and check out the changes in the ChangeLog.

September 6, 2004

LilyPond 2.3.14 was released and has exciting features! LilyPond will try to keep staves at the same distances across a page, but it will stretch distances to prevent collisions; key signature cancellations are now printed before the bar line; different voices that all use "\quote" can now refer to each other. Oude downloads and check out the changes in the ChangeLog.

August 29, 2004

LilyPond now has a Documentation Editor, Graham Percival. From now on, he will oversee that useful information flows from the mailiing list into the manual. Also, if there are unclear sections in the manual, let him know via one of the mailing lists. As a start of his career, he worked to transform the "Templates" section of the website into a readable and comprehensive chapter of the user manual. A lot of cheers for Graham!

August 29, 2004

LilyPond 2.3.13 was released. The new slur code was improved, scripts can be made to avoid slurs, by setting inside-slur to #f. It is no longer necessary to instantiate "up" and "down" staves separately when using \autochange. Jurgen Reuter refreshed the logic around mensural flags, so they are adjusted for staff lines once again. Oude downloads and check out the changes in the ChangeLog.

August 24, 2004

LilyPond 2.2.6 fixes a few minor issues, among others, the disappearing metronome mark. Oude downloads and check out the changes in the ChangeLog.

August 23, 2004

LilyPond 2.3.12 is out. This release has a lot of fixes and a new feature: there is now support for putting two slurs on chords, both above and below. This is switched on with the ‘doubleSlurs’ property. Oude downloads and check out the changes in the ChangeLog.

August 3, 2004

LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few annoying bugs fixed. Oude downloads and check out the changes in the ChangeLog.

August 1, 2004

LilyPond 2.3.10 is out. This release has a major clean-up of the input/test/ directory. Many examples have been moved to the regression test or manual, and the superfluous or outdated ones have been removed. The directory has gone from 146 examples to 72 examples. That means that we’re halfway cleaning it out. Incidentally, the manual has gone from 200 to 220 pages. New features:

Oude downloads and check out the changes in the ChangeLog.

July 30, 2004

LilyPond 2.3.9 is out. The important change is that lilypond now once-again directly runs the binary. The old wrapper script has been renamed to lilypond-latex.py, and should only be used for legacy projects. The recommended route is either using lilypond directly (with \book, you can have multiple movements within one document), or to run lilypond-book with a LaTeX wrapper file. This release also fixes a bunch of small errors. I now consider LilyPond feature complete for a 3.0 release. Next on the TODO list is updating the manual, and after that’s done we can release 3.0. The projected date for this to happen is in about a month. Oude downloads and check out the changes in the ChangeLog.

July 23, 2004

LilyPond 2.3.8 fixes a few minor bugs in the new slur code, and has rewritten support for ledger lines. Now, in tight situations, ledger lines will be shortened so they stay separate. This also required a cleanup of the Ambitus implementation. Oude downloads and check out the changes in the ChangeLog.

July 19, 2004

LilyPond 2.3.7 was released and has new exciting features! The slur formatting has been rewritten. The new slur code works similar to the Beam formatter: scores are assigned for all esthetic components of a slur. A large number of combinations for begin and end points is then tried out. Slurs will now also take into account collisions with staff lines, scripts (like staccato and accent) and accidentals. In the LilyPond emacs mode, the ‘|’ will now display the current beat within the measure. Oude downloads and check out the changes in the ChangeLog.

July 15, 2004

LilyPond 2.2.5 was released. It has a few bug fixes from 2.3.x. Oude downloads and check out the changes in the ChangeLog.

July 11, 2004

An introductory article on LilyPond appeared on Linux Journal.

July 5, 2004

LilyPond 2.3.6 was released. This release has more updates for the Fret diagram code (thanks, Carl!), fixes a bunch of bugs, including a serious one that trashed a lot of beam formatting, and was also present in the 2.2 series. Oude downloads and check out the changes in the ChangeLog.

July 5, 2004

LilyPond 2.2.4 was released. It is mainly a bug fix release. Oude downloads and check out the changes in the ChangeLog.

June 25, 2004

LilyPond 2.3.5 has numerous small bugfixes and cleanups, and features more work in the experimental GNOME output module. Adventurous hackers can check the instructions at scm/output-gnome.scm and try to run buildscripts/guile-gnome.sh to see what the fuss is all about. Carl Sorensen also provided us with more patches to the fret-diagram output. Check out the ChangeLog and Oude downloads.

June 20, 2004

LilyPond 2.2.3 has a turkish translation and fixes a few minor bugs that were reported over the past month. Check out the ChangeLog for a full description and Oude downloads.

June 13, 2004

LilyPond 2.3.4 further improves the output backends. As a result, manual page-breaks, multiple output formats and putting \score into markups now works. Check out the ChangeLog and Oude downloads.

May 31, 2004

LilyPond 2.3.3 has many internal changes relating to the output backend (PostScript) and page-layout. In addition, it contains a few bugfixes for recently reported problems. Check out the ChangeLog and Oude downloads.

May 31, 2004

LilyPond 2.2.2 is out. It has a number of small bugfixes, so upgrade if any of these errors concern you. Check out the ChangeLog or head straight to the Oude downloads.

May 26, 2004

LilyPond 2.3.2 is out. This release has a lot of internal changes relating to page layout, but also sports experimental fret-diagram code. Check out the Veranderingen or head straight to the Oude downloads.

May 9, 2004

LilyPond 2.3.1 is out. This release has many new and cool features. Check out the Veranderingen or head straight to the Oude downloads.

May 4, 2004

Help LilyPond get better, and join in on LilyPond development! This call for help was posted on the mailing list a month ago, and we are still looking for a Release Meister, Code Janitor, Newsletter editor and a Writer for implementation Documentation. Of course, any other help is also welcome!

May 3, 2004

LilyPond 2.2.1 has been released. It fixes a handful of bugs. Oude downloads.

April 17, 2004

LilyPond 2.2.0 is now available on Windows, and should find its way to the Cygwin mirrors soon.

April 12, 2004

LilyPond 2.3.0 is the first release in the 2.3 cycle. The focus for 2.3 is page layout, so instrumentalists can force parts to have page breaks at sane turning points. This release is experimental; expect things to break! More info in the Veranderingen. Oude downloads.

April 8, 2004

A French article on the new LilyPond release appeared on linuxfr.org.

April 8, 2004

Binaries for LilyPond 2.2.0 are available for MacOS X, Slackware, Mandrake and Debian Woody. Oude downloads

April 1, 2004

LilyPond 2.2.0 is out! This new stable version has completely revamped support for for orchestral score formatting, cue notes, font size management, lyric formatting, drum notation/playback and document integration. Read about it in the announcement or skip to the Oude downloads.

March 31, 2004

LilyPond 2.1.37 has build fixes for Cygwin and SUSE, bugfixes for part-combining and chord tremolos and even more documentation polish. This should be the final release candidate; expect only regression bugs to be fixed before 2.2. Oude downloads.

March 30, 2004

LilyPond 2.1.36 has many fixes in the user manual. Oude downloads.

March 28, 2004

LilyPond 2.1..35 fixes a slew of bugs, and has the raggedlast option, which causes paragraph like line breaking for scores. More info in the Veranderingen. Oude downloads

March 22, 2004

LilyPond 2.1.34 fixes minor bugs, and has more rewriting. Oude downloads.

March 21, 2004

LilyPond 2.1.33 fixes a serious bug, and a few other irritations. Oude downloads

March 20, 2004

LilyPond 2.1.32 has more rewriting in the user manual. There is also an experimental implementation of optimal page breaking (Postscript backend only). Oude downloads.

March 15, 2004

LilyPond 2.1.31 is out. It has fixes the alignment of bass figures and spurious dynamic warnings in MIDI. New attractions include rewritten font-selection routines. See the Veranderingen and Oude downloads.

March 14, 2004

The linuxmusician.com interview made the slashdot frontpage!.

March 11, 2004

linuxmusician.com is running an interview with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main authors of LilyPond.

March 11, 2004

LilyPond 2.1.30 has editorial fixes for the manual, and experimental support for page layout in the PostScript backend. See the Veranderingen and Oude downloads.

March 9, 2004

LilyPond 2.1.29 fixes a couple of MIDI bugs, and has experimental support for producing titles with markup.

February 29, 2004

In LilyPond 2.1.28 Scheme property functions may be used argument to set!. In addition, parts of the manual have been proofread and corrected in this release. See the Veranderingen and Oude downloads.

February 24, 2004

LilyPond 2.1.27 takes into account instrument transpositions when quoting other voices. This release also fixes a number of lyrics related bugs. See the Veranderingen and Oude downloads.

February 23, 2004

LilyPond 2.1.26 has a new, experimental feature for quoting other voices in instrumental parts. This can be used to produce cue notes. More information in the Veranderingen. Oude downloads

February 18, 2004

LilyPond 2.1.25 fixes many bugs, and changes the conventions for altering accidental rules. Oude downloads

February 16, 2004

LilyPond 2.1.24 has a big internal rewrite. One of its practical consequences is that \with now also works with Score contexts. Further 2.1.23, which was not announced here, fixes a few bugs caused by the change of \property syntax and has updates in the Program Reference document. More information in the Veranderingen. Oude downloads

February 13, 2004

LilyPond 2.1.22 has a simplification of the \property syntax: it is shorter and more consistent now. More information in the Veranderingen. Oude downloads

February 12, 2004

In LilyPond 2.1.21, output tweaks can be done at multiple levels of the context hierarchy. In addition, it has a bunch of bugfixes, improvements in the documentation. More information in the Veranderingen. Oude downloads

February 9, 2004

LilyPond 2.1.20 has MIDI output for drums. It also sports a completely rewritten lilypond-book script, which is cleaner, shorter, and faster. It also has a large number of bugfixes. More information in the Veranderingen. Oude downloads

February 5, 2004

LilyPond 2.1.19 has rewritten support for drum notation. This release also makes some long-standing cleanups: the removal of Thread (all functionality is now moved into Voice) and Lyrics (functionality moved to LyricsVoice) context. More information in the Veranderingen. Oude downloads

February 4, 2004

LilyPond 2.1.18 is out. This release has the new part-combiner installed by default, and a similar implementation of autochange. More information in the Veranderingen. Oude downloads

February 2, 2004

LilyPond 2.1.17 is out. It adds texts (solo, a due) for the part combiner. It also reinstates the ‘--safe’ option which prevents havoc by Scheme exploits. More information in the Veranderingen.

January 28, 2004

LilyPond 2.1.16 is out; its main feature is that it fixes the autobeams gaffe of 2.1.15. The part-combiner has been tested successfully on larger pieces. In the near future, expect more part-combining eye-candy. More information in the Veranderingen. Oude downloads

January 26, 2004

LilyPond 2.1.15 further improves the part-combiner, and fixes many bugs, among others in pedal brackets and finger positioning. More information in the Veranderingen. Oude downloads

January 21, 2004

LilyPond 2.1.14 has the first release of the new part combiner. If you have scores that use part-combining, please consider giving it a test-run. In addition many bugs relating to mixed staff sizes have been fixed. More information in the Veranderingen. Oude downloads

January 20, 2004

The lilypond.org domain has been moved to a new server. This will result in better connectivity and more bandwidth. Due to security concerns, the new server does not offer FTP access, but only HTTP downloads.

January 20, 2004

LilyPond 2.1.13 fixes a small but nasty bug in side-positioning placement, and some bugs in tuplet, tie and accidental formatting. This release contains rudimentary work on a new part-combiner. Oude downloads

January 19, 2004

LilyPond 2.1.12 fixes many bugs and improves formatting of ottava brackets. More information in the Veranderingen. Oude downloads

January 18, 2004

LilyPond 2.1.11 is now also available for Windows! For downloading, go here.

January 17, 2004

In 2.1.11, the mechanism for setting staff size and page is much simplified. In addition there are improvements in the notehead shape, and there is balloon help! More information in the Veranderingen. Oude downloads

January 16, 2004

LilyPond 2.1.10 has a load of bugfixes and a shorter syntax for octave checks. More information in the Veranderingen. Oude downloads

January 13, 2004

LilyPond 2.1.9 has a new mechanism for adding lyrics to melodies. It is now possible to have different melismatic variations for each stanza. More information in the Veranderingen. Oude downloads

January 9, 2004

LilyPond 2.1.8 has an important new feature: it is now possible to use \property to tune the appearance of spanning objects like StaffSymbol and SystemStartBrace. In addition, contexts may be modified with \remove and \consists for individual music expressions. More information in the Veranderingen. Oude downloads

January 7, 2004

An update to the stable branch, version 2.0.2, was released today. It contains a couple of minor bugfixes. Oude downloads

January 6, 2004

LilyPond 2.1.7 continues to improve the layout of the Schubert test piece; this release focuses on dot placement and multi measure rests centering. More information in the Veranderingen and download here.

January 4, 2004

LilyPond 2.1.6 continues to improve the layout of lyrics. More information in the release notes and download here.

January 2, 2004

In LilyPond 2.1.5, the lyric alignment is completely revamped, and now matches my Edition Peters version of the Schubert song Sängers Morgen. More information in the Veranderingen and download here.

December 30, 2003

LilyPond 2.1.4 is released. Font shapes and line thickness are now truly different for different staff sizes, thus lending an engraved look to scores printed in smaller type too. See the Veranderingen and download here.

December 23, 2003

LilyPond 2.1.3 released. Interpreting and formatting is now done while parsing the file. This allows for Scheme manipulation of music, and could be used to implement experimental MusicXML output (volunteers to implement this are welcome!) See the Veranderingen and download here.

December 17, 2003

LilyPond 2.1.2 released. This release has a new mechanism for setting font sizes, which combines different font design sizes and continuous font scaling. See the Veranderingen and download here.

December 16, 2003

LilyPond 2.1.1 released. This release wraps together all the small fixes made during Han-Wen’s absence. See the Veranderingen and download here.

October 11, 2003

LilyPond 2.1.0 released. See the Veranderingen and download here.

October 11, 2003

LilyPond 2.0.1 binaries for Mandrake 9.1 available from here thanks to Heikki Junes.

October 9, 2003

LilyPond 2.0.1 binaries for Slackware 9 available from here, thanks to Ricardo Hoffman.

October 5, 2003

LilyPond 2.0.1 binaries are available for Macos X, many thanks to Matthias Neeracher. Oude downloads

October 4, 2003

LilyPond 2.0.1 binaries are available for Windows (Cygwin version 1.5). Oude downloads. Thanks to Bertalan Fodor, our new Cygwin maintainer!

September 29, 2003

LilyPond 2.0.1 is released. It contains minor bugfixes. See the Veranderingen or download here directly.

September 27, 2003

PlanetCCRMA has been updated to include LilyPond 2.0. Go here to download. Thanks to Fernando Pablo Lopez-Lezcano!

September 24, 2003

LilyPond 2.0.0 is released. The focus of this release is cleanups of the syntax: entering music is now much easier and more efficient. Read the announcement here, or go to the download page directly.

September 24, 2003

LilyPond 1.9.10 is released. This is the final LilyPond 2.0 release candidate. Check the Veranderingen and download here.

September 23, 2003

LilyPond 1.9.9 is released. This is the second LilyPond 2.0 prerelease. Check the Veranderingen and download here.

September 19, 2003

LilyPond 1.9.8 is released. This is the first LilyPond 2.0 prerelease. Check the Veranderingen and download here.

September 17, 2003

LilyPond 1.9.7 is released. LilyPond now has support for quarter tone accidentals! Oude downloads

September 16, 2003

LilyPond 1.9.6 is released. It has a lot of minor fixes and updates. Oude downloads

September 10, 2003

LilyPond 1.9.5 is released. With this release, the 1.9 branch is feature complete. After some stabilization and documentation work, 2.0 will be available in a few weeks. Oude downloads

September 9, 2003

LilyPond 1.8.2 is released. This release fixes a couple of minor bugs. Oude downloads

September 7, 2003

LilyPond 1.8 binaries are available for Windows (Cygwin version 1.5). Oude downloads

August 31, 2003

LilyPond 1.9.4 is released. This is an experimental release: read the announcement before trying.

August 31, 2003

LilyPond 1.8 binaries for slackware available. Get them here.

August 31, 2003

LilyPond 1.9.3 is released. This release supports tagging for music version control, and has better fingering placement flexibility. Read the Veranderingen and get it here.

August 28, 2003

LilyPond 1.9.2 is released. Read the Veranderingen and get it here.

August 26, 2003

LilyPond 1.9.1 is released. Read the Veranderingen and get it here.

August 25, 2003

The LilyPond 1.9 development release is available. Read the Veranderingen and get it here.

August 25, 2003

Mandrake 9.1 RPMS available, get them here.

August 21, 2003

LilyPond 1.8.1 was released. Get it here, or read the Veranderingen.

August 18, 2003

PlanetCCRMA (eg. RedHat 8 and 9) has been updated to 1.8. Download here.

August 7, 2003

LilyPond 1.8 is released. Read Veranderingen and get it here.

August 7, 2003

New website went live!

August 6, 2003

Announced new website.

August 1, 2003

LilyPond 1.7.30 released.

July 30, 2003

Website: present treatise about music engraving, music printing software, and LilyPond’s unique faculties.

July 29, 2003

1.7.29 - release candidate 4 has been released. Packages for Red Hat, Debian, Cygwin are available.


Attic

Announcements

Announcements and news by version: v2.16, v2.14, v2.12, v2.10, v2.8, v2.6, v2.4, v2.2, v2.0, v1.2, v1.0, v0.1

Descriptive list of changes by version: v2.16, v2.14, v2.12, v2.10, v2.8, v2.6, v2.4, v2.2, v2.0, v1.8, v1.6, v1.4, v1.2

Thanks

Thanks to developers, contributors, bug hunters and suggestions for v2.16, v2.14, v2.12, v2.10, v2.8, v2.6, v2.4, v2.2, v2.0, v1.8

Changelogs

Developers’ changelogs by version: v2.10, v2.3, v2.1, v1.5 (1), v1.5 (2), v1.4, v1.3, v1.2, v1.1, v1.0, v0.1, v0.0


Inhoudsopgave


No translation available!

This document was generated by gub on April 20, 2014 using texi2html 1.82.

The buttons in the navigation panels have the following meaning:

Button Name Go to From 1.2.3 go to
[]
[ << ] FastBack Beginning of this chapter or previous chapter 1
[]
[Top] Top Cover (top) of document  
[Contents] Contents Table of contents  
[Index] Index Index  
[ ? ] About About (help)  
[]
[ >> ] FastForward Next chapter 2
[]
[]
[ < ] Back Previous section in reading order 1.2.2
[]
[ Up ] Up Up section 1.2
[]
[ > ] Forward Next section in reading order 1.2.4

where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:


Andere talen: English, česky, deutsch, español, français, magyar, italiano, 日本語, 中文.
About automatic language selection.

Validation

Met dank aan webdev.nl voor het hosten van lilypond.org. Valid HTML 4.01 Transitional