| [Anfang] | [Inhalt] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
LilyPond ist ein Notensatzsystem. Das erklärte Ziel ist es, Notendruck in bestmöglicher Qualität zu erstellen. Mit dem Programm wird es möglich, die Ästhetik handgestochenen traditionellen Notensatzes mit computergesetzten Noten zu erreichen. LilyPond ist Freie Software und Teil des GNU-Projekts.
Lesen Sie mehr in der Einleitung!
LilyPond ist ein sehr mächtiges und flexibles Werkzeug, das Notensatz unterschiedlichster Art handhaben kann: zum Beispiel klassische Musik (wie in diesem Beispiel von J. S. Bach), komplexe Notation, Alte Musik, moderne Musik, Tabulatur, Vokalmusik, Popmusik, Unterrichtsmaterialien, große Orchesterpartituren, individuelle Lösungen, und sogar Schenker-Graphen.
Sehen Sie sich unsere Beispiele an und lassen sich inspirieren!
New Italian mailing list - June 22, 2020
LilyPond 2.21.2 released - June 20, 2020
LilyPond 2.20.0 released - March 1, 2020
@ref{News, Weitere Neuigkeiten...}
| Einleitung | Hier beginnen, um Noten zu setzen. | |
| Download | LilyPond Herunterladen. | |
| Handbücher | Lesen der Handbücher. | |
| Gemeinschaft | Kontakt mit anderen Benutzern aufnehmen. |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Introduction
LilyPond entstand, als zwei Musiker über das tote und unbeseelte Aussehen von computererstellten Notendrucken hinausgehen wollten. Musiker wollen schöne Noten lesen, warum also sollten Programmierer kein Programm schreiben können, das schönere Orchesterstimmen setzen kann?
Das Resultat ist ein Programm, das schönen Notensatz erzeugt und dabei der Tradition und dem ganzen Erfahrungsschatz des klassischen Notensatzes folgt. Es kümmert sich programmatisch um alle Feinheiten des Layouts, damit Komponisten, Setzer und Verleger sich auf die Musik konzentrieren können. Musiker sollen sich auf das Spielen und nicht das Lesen der Musik konzentrieren.
| Eigenschaften | What can LilyPond do? | |
| Beispiele | I want to see some music! | |
| Freiheit | Freedom and the GPL. | |
| Hintergrund | Computational aesthetics. | |
| Produktionen | Real-life use of LilyPond. | |
| Rezensionen | What do people say about it? | |
| Texteingabe | You write music as text?! | |
| Leichteres Editieren | Andere Wege, mit LilyPond zu arbeiten. |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Features
Durch die Benutzung von LilyPond erhalten Sie eleganten Notensatz, der leicht zu lesen ist. Die Entwicklergemeinschaft des Programmes hat tausende von Stunden damit verbracht, ein sehr mächtiges Notensatzprogramm zu entwickeln, dass automatisch schönen Notensatz ausgibt. Alle stilistischen Einstellungen, Schriftartendesign und Algorithmen von LilyPond wurden von den besten handgestochenen Notenbeispielen inspiriert. Die Ausgabe von LilyPond hat das gleiche kraftvolle, ausbalancierte und elegante Aussehen wie die besten gestochenen klassischen Partituren. Dazu mehr in unserem Aufsatz.
LilyPond verarbeitet Texteingaben, die alle Informationen bzgl. des Inhalts ihrer Partitur enthalten und kann leicht durch Menschen oder andere Programme gelesen werden. Es gibt keine in irgendwelchen Menus versteckten Eigenschaften und kein binäres Dateiformat.
Weitere Informationen zu diesem Konzept unter Texteingabe.
Wenn Sie irgendwelche Layoutänderungen vornehmen, so sind diese Optimierungen für jeden in der Eingabedatei sichtbar und damit sind diese Anpassungen jederzeit nachvollziehbar. Versehentlich eingefügte Fehler können so leicht rückgängig gemacht werden, ohne dabei auf die Gnade einer Undo Funktion angewiesen zu sein.
Textdateien sind in Bezug auf Datenverfälschung ausgesprochen robust. Dazu sind sie direkt lesbar und daher jederzeit verständlich, auch ohne die Verwendung des Programms, mit dem sie mal erzeugt wurden.
Textdateien eignen sich hervorragend zur Verwaltung durch ein Versionsmanagement System. Machen Sie das und erfahren unendliches und selektives Undo/Redo und erhalten die vollständige Änderungshistorie ihrer Werke. Versionskontrolle erleichtert dazu neue (kollaborative) Arbeitsweisen.
Verbringen Sie weniger Zeit damit, den Notensatz nachträglich zu optimieren; LilyPond formatiert die Noten von Anfang an richtig. Die Platzaufteilung und die richtigen Zeilen- und Seitenumbrüche werden von selber errechnet, um ein dichtes und gleichmäßiges Notenbild zu erzeugen. Zusammenstöße zwischen Gesangstext, Noten und Akkorden werden aufgelöst und alle Bögen sind automatisch richtig gekrümmt!
Sie können Notenfragmente in einen Text einfügen, ohne Bilder auszuschneiden und einzufügen. Mit LilyPond lassen sich Noten in LaTeX oder HTML nahtlos einfügen und mit OOoLilypond auch in OpenOffice.org und LibreOffice Dokumente integrieren. Es gibt auch Plugins, mit denen LilyPond Code für verschiedene Blogs und Wikis ermöglicht wird, sodass auch eine Zusammenarbeit online möglich wird.
Text-basierte Eingabe ermöglicht das Schreiben von Partituren auch für Leute mit schweren physischen Behinderungen. Benutzer mit motorischen Behinderungen, die Tastatur oder Maus nicht benutzen können, können mit einem Spracherkennungsprogramm LilyPond Dateien bearbeiten. Sogar vollkommen blinde Benutzer können mit Screenreader LilyPond-Dateien erstellen – vollkommen unmöglich mit graphisch-basierten Notationsprogrammen.
Diverse Entwickler, selbst aktive LilyPond Anwender, haben spezielle Werkzeuge entwickelt um das Editieren von LilyPond Dateien schneller und effizienter zu gestalten; Sie sind nicht auf ein bestimmter Benutzerinterface festgelegt sondern können aus einer Vielzahl unterschiedlicher Werkzeuge wählen. So können sie daheim einen LilyPond Editor mit allem drum und dran verwenden und unterwegs den Minieditor ihres Mobiltelefons. Einige Beispiele finden Sie unter Leichteres Editieren.
Alle Layout Einstellungen an ihre persönlichen typographischen Vorstellungen angepasst werden. Sie können sehr einfach Formatvorlagen schreiben, die buchstäblich jede von LilyPond’s Voreinstellungen verändern. So erstellte Formatvorlagen sind ihrerseits wieder Textdateien und können jeweils in einer eigenen Datei abgelegt werden. Das ermöglicht ein extrem einfaches Wechseln zwischen vollkommen unterschiedlichem Notensatz einfach durch Austausch dieser Formatvorlagen. Sie möchten die Partitur auf A4 Papier drucken sowie die Noten mit einem Beamer ein System pro Seite projezieren? LilyPond’s Layout Engine erzeugt beides aus ein und derselben Eingabedatei.
Wenn das noch nicht reichen sollte, dann gibt es immer noch die eingebaute Skriptsprache Scheme. Mit ihr kann auf LilyPond’s Layout Engine in exakt der gleichen Weise zugegriffen werden, wie LilyPond es intern selbst tut. Es ist damit ein extrem mächtiges Werkzeug. Einstellungen, Variablen und Funktionen sind alle im umfangreichen Programm Referenz Handbuch dokumentiert.
LilyPond Eingabedateien können von externen Programmen oder Skripten editiert oder sogar in Gänze erzeugt werden. Das kann z.B. für algorithmisches Komponieren genutzt werden. Oder Sie Verarbeiten den musikalischen Inhalt zu Analysezwecke oder verwalten musikalische Fragmente in einer Datenbank. Die Möglichkeiten sind nur durch ihre Phantasie begrenzt.
LilyPond is kein monolithisches GUI Programm sondern ein Kommandozeilen Progrmm. Daher kann es auch von anderen Programmen verwendet werden. So kann z.B. eine Webanwendung mit LilyPond’s Notensatzfähikeiten erweitert werden. Tatsächlich existieren verschiedene Online Werkzeuge, die LiylPond verwenden.
LilyPond gibt es für alle verbreiteten Betriebssysteme: GNU/Linux, MacOS X und Windows. LilyPond hat eine ausführliche Dokumentation und hunderte von Beispieldateien. Es gibt eine aktive Benutzergemeinschaft, die Fragen auf der LilyPond-Mailliste und in einem deutschsprachigen Forum beantwortet, während das Entwicklungsteam es ermöglicht, dass Probleme schnell gelöst werden.
LilyPond kann ohne jede Bezahlung heruntergeladen werden! Wirklich, es ist vollkommen frei! Holen Sie es sich von der Download-Seite.
Es handelt sich um Freie Software, welche zusammen mit dem Quellcode zur Verfügung gestellt wird – mit der Erlaubnis, zu verändern und zu kopieren. Stören Sie sich an einem Fehler oder brauchen Sie dringend eine neue Funktion? Schreiben Sie sie einfach selber, oder bezahlen Sie jemanden, der es für Sie tut.
Sie sind noch nicht überzeugt? Dann schauen Sie sich einige konkrete Beispiele an. Wenn Sie sich bereits entschlossen haben, LilyPond auszuprobieren, lesen Sie zuerst über unsere Texteingabe.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Examples
LilyPond ist ein sehr mächtiges und flexibles Werkzeug, das Notensatz unterschiedlichster Art handhaben kann. Sehen Sie sich unsere Beispiele an und lassen Sie sich inspirieren!
Dieses Orgelpräludium von J. S. Bach ist ein recht typisches Notensatzprojekt mit LilyPond.
(Klick zum Vergrößern)
Dieses Beispiel aus Goyescas von Enrique Granados zeigt einige der fortgeschrittenen Notensatzfunktionen, unter Anderem Balken zwischen Notenzeilen, Hälse über die Notenzeilen hinweg und Stimmfolgestriche.
(Klick zum Vergrößern)
LilyPond hat Unterstützung für verschiedene Notationsarten der Alten Musik, wie etwa dieser Abschnitt eines Gregorianischen Chorals.
(Klick zum Vergrößern)
Zeitgenössische Komponisten werden feststellen, dass LilyPond sich sehr gut dazu eignet, außergewöhnliche Notation darzustellen. Hier ein Ausschnitt aus Čáry von Trevor Bača für Bassflöte Solo.
(Klick zum Vergrößern)
Verschiedenes Aufführungsmaterial kann aus dem selben Quellcode erstellt werden. Hier ein Ausschnitt aus Händels Giulio Cesare, gesetzt von Nicolas Sceaux, als Partitur, Klavierauszug und eine Geigenstimme.
(Klick zum Vergrößern)
(Klick zum Vergrößern)
(Klick zum Vergrößern)
LilyPond unterstützt Tabulatur-Notation, die an ein beliebiges Instrument angepasst werden kann, dass Tabulatur-Notation einsetzt. Das Tabulatur-System wird automatisch anhand der Noten erstellt, die man für das fünflinige Notensystem notiert hat.
(Klick zum Vergrößern)
Das Standardnotenbild kann sehr stark verändert werden. Hier eine eindrucksvolle Schenker-Analyse, von Kris Schaffer mit LilyPond erstellt für einen Artikel im Linux Journal. Die Farben wurden zur Verdeutlichung hinzugefügt.
(Klick zum Vergrößern)
Ein kurzer Auszug aus Stockhausen’s Klavierstück II zeigt die Fähigkeiten von LilyPond eine individuelle Ausgabe zu erzeugen.
(Klick zum Vergrößern)
LilyPond eignet sich hervorragend, um Vokalmusik aller Arten zu notieren, von Hymnen bis zu einer Oper. Hier eine mittelalterliche Motette mit geringfügig speziellen Anforderungen. Die Tenorstimme ist in einer anderen Taktart als die anderen Stimmen geschrieben, wird aber an den anderen Stimmen ausgerichtet, als ob sie die gleiche Taktart hätte. LilyPond kann damit sehr elegant umgehen. Beachten Sie auch die Incipite mit Schlüsseln im Vaticana-Stil, durchgestrichene Notenhälse für plicierte Noten und Ligaturklammern über bestimmten Notengruppen.
(Klick zum Vergrößern)
LilyPond eignet sich perfekt für eine Anwendung in der Musikerziehung. Hier ein Beispiel einer einfachen Kontrapunktaufgabe.
(Klick zum Vergrößern)
Es ist einfach, ein Liedblatt mit Melodie, Text und Akkorden sowie Griffsymbolen zu erstellen. In diesem Beispiel sind einige der vordefinierten Griffdiagramme eingesetzt, aber sie können vollständig angepasst werden, um fast jeder Situation gerecht zu werden.
(Klick zum Vergrößern)
LilyPond eignet sich großartig für große Projekte wie Opern oder Werke für großes Symphonieorchester. Zusätzlich ermöglicht die texbasierte Eingabe größere Barrierefreiheit – das folgende Beispiel wurde von Hu Haipeng, einem blinden Komponisten, zur Verfügung gestellt.
(Klick zum Vergrößern)
Noch immer nicht überzeugt? LilyPond ist Open Source und garantiert Ihnen Freiheit. Wenn Sie sich schon entschlossen haben, LilyPond auszuprobieren, lesen zuerst über unsere Texteingabe.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Freedom
GNU LilyPond wird von einer Gemeinschaft von Enthusiasten geschrieben und unterhalten. Es wird unter der GNU General Public License und der GNU Free Documentation License herausgegeben, sodass jeder die Freiheit hat, Fehler zu verbessern, das Programm zu ändern oder zu erweitern. Es sollte nicht hunderte Euro kosten, ein Programm zum erstellen schönen Notensatzes zu erwerben.
Das wird sich vielleicht für den gelegentlichen Musiker nicht nach einem Vorteil anhören, aber die Möglichkeit, ein Programm zu erweitern kann sich als sehr wertvoll für ernsthafte Komponisten, Notenverlage und Wissenschaftler erweisen.
Die meisten sehen die Entwicklungsarbeit an LilyPond als ein Hobby oder freiwillige Arbeit. Man müsste also eigentlich fragen: „Warum machen Leute etwas freiwillig“?
Noch immer nicht überzeugt? Lesen Sie unseren ausführlichen Aufsatz über unsere Notensatzphilosophie in Hintergrund. Wenn Sie sich schon entschlossen haben, LilyPond auszuprobieren, lesen zuerst über unsere Texteingabe.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Background
Wir haben einen ausführlichen Aufsatz geschrieben, der die Computerästhetik beschreibt: die Kunst, Schönheit mit dem Computer zu erstellen.
Darin beschreiben wir ausführlich unsere grundlegenden Ideen. Wegen seines Umfangs liegt er als eigenständiges ‚Handbuch‘ vor. Wenn Sie ihn jetzt lesen wollen, gehen sie zu Aufsatz. Wenn Sie indessen lediglich an einer kurzen Einführung in LilyPond interessiert sein sollten, dann können sie das auch auf später verschieben.
Noch immer nicht überzeugt? Lesen Sie über einige der @ref{Productions} unserer Benutzer und schauen Sie sich die Noten an. Wenn Sie sich schon entschlossen haben, LilyPond auszuprobieren, lesen zuerst über unsere Texteingabe.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Productions
Hier lesen Sie von Leuten, die LilyPond in ihren realen Produktionen einsetzen, sei es für Aufführungen ihrer Musik oder zur Erzeugung der druckreifen Veröffentlichungen.
LilyPond-Notensatz wurde für verschiedene Aufführungen rund um die Welt eingesetzt. Einige Highlights:
Aurélien hat ebenfalls Der Ring des Nibelungen von Richard Wagner zu einer 100-minütigen Fassung für Kinder. neu orchestriert. Geschrieben für ein Standard Sinfonie Orchester jedoch mit verkleinertem Sängerensemble wurde das Werk vom Radio-Sinfonieorchester Berlin im April 2014 im Atze Musiktheater Berlin aufgeführt. Der Dirigent war Heiko Matthias Förster.
Sollten Sie hier die Erwähnung von concerts or sheet music vermissen, dann teilen Sie uns dies bitte mit indem Sie eine Nachricht an die bug-lilypond Mailingliste schicken. Falls Sie diese Mailingliste noch nicht abonniert haben, können Sie das auf dieser Seite ändern: info page.
Immer noch nicht überzeugt? Lesen Sie einige der Rezensionen unserer Benutzer. Wenn Sie sich schon entschlossen haben, LilyPond auszuprobieren, lesen zuerst über unsere Texteingabe.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Reviews
Linux Magazine publiziert einen Atikel mit dem Titel Projects on the Move. Es es eine Einleitung zu MuseScore, LilyPond and Chordii. Die Authorin Carla Schroder schreibt „LilyPond wird von der Kommandozeile aus gesteuert, aber lassen Sie sich nicht davon abschrecken, dass es keine graphische Oberfläche gibt: LilyPond ist benutzerfreundlich und leicht zu erlernen“ und zeigt einige praktische Beispiele.
Peter Kirn publiziert auf der Create Digital Music-Webseite einen LilyPond-Test. Er nimmt einen gerechten Standpunkt in Bezug auf die Benutzbarkeit ein, lobt die hohe Qualität des LilyPond-Notensatzes und fordert dazu aus, das Programm einmal auszuprobieren.
Die deutsche LinuxUser-Zeitschrift schrieb einen Artikel über LilyPond.
Ann Drinan präsentiert auf der Polyphonic.org-Webseite Kommentare von zwei Orchsterbibliothekaren, die sich über die Benutzung von Software zur Unterhaltung ihrer Bibliotheken unterhalten.
In einem Artikel in der Jahreszeitschrift der National Conservatory Parent Association erklärt der französischer Komponist und LilyPond-Mitarbeiter Valentin Villenave wie freie Lizenzen und insbesondere mit LilyPond gesetzte Partituren dazu beitragen, dass notierte Musik allen zugänglich gemacht wird.
In Artikeln auf seiner Homepage vergleicht Andrew Hawryluk Finale und LilyPond generell und ermittelt detailliert die Notensatzfähigkeiten beider Programme. Der zweite Artikel ist eine informative Analyse des Notensatzes von Rachmaninoffs Klavierprelude 6, mit einem Vergleich einer handgestochenen Edition.
DistroWatch erteilt LilyPond einen Preis und schreibt writes „Ladies and Gentleman, we are pleased to announce that, based on readers’ requests, the DistroWatch May 2006 donation has been awarded to LilyPond (€ 190.00) and Lua (US$250.00).“
Linux Journal veröffentlicht einen Artikel unter dem Titel Make Stunning Schenker Graphs with GNU LilyPond. Es handelt sich um einen tiefgehenden, aber sehr praktischen Artikel mit gestochen scharfen LilyPond-Graphiken. Der Autor Kris Shaffer merkt an: »GNU LilyPond erstellt schöne Graphik, die kommerzielle Alternativen als zweite Wahl erscheinen lassen.«
Die belgische Zeitung De Standaard untersucht, was die Autoren von Freier Software antreibt in dem Artikel Delen van KENNIS zonder WINSTBEJAG (Non-profit-Teilen von Wissen) in ihrer ‘DS2 bijlage’. LilyPond wird als Beispiel benutzt und der Artikel ist unterteilt durch Auszüge aus einem E-Mail-Interview mit Jan Nieuwenhuizen. Hiermit erscheint LilyPond gleichzeitig das erste Mal in der großen gedruckten Presse.
Ein französischer Artikel über LilyPond Version 2.6 erscheint auf linuxfr.org.
Die Redakteure von Computer!Totaal, einer holländischen Computerzeitschrift, beschreiben LilyPond in der Ausgabe Oktober 2004 als: „Wunderbare freie (Open Source) Software […] Die Partituren von LilyPond sind ausnahmslos schön […] ein sehr mächtiges System das fast alles tun kann.“
Dave Phillips schrieb einen Einleitungsartikel für das Linux Journal: At the sounding edge: LilyPond, Teil eins und zwei.
Chris Cannam interviewte Han-Wen Nienhuys und Jan Nieuwenhuizen auf linuxmusician.com (ursprüngliche Seite funktioniert nicht mehr). Das Interview wurde auch in einer slashdot Story besprochen.
Der Jazz-Sänger Gail Selkirk schreibt über Diving into LilyPond. „… man kann Liedblätter oder volle Orchsterpartituren erstellen, und das Ergebnis kann einen erstaunen.“ Computer Music Special, Nummer CMS06.
„… Ich habe einige Zugabestücke für Solo-Cello geschrieben und mit LilyPond gedruckt. Sie sollen bei Schirmer herausgegeben werden. Ich bin mir sicher, dass ihre eigene Version nicht halb so scharf gestochen ist wie meine!“
„Auch wenn ich [LilyPond] noch nicht sehr gut kenne, bin ich schon außerordentlich beeindruckt. Ich habe das Programm benutzt, um eine Motette von Josquin Desprez in Mensuralnotation zu notieren. Es steht außer Frage, dass LilyPond in der Geschwindigkeit, Einfachheit in der Benutzung und Notensatz alle anderen Notationsprogramme leicht überholt.“
„[Nach der ersten Orchesterprobe] wurde die Qualität meiner Notenblätter immer wieder gelobt. Und das, obwohl ich keine der vielen Möglichkeiten in Anspruch genommen hatte, den Satz zu verbessern. Was ich dem Orchester ausgeteilt habe, war im Grunde die rohe, unveränderte LilyPond-Version.“
„Anerkennung und Dank an das Entwicklungsteam für ihre unglaubliche Arbeit. Ich habe noch nie etwas gesehen, das dem Satz nahekommt, den ich mit LilyPond erhalte. Ich bin vollkommen überzeugt, dass meine Publikationsanforderungen über alle Erwartungen erfüllt werden, da ich dieses Programm verwenden kann. […] sozusagen unveränderter Notensatz von LilyPond […] sieht besser aus als alle „professionellen“ Publikationen der letzten Zeit, mit denen ich ihn verglichen habe (so ungefähr alle Warner Bros.-Noten und sogar viele der „traditionellen Notenhäuser“). […] “
„Das sollen erstmal Finale/Sibelius/Igor/usw. erreichen!!!!“
„LilyPond ist offensichtlich der Super-Gorilla [des Notensatzes].“
„Die Art, in der die Noten mit LilyPond eingegeben werden, lässt mich musikalischer denken – es gab Zeiten, wenn ich vergeblich versucht habe, LilyPond zu erklären, wie etwas in Noten gesetzt werden soll, nur um festzustellen, dass, auch wenn ich es genauso hinkriegen würde, wie der Komponist es wollte, die Noten trotzdem sehr unklar zum Lesen sein würden. LilyPond macht es für mich sehr viel einfacherer, in meiner Doppelrolle als Editor und Notensetzer zu arbeiten.“
„Ich habe LilyPond ausschließlich für meine startende Notendruckfirma benutzt. So gut wie ohne Ausnahme waren alle Komponisten hingerissen von der Qualität des Notensatzes, wenn ich ihnen die Korrekturfahnen ihrer Musik gezeigt habe. Ich verdiene selber auch einen Teil dieses Lobes, denn ich habe viel Zeit damit verbracht, die Ausgabe zu verändern, insbesondere die Bindebögen von Akkorden – aber LilyPond gibt einen wunderbaren Punkt zum Beginnen, eine sehr intuitive Schnittstelle und die Möglichkeit, absolut alles zu verändern, wenn ich mir nur die Zeit nehme. Ich bin überzeugt, dass kein kommerzielles Produkt dem auch nur nahe kommen kann.“
„Ich finde LilyPond einfach toll […] Je mehr ich darüber lerne, desto mehr mag ich es!“
„Ich bin total beeindruckt von LilyPond […]“
„DAS IST DAS BESTE PROGRAMM ALLER ZEITEN!!!“
„Vielen, vielen Dank an euch alle für die harte Arbeit und die Hingabe!“
„Ich hatte so eine Hassliebe zu ihm entwickelt. Liebe, weil das erste Notenblatt, das ich gesehen hatte, so gut aussah. Die Beschreibung lügt, wenn es um die Schönheit von LilyPond geht – das ist viel zu bescheiden! […] da LilyPond immer besser wird und ich mich mehr damit auseinander setze, wie Sachen in Scheme gemacht werden, habe ich viel weniger Frustrationen. Auf jeden Fall wollte ich sagen: Danke, dass ihr LilyPond anbietet, es ist wirklich toll!“
„Überhaupt macht LilyPond saubere Arbeit!“
„Ich finde, [LilyPond ist] ein außerordentliches Programm, und es erreicht wunderschöne Ergebnisse. Als ich im letzten Jahr ein Interview darüber gelesen habe, habe ich verschiedenen Freunden über sein Potential gepredigt.“
und Autor des Expressive Notation Package (ENP)
„Ich habe eine große Achtung vor LilyPond und denen, die es geschrieben haben, denn ich weiß aus eigener Erfarhung, wie schwierig solch ein Programm sein kann.“
professioneller Notensetzer und lange Zeit Score-Benutzer
„Den allergrößten Dank an alle, die zu diesem Projekt beitragen. Ich habe SCORE für einen großen Musikverlag in den 90er Jahren sehr intensiv benutzt, aber jetzt sehe ich, dass LilyPond es mir endlich ermöglicht, genau das Aussehen des Notendrucks zu erreichen, das ich will, besonders wenn es sich nicht um "Standardlösungen" handelt.“
Sollten Sie hier die Erwähnung von news articles or testimonals vermissen, dann teilen Sie uns dies bitte mit indem Sie eine Nachricht an die bug-lilypond Mailingliste schicken. Falls Sie diese Mailingliste noch nicht abonniert haben, können Sie das auf dieser Seite ändern: info page.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Text input
(Klick zum Vergrößern)
LilyPond ist ein kompiliertes System: es wird über eine Text-Datei gestartet, die die Noten beschreibt. Die resultierende Ausgabe wird am Bildschirm betrachtet oder ausgedruckt. In einer bestimmten Beziehung ist LilyPond eher eine Programmsprache als ein graphisches Notensatzprogramm.
Man schreibt die Noten nicht, indem man Notensymbole von einer graphischen Leiste zieht und auf einem sich dynamisch immer wieder erneuernden Notensystem platziert. Anstatt dessen schreibt man Text. Dieser Text wird von LilyPond interpretiert (oder „kompiliert“) und dabei schön aussehender Notensatz produziert.
Leute, die an das graphische Notensetzen gewöhnt sind, können eine Weile brauchen, um die neue Arbeitsweise zu lernen, aber das Resultat macht den Aufwand wett.
Achtung: Wir zeigen einen kurzen Überblick über unsere Texteingabe – es ist nicht so kompliziert, wie es sich anhört. Machen Sie sich keine Sorge, wenn Sie nicht jedes Detail der Beispiele verstehen. In unserer Dokumentation für Anfänger werden alle Einzelheiten sehr viel ausführlicher behandelt.
Noten werden durch Buchstaben und Zahlen kodiert. Besondere Kommandos werden mit einem Backslash eingegeben.
Versetzungszeichen werden durch verschiedene Endungen hinzugefügt: -is
nach der Note setzt ein Kreuz, -es dagegen ein b (– das sind die deutschen
Endungen, Endungen in anderen Sprachen sind auch möglich). LilyPond entscheidet selber, wo
es die Versetzungszeichen platziert.
Akkorde und Liedtext können einfach zu einem Lead Sheet kombiniert werden.
Die Eingabedatei enthält die Noten eines Stückes. Partitur und Stimmen können aus einer einzigen Eingabe-Datei erstellt werden. Wenn man eine Note verändert, findet sich die Veränderung also gleichzeitig in der Stimme und der Partitur wieder. Damit die Noten mehrfach verwendet werden, sollten sie einer Variablen zugewiesen werden:
Mit dieser Variable kann dann eine Einzelstimme erstellt werden (hier transponiert, die Pausen sind zusammengezogen):
Die gleiche Variable wird dann in der Partitur benutzt (hier in der Originaltonhöhe):
Es ist uns klar, dass diese Art, Noten zu schreiben, vielen Benutzern seltsam vorkommt. Aus diesem Grund haben wir eine ausführliche Anleitung verfasst, die neuen Benutzern helfen soll. Man sollte mit der Einführung beginnen. Das Handbuch zum Lernen funktioniert als Einführung und Beginn für das Arbeiten mit LilyPond; hier werden viele Fragen beantwortet, bevor man sie überhaupt stellen konnte!
Bisweilen sind Meulinge von manchen Verhaltensweisen von LilyPond unnötig verwirrt. Bitte lesen Sie dieses Handbuch bevor Sie anzweifeln, daß LilyPond fehlerfrei arbeitet.
Weitere Information findet sich unter Handbücher
Der LilyPond Anwender Ben Lemon hat eine ganze Reihe von Video Tutorials in seinem Blog hinterlegt, die sich speziell an Neulinge wenden.
(Klick zum Vergrößern)
LilyPond kümmert sich vor allem darum, Noten in bester Qualität zu setzen – das Programmieren einer graphischen Benutzeroberfläche (GUI) würde uns nur von dieser Aufgabe ablenken. Es gibt dennoch andere Projekte, deren Ziel es ist, LilyPond-Dateien zu erstellen.
Einige Editionsumgebungen beinhalten Syntaxhervorhebung, automatische Vervollständigung und vorgefertigte Vorlagen. Andere Programme stellen tatsächliche eine GUI zur Verfügung, mit der man graphisch eine Partitur editieren kann. Mehr Information finden Sie unter Leichteres Editieren.
Sie sind jetzt bereit, LilyPond herunterzuladen. Sind Sie immer noch nicht überzeugt? Lesen Sie Leichteres Editieren.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Easier editing
(Klick zum Vergrößern)
Frescobaldi ist ein leichtgewichtiger (im Sinne von ‚installiert nur wenig zusätzliche Software‘), aber sehr mächtiger LilyPond Musik- und Texteditor mit vielen für die Arbeit mit LilyPond nützlichen Fähigkeiten. Herausragend ist die beidseitige Verknüpfung zwischen dem LilyPond Code und der dargestellten Musik durch ‚point-and-click‘ mit der Maus. Ferner gibt es Partiturassistenten, eingebautes LilyPond Handbuch, Syntaxhighlighting sowie automatische Befehlsvervollständigung. Frescobaldi wurde in Python geschrieben, verwendet PyQt4 für das GUI und ist auf allen gängigen Betriebssystemen verfügbar (GNU/Linux, Mac OS X and Windows).
(Klick zum Vergrößern)
Denemo ist ein graphischer Editor, welcher LilyPond-Dateien produzieren kann und auch Audioplayback erlaubt. Hiermit kann die LilyPond-Datei parallel zum graphischen Notenbild betrachtet werden. Zusätzliche Veränderungen und Anpassungen können an die Objekte angehängt werden – sie werden mit der Denemo-Datei gespeichert, sodass der Benutzer graphisch weiterarbeiten kann.
Wenn man den Cursor im LilyPond-Text bewegt, wird er auch im Notenbild verschoben, und Syntaxfeher in LilyPond-Anpassungen werden in Textansicht markiert, wenn man von dort aus druckt.
Ein webbasierter LilyPond Editor, in dem man die Noten direkt online setzen kann, ohne LilyPond vorher installieren zu müssen.
Mit tunefl können Sie kleine Partituren direkt online setzen, ohne LilyPond lokal installieren zu müssen. Es unterstützt alle Fähigkeiten des Programms über ein bequemes Webinterface.
Elysium ist eine LilyPond IDE für Eclipse mit integrierter paralleler Sicht auf Quelle und erzeugte Noten. Ferner verfügt es über schnelles visuelle und akkustische Rückmeldung, ohne daß dazu der Kontext gewechselt werden müßte. Schließlich verfügt es über eine ganze Reihe von Assistenten, die von vorgefertigten Templates getrieben werden.
http://www.gnu.org/software/emacs/ Emacs ist ein Texteditor mit sprachensensitiven Eigenschaften für sehr viele Computersprachen. Emacs ist ein sehr stark erweiterbarer Editor, welcher auch als Integrierte Entwicklungsumgebung benutzt werden kann. Es gibt einen „lilypond“-Modus, der die Sprachdefinitionen für das Arbeiten mit LilyPond-Dateien zur Verfügung stellt. Einer unserer Entwickler hat auch einen Hauptmodus für Emacs, lyqi geschrieben.
Wenn Sie bisher nicht bereits mit Emacs vertraut sind, dann bevorzugen sie möglicherweise einen anderen Editor um LilyPond Dateien zu schreiben.
Nähere Informationen zum Einrichten von Emacs finden Sie unter (usage-big-page)Unterstützung von Texteditoren in Abschnitt ‘Unterstützung von Texteditoren’ in Anwendungsbenutzung.
http://www.vim.org
Vim ist ein minimaler Texteditor und eine Erweiterung des älteren
Unix-Editors vi. Er ist auch erweiterbar und konfigurierbar.
Wenn Sie bisher nicht bereits mit Vim vertraut sind, dann bevorzugen sie möglicherweise einen anderen Editor um LilyPond Dateien zu schreiben.
Nähere Informationen zum Einrichten von Vim finden SIe unter (usage-big-page)Unterstützung von Texteditoren in Abschnitt ‘Unterstützung von Texteditoren’ in Anwendungsbenutzung.
http://www.uoregon.edu/~koch/texshop
Der TeXShop-Editor für MacOS X kann erweitert werden, sodass
er LilyPond, lilypond-book und convert-ly
vom Editor aus ausführen kann. Hierzu wird eine Erweiterung
eingesetzt, die man hier erhält:
http://users.dimi.uniud.it/~nicola.vitacolonna/home/content/lilypond-scripts. |
.bww oder .bmw Datei nach LilyPond zu konvertieren. Auch wenn
nicht jeder Schnörkel korrekt konvertiert wird (das gilt besonders für solche
mit ‚piobaireachd‘ [was immer das ist – Anm. des Übersetzers]), jedoch werden
diese zumindest aufgeführt.
Sind Sie jetzt bereit, LilyPond herunterzuladen.
Sie sind noch immer nicht überzeugt? Viele Komponisten, Musiker und Dirigenten haben gelernt, wie man Noten in unserem Eingabeformat schreibt. Erfahrene Benutzer haben sogar berichtet, dass sie eine volle Partitur in LilyPond schneller notieren können als mit Klaviertastatur oder Maus plus GUI! Vielleicht wollen Sie noch einmal schauen, welche Eigenschaften, Beispiele oder Freiheit LilyPond ermöglicht oder über die Produktionen und Rezensionen unserer Benutzer lesen. Zusätzlich haben wir unsere Herangehensweise an die Computerästhetik der klassischen Notensatzkunst im unserem Hintergrund erklärt.
Alle Logos und Produktabbildungen werden unter ausdrücklicher Anerkennug des Copyright und Trademark der Rechteinhaber verwendet.
Tux the Linux Penguin was created by lewing@isc.tamu.edu with the Gnu Image Manipulation Program.
The FreeBSD logo is a registered trademark of The FreeBSD Foundation.
The „X image“ is not a registered trademark. It was created by Nihonjoe and CyberSkull, and placed under the GNU Free Documentation License version 1.2 or later. We found the image on this Wikipedia Commons page.
The „four colored rectangles image“ is not a registered trademark. It was created by Rohitbd and placed under the GNU Free Documentation License version 1.2. We found the image on this Wikipedia Commons page.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Download
Achtung: LilyPond ist ein textbasiertes Notationsprogramm, es ähnelt eher einer Programmiersprache als einem graphischen Programm zum Notensatz. Bevor Sie LilyPond herunterladen, lesen Sie bitte über unsere Texteingabe.
Alle Logos und Produktabbildungen werden unter ausdrücklicher Anerkennug des Copyright und Trademark der Rechteinhaber verwendet.
Tux the Linux Penguin was created by lewing@isc.tamu.edu with the Gnu Image Manipulation Program.
The FreeBSD logo is a registered trademark of The FreeBSD Foundation.
The „X image“ is not a registered trademark. It was created by Nihonjoe and CyberSkull, and placed under the GNU Free Documentation License version 1.2 or later. We found the image on this Wikipedia Commons page.
The „four colored rectangles image“ is not a registered trademark. It was created by Rohitbd and placed under the GNU Free Documentation License version 1.2. We found the image on this Wikipedia Commons page.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Unix
Achtung: LilyPond ist ein textbasiertes Notationsprogramm, es ähnelt eher einer Programmiersprache als einem graphischen Programm zum Notensatz. Bevor Sie LilyPond herunterladen, lesen Sie bitte über unsere Texteingabe.
Viele Distributionen enthalten LilyPond in ihrem normalen Packet-System. Oft sind diese Versionen erheblich älter, als die das aktuelle stabile Version. Diese alten Packete sind meist einfacher zu installieren und auch wieder zu entfernen, jedoch empfehlen wir im Falle von veralteten Packeten dringend die Verwendung unserer generischen Packete. Achten sie in dem Falle auch darauf, daß ihr LilyPond Editor die korrekte Version verwendet. Siehe auch Leichteres Editieren.
GNU/Linux x86: LilyPond 2.20.0-1
32bit Systeme.
GNU/Linux 64: LilyPond 2.20.0-1
64bit Systeme.
GNU/Linux PPC: LilyPond 2.20.0-1
FreeBSD i386: LilyPond 2.20.0-1
32bit Systeme.
FreeBSD amd64: LilyPond 2.20.0-1
64bit Systeme.
Auf der Kommandozeile schreiben Sie
cd PFAD-ZUM-DOWNLOADVERZEICHNIS sh lilypond-2.20.0-OS-ART.sh |
Auf der Kommandozeile schreiben Sie
uninstall-lilypond |
Auf der Kommandozeile schreiben Sie
sh lilypond-2.20.0-OS-TYPE.sh --help |
Achtung: Diese Anweisungen gehen davon aus, dass Sie den installierten LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in (web-big-page)Leichteres Editieren in Abschnitt ‘Leichteres Editieren’ in Allgemeine Information beschrieben sind, schauen Sie bitte in der Dokumentation nach, wenn Sie Probleme damit haben, eine Datei zu kompilieren.
Erstellen Sie eine Text-Datei mit dem Namen ‘test.ly’ und geben Sie folgenden Text ein:
\version "2.20.0"
{
c' e' g' e'
}
|
Um die Datei zu kompilieren, geben sie an der Konsole bzw. Kommandozeile
lilypond test.ly |
ein. Sie werden ungefähr folgende Meldungen sehen:
lilypond test.ly GNU LilyPond 2.20.0 »test.ly« wird verarbeitet Analysieren... Interpretation der Musik... Vorverarbeitung der grafischen Elemente... Ideale Seitenanzahl wird gefunden... Musik wird auf eine Seite angepasst... Systeme erstellen... Layout nach »test.ps« ausgeben... Konvertierung nach »test.pdf«... Erfolg: Kompilation erfolgreich beendet |
Als Ergebnis erhalten Sie ein ‘test.pdf’, das Sie mit den Standardprogrammen Ihres Betriebssystemes anschauen können.
Alle Logos und Produktabbildungen werden unter ausdrücklicher Anerkennug des Copyright und Trademark der Rechteinhaber verwendet.
Tux the Linux Penguin was created by lewing@isc.tamu.edu with the Gnu Image Manipulation Program.
The FreeBSD logo is a registered trademark of The FreeBSD Foundation.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
Achtung: LilyPond ist ein textbasiertes Notationsprogramm, es ähnelt eher einer Programmiersprache als einem graphischen Programm zum Notensatz. Bevor Sie LilyPond herunterladen, lesen Sie bitte über unsere Texteingabe.
Mac OS X x86 32-bit: LilyPond 2.20.0-1
Für MacOS X 10.4 oder höher auf Intel-Prozessoren (wenn Sie Zweifel haben,
benutzen Sie diese Version).
Mac OS X PPC: LilyPond 2.20.0-1
Für MacOS X 10.4 oder höher auf G3 und G4 Prozessoren (alte
Apple-Computer).
Doppelklicken Sie die heruntergeladene Datei, dann ziehen Sie es dorthin, wo Sie das Programm speichern wollen.
Entfernen Sie den LilyPond.app-Ordner.
Achtung: Wenn Sie mit der GUI Hinweisen weiter unten zufrieden sind, dann ignorieren Sie bitte diese Anweisungen.
Die einfachste Art, lilypond-Skripte auszuführen ist es, eigene „Hilfsskripte“ zu erstellen.
mkdir -p ~/bin cd ~/bin |
lilypond und
dem Inhalt:
#!/bin/bash exec DIR/LilyPond.app/Contents/Resources/bin/lilypond "$@" |
Achtung: VERZ ist üblicherweise /Applications/
lilypond-book,
convert-ly und andere Skripte, die Sie benutzen wollen,
wobei Sie bin/lilypond durch bin/convert-ly
(oder andere Programmbezeichnungen) ersetzen.
chmod u+x lilypond |
.profile in
Ihrem home-Verzeichnis, sodaß sie beinhaltet:
export PATH=$PATH:~/bin |
Diese Datei sollte mit einer leeren Zeile schließen.
Die Skripte — wie lilypond-book, convert-ly,
abc2ly und auch lilypond selber — sind in
einer .app-Datei für MacOS X enthalten.
Skripte können auch von der Kommandozeile aus aufgerufen werden, indem man sie direkt aufruft:
Pfad/zur/LilyPond.app/Contents/Resources/bin/lilypond |
Das gilt auch für alle anderen Skripte in diesem Verzeichnis, wie
lilypond-book und convert-ly.
Achtung: Diese Anweisungen gehen davon aus, dass Sie die LilyPond-Application benutzen. Wenn Sie eins der Programme benutzen, die in (web-big-page)Leichteres Editieren in Abschnitt ‘Leichteres Editieren’ in Allgemeine Information beschrieben sind, schauen Sie bitte in der Dokumentation nach, wenn Sie Probleme damit haben, eine Datei zu kompilieren.
Wenn Sie das LilyPond.app-Symbol doppelt klicken, öffnet
sich eine Beispiel-Datei.
Wählen Sie aus den Menüs oben links auf Ihrem Bildschirm
File > Save.
Wählen Sie einen Namen für die Datei, etwa ‘test.ly’.
Aus den selben Menüs wählen Sie jetzt Compile > Typeset.
Ein neues Fenster öffnet sich, in dem ein Fortschrittslog der Kompilation der von ihnen gerade gespeicherten Datei gezeigt wird.
Wenn die Kompilation fertig ist, wird ein PDF mit dem gleichen Namen wie das Original erstellt und automatisch mit dem Standard-PDF-Programm geöffnet und angezeigt.
Um neue LilyPond-Dateien zu erstellen beginnen sie mit
File > New
oder File > Open um eine schon existierende Datei zu
öffnen und zu editieren.
Sie müssen alle Änderungen an der Datei zuerst speichern, bevor Sie
wieder Compile > Tyepset wählen. Wenn das PDF nicht
erscheint, schauen Sie im Fortschrittslog nach Fehlern.
Wenn Sie nicht das Standard-PDF-Programm benutzen, das automatisch bei Mac OS X dabei ist, und Sie die PDF-Datei noch von einer vorigen Kompilation geöffnet haben, können weitere Kompilationen fehlschlagen, bis Sie das Original-PDF schließen.
Alle Logos und Produktabbildungen werden unter ausdrücklicher Anerkennug des Copyright und Trademark der Rechteinhaber verwendet.
The „X image“ is not a registered trademark. It was created by Nihonjoe and CyberSkull, and placed under the GNU Free Documentation License version 1.2 or later. We found the image on this Wikipedia Commons page.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
Achtung: LilyPond ist ein textbasiertes Notationsprogramm, es ähnelt eher einer Programmiersprache als einem graphischen Programm zum Notensatz. Bevor Sie LilyPond herunterladen, lesen Sie bitte über unsere Texteingabe.
Windows: LilyPond 2.20.0-1
Für Windows 2000, XP, Vista, Windows 7, 8 und 10.
Um LilyPond zu entfernen, können Sie entweder
Achtung: Wenn Sie mit der GUI Hinweisen weiter unten zufrieden sind, dann ignorieren Sie bitte diese Anweisungen.
Die einfachste Art LilyPond zu benutzen ist, den Installationsordner zur Umgebungsvariable „Path“ hinzuzufügen.
[voreingestellter PATH];VERZ\LilyPond\usr\bin |
Achtung: VERZ ist üblicherweise C:\Program Files.
und klicken Sie auf „OK“ um das Fenster zu schließen.
LilyPond-Programme – wie lilypond, lilypond-book, convert-ly und so weiter – können von der Kommandozeile aus aufgerufen werden:
lilypond test.ly |
Achtung: Diese Anweisungen gehen davon aus, dass Sie den installierten LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in (web-big-page)Leichteres Editieren in Abschnitt ‘Leichteres Editieren’ in Allgemeine Information beschrieben sind, schauen Sie bitte in der Dokumentation nach, wenn Sie Probleme damit haben, eine Datei zu kompilieren.
Wenn sie auf das LilyPond-Symbol auf dem Desktop doppelklicken, öffnet sich ein einfacher Texteditor mit einer Beispieldatei.
Aus dem Menü über der Beispieldatei wählen Sie File > Save as.
Benutzen Sie nicht File > Save für die Beispieldatei,
weil die Datei nicht funktioniert, bis Sie sie mit einem eigenen
Namen gespeichert haben.
Wählen Sie einen Namen für Ihre Datei, etwa ‘test.ly’.
Sie können nach Belieben die Kompilation starten, indem Sie entweder:
Die Datei auf das LilyPond-Symbol ziehen.
Oder Sie klicken mit der rechten Maustaste auf die Datei und wählen
Sie aus dem Menü Open with > LilyPond.
Sie können auch einfach die Datei ‘test.ly’ doppelt anklicken.
Während der Kompilation von ‘test.ly’ öffnet sich ein Kommandofenster sehr schnell und schließt sich wieder. Drei zusätzliche Dateien werden in diesem Schritt erstellt.
Das PDF enthält den Notensatz aus der Datei ‘test.ly’.
Um eine neue Datei zu erstellen, wählen Sie File > New
aus irgendeiner schon erstellten Datei oder File > Open,
um eine Datei zu öffnen und zu bearbeiten, die Sie schon vorher
gespeichert hatten.
Sie müssen jede neue Änderung erst speichern, bevor Sie die Datei kompilieren. Wenn kein PDF erstellt wird, öffnen Sie die Log-Datei und schauen Sie nach Fehlern.
Die Log-Datei wird jedes Mal überschrieben, wenn Sie Ihre LilyPond-Datei kompilieren.
Die PS-Datei wird intern von LilyPond benutzt um das PDF zu erstellen und kann ignoriert werden. Sie wird auch jedes Mal neu überschrieben.
Wenn Sie das PDF in einem PDF-Programm anschauen, müssen Sie es zuerst schließen, bevor Sie eine neue Kompilation durchführen können, denn es kann einen Fehler bei der Erstellung des neuen PDFs geben, wenn das alte noch geöffnet ist.
Alle Logos und Produktabbildungen werden unter ausdrücklicher Anerkennug des Copyright und Trademark der Rechteinhaber verwendet.
The „four colored rectangles image“ is not a registered trademark. It was created by Rohitbd and placed under the GNU Free Documentation License version 1.2. We found the image on this Wikipedia Commons page.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Source
Achtung: LilyPond ist ein textbasiertes Notationsprogramm, es ähnelt eher einer Programmiersprache als einem graphischen Programm zum Notensatz. Bevor Sie LilyPond herunterladen, lesen Sie bitte über unsere Texteingabe.
Achtung: Wir empfehlen nicht, dass Sie versuchen, LilyPond selber aus den Quellen zu kompilieren. Fast alle Benutzer haben mehr Vorteile von der vorkompilierten Version.
Quellen: lilypond-2.20.0.tar.gz
Für ein ausführliche Liste aller Versionen (alt und neu) siehe unsere Download-Seite.
Anweisungen finden sich unter (contributor-big-page)Compiling LilyPond in Abschnitt ‘LilyPond kompilieren’ in Contributor’s Guide.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Old downloads
Achtung: LilyPond ist ein textbasiertes Notationsprogramm, es ähnelt eher einer Programmiersprache als einem graphischen Programm zum Notensatz. Bevor Sie LilyPond herunterladen, lesen Sie bitte über unsere Texteingabe.
Für eine ausführliche Liste aller Versionen (alt und neu) siehe unsere Download-Seite.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof GPL
GNU LilyPond wird unter der GNU General Public License publiziert. Eine Einführung zu der Lizenz und unsere Gründe für diese Wahl finden Sie in Freiheit.
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. https://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
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.
“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.
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.
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.
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.
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.
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:
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.
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:
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.
“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:
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 https://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 https://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 https://www.gnu.org/philosophy/why-not-lgpl.html.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Manuals
Die LilyPond Handbücher liegen generell in drei Formaten vor: geteiltes HTML, großes HTML und
PDF. Geteiltes HTML eignet sich besonders Online gelesen zu werden. Großes HTML (und einige sind
sehr groß) beinhaltet das gesamte Handbuch in einer einzigen Seite. PDF ist zum Download und
dem Offline Lesen vorgesehen. Sie gelangen zu diesen 3 Formaten indem Sie den Links
details of folgen und dann dem Namen des Handbuchs.
| Einführung | ||
| Glossar | ||
| Aufsatz | ||
| Notation | Referenz. | |
| Benutzung | ||
| Schnipsel | ||
| FAQ | ||
| Web | ||
| Änderungen | NEWS. | |
| Erweitern | Programmierung. | |
| Interna | ||
| Übersetzt | ||
| Alles | Alle Handbücher | |
| FDL | Lizenz. |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Learning
Dieses Buch erklärt, wie man beginnen sollte, LilyPond zu erlernen. Hier werden auch einige Schlüsselkonzepte und einfache Begriffe erklärt. Sie sollte diese Kapitel von vorne bis hinten lesen.
Am Ende jeden Abschnitts gibt es einen Absatz Siehe auch, welcher Links in andere Abschnitte enthält. Beim ersten Durchlesen sollten Sie diesen Verlinkungen nicht folgen. Wenn Sie das gesamte Handbuch einmal gelesen haben, werden Sie wahrscheinlich einige Abschnitte noch einmal lesen und dann auch den Links folgen, um weitere Informationen zu erhalten.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Glossary
Hier werden musikalische Fachbegriffe auf Englisch erklärt und Übersetzungen zu einer Reihe von Sprachen gegeben. Wenn Sie sich mit der Terminologie der Musik und Musiknotation nicht auskennen (und vor allem, wenn Sie Englisch nicht fließend sprechen) lohnt es sich sehr, dieses Glossar zu Hilfe zu ziehen.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Essay
Dieses Buch enthält eine kurze Geschichte des Musiknotensatzes und anschließend eine Betrachtung der Notensatztechniken von LilyPond. Ein Vergleich von LilyPond mit anderen Notensatzprogrammen wird auch vorgenommen.
Achtung: Die detailierten typographischen Beispiele lassen sich in der PDF-Version einfacher analysieren, weil sie eine höhere Auflösung hat.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Notation
Dieses Buch erklärt alle Befehle von LilyPond, die Notation erstellen.
Achtung: Die Notationsreferenz geht davon aus, dass der Leser die Grundlagen von LilyPond bereits kennt, wie sie im Handbuch zum Lernen ausgeführt werden. In einigen Fällen sollte die englische Musikterminologie (siehe Glossar) bekannt sein.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Usage
Dieses Buch erklärt, wie die Programme ausgeführt werden, wie man LilyPond-Notation in andere Programme integrieren kann und macht Vorschläge, wie man am besten seine Notationsdateien anlegt. Es wird empfohlen, das Dokument zu lesen, bevor man größere Projekte in Angriff nimmt.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Snippets
Hier werden ausgewählte Schnipsel an LilyPond-Code mit der produzierten Notation gezeigt. Die Schnipsel stammen aus dem LilyPond-Schnipsel-Depot (LSR) und stehen alle unter der Public Domain.
Beachten Sie, dass dieses Dokument keine bestimmte Teilmenge von LSR darstellt. LSR läuft unter der stabilen Version von LilyPond, sodass jedes Schnipsel, das eine neue Eigenschaft von der Entwicklungsversion zeigt, extra hinzugefügt werden muss. Diese Schipsel sind in der Datei ‘Documentation/snippets/new/’ im Quellverzeichnis von LilyPond gespeichert.
Die Schnipsel-Listen für jeden Abschnitt der Notationsreferenz sind auch verlinkt vom Siehe auch Absatz.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof FAQ
LilyPond erfordert es, dass Noten als Text eingegeben werden. Lesen Sie bitte über unsere Texteingabe.
lesen?
Sie müssen das @ref{Learning, Handbuch zum Lernen} lesen. Der Rest der Dokumentation ist zum Nachschlagen gedacht, wenn Sie eine bestimmte Art von Notationszeichen oder -typ brauchen.
denn?
Das müssen Sie selber entscheiden; die Gründe, warum Sie LilyPond anderen Programmen vorziehen können, sind dargestellt in der Einleitung.
Das wird erklärt in (usage-big-page)Fehlersuche in Abschnitt ‘Fehlersuche’ in Anwendungsbenutzung.
Das wird erklärt in (usage-big-page)Warum verändert sich die Syntax? in Abschnitt ‘Warum verändert sich die Syntax?’ in Anwendungsbenutzung.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Web
Dieses Handbuch stellt allgemeine Information zu LilyPond zur Verfügung. Es enthält auch Information über die verschiedenen Gemeinschaftsforen, das Melden von Fehlern und die Mitarbeit am Programm.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Changes
Hier eine Zusammenfassung von wichtigen Veränderungen und neuen Eigenschaften in LilyPond seit der vorigen stabilen Version.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Extending
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Internals
Hierbei handelt es sich um eine Anzahl sehr stark verlinkter Seiten, welche alle klitzekleinen Details von jeder einzigen LilyPond-Klasse, jedem Objekt und jeder Funktion dokumentieren. Das Dokument wird direkt aus den Formatanweisungen des Quellcodes erstellt und ist nur auf Englisch erhältlich.
Fast alle Formatierungsfunktionen, die intern benutzt werden, stehen auch direkt dem Benutzer zur Verfügung. Beispielsweise die meisten Variablen, die Dickewerte, Entfernungen usw. kontrollieren, können in der Eingabedatei verändert werden. Es gibt eine große Anzahl von Formatierungsoptionen und alle sind in diesem Dokument erklärt. Jeder Abschnitt der Notationsreferenz hat einen Siehe auch-Abschnitt, der auf diese Dokumentation verweist.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Translated
Zuletzt aktualisiert am Sun May 24 17:38:33 UTC 2020
| LilyPond Changes | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
740 | David Kastrup
Lukas-Fabian Moser | Michael Gerdau | ja | K/A | vor-GDP |
| LilyPond – \TITLE\
1139 | David Kastrup
Lukas-Fabian Moser | Michael Gerdau | ja | teilweise | vor-GDP |
| Aufsatz über den automatischen Musiksatz | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
92 | Till Paala | ja | teilweise | vor-GDP | |
| LilyPond – \TITLE\
1139 | Till Paala | ja | teilweise | vor-GDP | |
| 1 Notensatz
5315 | Till Paala | ja | teilweise | vor-GDP | |
| 2 Literatur
382 | Till Paala | ja | teilweise | vor-GDP |
| LilyPond erweitern | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
107 | Till Paala | ja | teilweise | vor-GDP | |
| LilyPond – \TITLE\
1139 | Till Paala | ja | teilweise | vor-GDP | |
| 1 Scheme-Tutorium
6331 | Till Paala | teilweise (54 %) | teilweise | vor-GDP | |
| 2 Schnittstellen für Programmierer
5769 | Till Paala | ja | teilweise | vor-GDP |
| LilyPond Handbuch zum Lernen | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
124 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| LilyPond – \TITLE\
1139 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| 1 Tutorium
2536 | Till Paala
Reinhold Kainhofer Michael Gerdau | Hajo Bäß | ja | teilweise | vor-GDP |
| 2 Übliche Notation
4517 | ???
Michael Gerdau | ja | teilweise | vor-GDP | |
| 3 Grundbegriffe
11576 | Till Paala
Reinhold Kainhofer Michael Gerdau | teilweise (96 %) | teilweise | vor-GDP | |
| 4 Die Ausgabe verbessern
16582 | ???
Michael Gerdau | ja | teilweise | vor-GDP | |
| A Vorlagen
1236 | Till Paala
Michael Gerdau | ja | ja | vor-GDP |
| LilyPond Benutzerhandbuch | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
361 | Till Paala | ja | teilweise | vor-GDP | |
| LilyPond – \TITLE\
1139 | Till Paala | ja | teilweise | vor-GDP | |
| 1 Musikalische Notation
91 | Till Paala | ja | ja | vor-GDP | |
| 1.1 Tonhöhen
5513 | Till Paala | ja | teilweise | vor-GDP | |
| 1.2 Rhythmus
7098 | Till Paala | ja | teilweise | vor-GDP | |
| 1.3 Ausdrucksbezeichnungen
1907 | Till Paala | ja | teilweise | vor-GDP | |
| 1.4 Wiederholungszeichen
1310 | Till Paala | ja | teilweise | vor-GDP | |
| 1.5 Gleichzeitig erscheinende Noten
3001 | Till Paala | ja | teilweise | vor-GDP | |
| 1.6 Notation auf Systemen
3017 | Till Paala | ja | teilweise | vor-GDP | |
| 1.7 Anmerkungen
1700 | Till Paala | ja | teilweise | vor-GDP | |
| 1.8 Text
3572 | Till Paala | ja | teilweise | vor-GDP | |
| 2 Spezielle Notation
81 | Till Paala | ja | ja | vor-GDP | |
| 2.1 Notation von Gesang
5174 | Till Paala | ja | teilweise | vor-GDP | |
| 2.2 Tasteninstrumente und andere Instrumente mit mehreren Systemen
903 | Till Paala | ja | teilweise | vor-GDP | |
| 2.3 Bundlose Saiteninstrumente
279 | Till Paala | ja | teilweise | vor-GDP | |
| 2.4 Saiteninstrumente mit Bünden
2930 | Till Paala | ja | teilweise | vor-GDP | |
| 2.5 Schlagzeug
1000 | Till Paala | ja | teilweise | vor-GDP | |
| 2.6 Blasinstrumente
349 | Till Paala | ja | teilweise | vor-GDP | |
| 2.7 Notation von Akkorden
2177 | Till Paala | ja | teilweise | vor-GDP | |
| 2.8 Zeitgenössische Musik
475 | Till Paala | ja | teilweise | vor-GDP | |
| 2.9 Notation von alter Musik
5468 | Till Paala | ja | teilweise | vor-GDP | |
| 2.10 Weltmusik
2004 | Till Paala | ja | teilweise | vor-GDP | |
| 3 Allgemeine Eingabe und Ausgabe
13941 | Till Paala | teilweise (86 %) | teilweise | vor-GDP | |
| 4 Abstände
11050 | Till Paala | ja | teilweise | vor-GDP | |
| 5 Standardeinstellungen verändern
17137 | Till Paala | teilweise (85 %) | teilweise | vor-GDP | |
| A Notationsübersicht
3450 | Till Paala | ja | teilweise | vor-GDP | |
| B Befehlsübersicht
252 | Till Paala | ja | teilweise | vor-GDP |
| GNU LilyPond Programmbenutzung | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
135 | Till Paala | ja | teilweise | vor-GDP | |
| LilyPond – \TITLE\
1139 | Till Paala | ja | teilweise | vor-GDP | |
1 lilypond starten
6877 | Reinhold Kainhofer
Till Paala | Till Paala | teilweise (92 %) | teilweise | vor-GDP |
2 Dateien mit convert-ly aktualisieren
2097 | Till Paala | teilweise (89 %) | teilweise | vor-GDP | |
3 lilypond-book aufrufen
4212 | Reinhold Kainhofer | Till Paala | ja | teilweise | vor-GDP |
| 4 Externe Programme
3051 | Till Paala
Reinhold Kainhofer | teilweise (88 %) | teilweise | vor-GDP | |
| 5 Vorschläge zum Schreiben von LilyPond-Eingabe-Dateien
2793 | Till Paala | ja | teilweise | vor-GDP |
| LilyPond – Notation für Jedermann | Übersetzer | Übersetzungsüberprüfer | Übersetzt | Aktuell | Mehr Information |
|---|---|---|---|---|---|
| Überschriften
752 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| LilyPond – \TITLE\
1139 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| Einleitung
6073 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| Download
1174 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| Handbücher
1279 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP | |
| Gemeinschaft
2359 | Till Paala
Michael Gerdau | ja | teilweise | vor-GDP |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof All
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
Die Dokumentation für GNU LilyPond wird unter der GNU Free Documentation License publiziert. Eine Einführung in diese Lizenz und Gründe für ihre Benutzung finden sich in Freiheit.
Version 1.3, 3 November 2008
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. https://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
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.
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.
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.
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.
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:
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.
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.”
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.
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.
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.
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.
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 https://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.
“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.
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.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Community
| Kontakt | ||
| Minimalbeispiele | ||
| Fehlerberichte | ||
| Helfen Sie uns | ||
| Sponsoren | ||
| Entwicklung | ||
| Google Summer of Code | ||
| Autoren | ||
| Danksagungen | ||
| Veröffentlichungen | ||
| Ältere Neuigkeiten | ||
| Abstellkammer |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Contact
lilypond-user@gnu.orgDiese Mailingliste ist der zentrale Ort, an dem Benutzer diskutieren und einander helfen. Die Sprache der Liste ist Englisch. Zu deutschsprachiger Hilfe, siehe unten.
Achtung: Wenn Sie Fragen stellen (immer auf Englisch) benutzen Sie bitte Minimalbeispiele!
Das LilyPond-Schnipsel-Depot (LSR - LilyPond Snippet Repository) ist eine große Sammlung durch Anwender erstellter Beispiele, die frei kopiert und in eigenen Werken verwendet werden dürfen. Schauen Sie, was andere Leute konstruiert haben und fügen Sie ggf. eigene Schnipsel hinzu!
http://lsr.di.unimi.it |
Besonders lehrreiche Beispiele aus dem LSR werden in unsere offizielle Dokumentation eingefügt, in Schnipsel.
Unterstützung können Sie auch auf unserem IRC-Kanal erhalten:
#lilypond@irc.freenode.net |
Dieser Kanal hat kein öffentliches Archiv, sodass jede Frage, die auch für andere Benutzer nützlich sein könnte, besser auf der Mailingliste gestellt wird.
Folgen sie unserem community blog, ‚Scores of Beauty‘:
https://lilypondblog.org |
info-lilypond@gnu.orgDiese Mailingliste hat ein sehr geringes Mailaufkommen und kann nur gelesen werden. Sie dient der Ankündigung neuer Versionen.
lilypond-devel@gnu.orgDiskussionen der Entwicklern finden auf dieser Liste statt. Patches können ebenfalls hier hin geschickt werden.
bug-lilypond@gnu.orgFehlermeldungen und Diskussionen finden hier statt, jedoch bitte keine Patches an diese Liste senden.
Achtung: Bevor Sie eine Nachricht an die Fehler-Liste schreiben, lesen Sie bitte unsere Richtlinien für Fehlerberichte.
translations@lilynet.orgJegliche Diskussionen über Übersetzungen der LilyPond Handbücher sollte auf dieser Liste stattfinden, jedoch bitte keine Patches an diese Liste senden.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Tiny examples
Ein Minimalbeispiel ist eine vollständige Quelldatei, die nicht mehr weiter reduziert werden kann, ohne dass das illustrierte Problem verschwindet. Es sollten keine Warnungen und Fehlermeldungen produziert werden, die nicht mit dem Problem im Zusammenhang stehen.
\version-Nummer einfügen.
%
oder %{ … %}). Wenn Sie etwas auskommentieren
können, und das Problem immer noch vorhanden ist, entfernen Sie die
auskommentierten Abschnitte.
\override oder \set, es sei denn,
der Fehler zeigt sich im Zusammenhang mit diesen Befehlen.
Ist der Code unten ein Minimalbeispiel?
\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''> ]
}
}
|
Das ist zwar kein langer Code, aber ein wirkliches Minimalbeispiel ist folgendes:
\version "2.14.1"
{
% middle tie looks funny here:
<c' d'' b''>8. ~ <c' d'' b''>8
}
|
Wenige Minimalbeispiele brauchen mehr als 10 Zeilen, meistens kann das Problem mit vier Zeilen gezeigt werden!
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Bug reports
Wenn Ihre Datei zu einem Programmabsturz oder falschem Notensatz führt, handelt es sich um einen Fehler.
Vielleicht ist der Fehler schon bekannt. Prüfen Sie hier:
https://gitlab.com/lilypond/lilypond/-/issues |
Achtung: Bitte fügen Sie NICHT selber neue Fehlerberichte hinzu! Wenn der Fehler einmal im Bug-Tracker zu sehen ist, können Sie selber weitere Informationen hinzufügen.
Wenn Sie einen Fehler entdeckt haben, der nicht aufgelistet ist, helfen Sie uns bitte, indem Sie einen Fehlerbericht (bug report) erstellen.
Achtung: Wir akzeptieren Fehlerberichte nur als Minimalbeispiele. Wir haben sehr begrenzte Ressourcen, weshalb jedes nicht-Minimalbeispiel zurückgewiesen wird. Fast jeder Fehler kann mit vier oder sogar weniger Noten demonstriert werden!
Hier ein Beispiel eines guten bug reports:
% 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
}
|
Wenn Sie sichergestellt haben, dass der Fehler noch nicht bekannt ist und einen Fehlerbericht erstellt haben, senden sie ihn bitte an uns!
Wenn Ihr Fehlerbericht an die Liste versandt wurde, untersuchen unsere Fehlerbeseitiger (engl. bug squad) den Bericht. Sie werden eventuell nach mehr Information gefragt. Sie werden informiert, wann der Bericht im Tracker hinzugefüt wird. Warten Sie bitte vier Tage, da uns für diese Tätigkeit nur eine geringe Zahl an Helfern zur Verfügung stehen.
Wenn ein Fehler dem Tracker hinzugefügt wurde, können Sie ihn kommentieren, um mehr Information hinzuzufügen. Sie können den Fehler auch markieren, sodass Sie immer eine E-Mail erhalten, wenn Aktivität für diesen Fehler vorkommt. Hierzu müssen Sie einen Google-Account haben.
Wenn ein Fehlerbericht einmal dem Tracker hinzugefügt wurde, kann es sehr hilfreich sein, wenn wir sehen können, wie die gewünschte Ausgabe aussieht. Sie können beliebig Code, Text und Bilder (auch mit anderen Programmen erstellt) hinzufügen, die das gewünschte Bild demonstrieren.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Help us
Vielen Dank, dass Sie sich dafür interessieren, uns zu helfen – wir freuen uns sehr, wenn Sie sich einbringen. Bitte denken Sie daran, dass Sie auch allen anderen LilyPond-Benutzern helfen, wenn Sie sich an der Entwicklung beteiligen.
Auch kleine Aufgaben können große Auswirkungen haben: wenn man sich ihnen annimmt, können sich die erfahrenen Entwickler den schwierigen Aufgaben widmen anstatt diese einfachen Probleme zu lösen.
Bei einem so großen und vielfältigen Projekt wie LilyPond ist es oft schwierig zu entscheiden, wo man anfangen soll. Zusätzlich zu den Vorschlägen, die sich weiter unten finden, können Sie auch eine E-Mail (auf Englisch) an den Frog meister schicken und Ihre Fähigkeiten mitteilen, sodass er Ihnen einen Einstieg zeigen oder Ihnen bei ihren eigenen Projekten helfen kann.
Keine Kentnisse im Programmieren benötigt!
Diese Aufgaben setzen voraus, dass Sie die Quellen von Programm und Dokumentation haben und die Quellen auch kompilieren können.
Achtung: Wir empfehlen, dass Beitragende, die Windows oder MacOS X benutzen, nicht ihre eigene Entwicklungsumgebung einrichten, sondern anstattdessen lilybuntu benutzen, welches besprochen ist in (contributor-big-page)Quick start in Abschnitt ‘Schnellstart’ in Contributor’s Guide.
Beitragende, die GNU/Linux oder FreBSD benutzen, können auch lilybuntu einsetzen, aber wenn Sie Ihre eigene Entwicklungsumgebung einrichten wollen, lesen Sie bitte (contributor-big-page)Working with source code in Abschnitt ‘Mit dem Sourcecode arbeiten’ in Contributor’s Guide und (contributor-big-page)Compiling in Abschnitt ‘Kompilieren’ in Contributor’s Guide.
Beginnen Sie, indem Sie das Kapitel (contributor-big-page)Summary for experienced developers in Abschnitt ‘Zusammenfassung für erfahrene Entwickler’ in Contributor’s Guide lesen.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Sponsoring
In der Vergangenheit
Das LilyPond-Projekt kann derartige Verabredungen nicht koordinieren, wir wollen deshalb weder dazu aufrufen noch davon abraten. Jegliche Abkommen zwischen privaten Personen beziehen sich nur auf diese Personen, ncht auf das LilyPond-Projekt.
Jeder Benutzer, der Geld gegen Arbeit eintauschen will, sollte Folgendes im Auge behalten:
Hier ist eine Liste der Leute, die sich Dienstleistungen sponsoren lassen. Die Menge an Arbeit, die unterschiedliche Entwickler im Laufe des Jahres vollbringen, kann stark schwanken. Wir können nicht garantieren, dass die Liste aktuell ist oder die Leute auf der Liste über bestimmte Fähigkeiten verfügen. Das einzige Kriterium ist, dass die entsprechende Person um Aufnahme in die Liste gebeten hat.
Ein Blick auf die erbrachten Leistungen im git-Repositorium ist eine gute Art sich über Aktivität und Erfahrenheit von Entwicklern Klarheit zu verschaffen. Statistiken bis 2.21.3:
| gesamter Zeitraum | das letzte Jahr | die letzten drei Monate |
Interessirte Entwickler:
Spenden sind notwendig, damit ich meine aktuelle Vollzeitbeschäftigung an LilyPond aufrechterhalten kann. Ich konzentriere mich auf das Schnittstellendesign für Benutzer und Programmieren, auf Kohäränz, Implementation, Vereinfachung, Dokumentation und Fehlerbeseitigung.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Development
Achtung: Hier handelt es sich um möglicherweise instabile Entwicklerversionen. Wenn Sie nicht genau wissen, wie man LilyPond installiert und benutzt, empfehlen wir ausdrücklich, die stabile Download-Version zu benutzen und die stabilen Handbücher zu lesen.
Es gibt zwei Veröffentlichungsreihen für LilyPond: stabile Versionen und die instabilen Entwicklerversionen. Stabile Versionen haben eine gerade zweite Versionsnummer (also etwa 2.8, 2.10, 2.12). Entwicklerversionen haben eine ungerade zweite Versionsnummer (also 2.7, 2.9, 2.11).
Anleitungen zu git und der Kompilierung finden sich im Contributor’s Guide (nur auf Englisch).
Schreiber der Dokumentation und Tester sollten die neuesten Binärpakete herunterladen:
GNU/Linux x86: LilyPond 2.21.3-1
GNU/Linux 64: LilyPond 2.21.3-1
GNU/Linux PPC: LilyPond 2.21.3-1
FreeBSD i386: LilyPond 2.21.3-1
FreeBSD amd64: LilyPond 2.21.3-1
Mac OS X x86 32-bit: LilyPond 2.21.3-1
Die Entwicklung von LilyPond ist eine ziemlich komplizierte Angelegenheit. Um neuen Mitarbeitern zu helfen und das ganze System (ziemlich) stabil zu halten, haben wir ein Handbuch für Entwicklungsarbeiten geschrieben (nur auf Englisch).
| Zum Herunterladen |
|---|
| Doc tarball for 2.21.3 |
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Google Summer of Code
Google Summer of Code ist ein globales Programm, bei dem Google Studenten Stipendien offeriert, um in den Sommerferien an Open-Source-Projekten zu arbeiten.
Es ist dies eine ausgezeichnete Gelegenheit neue Entwickler zu finden und diejenigen, die bereits an LilyPond mitwirken zu motivieren, ihr Engagement zu vertiefen. Einer unserer Entwickler wurde für den Sommer 2012 als Teil des GNU-Projekts angenommen; wir hoffen, dass auch in kommenden Jahren Entwickler für LilyPond an dem Programm teilnehmen können.
Unten befindet sich eine Liste mit vorgeschlagenen Projekten für GSoC-Stundenten für den Sommer 2012. Wir haben sie hier aufbewahrt, damit sie zukünftigen GSoC Interessenten als Anregung dienen mag.
Natürlich gibt es noch sehr viele andere Aufgaben, um LilyPond weiter zu verbessern und das LilyPond Entwicklerteam wird jederzeit jede/n gern unterstützen, die/der Aufgaben wie jene unten aufgeführten angehen möchte.
Eine vollständige Liste aller aktuell offenen Punkte findet sich hier.
Beseitigen Sie Probleme bei der Synchronisation von Vorschlagsnoten. Vorschlagsnoten können das Zeitmaß von LilyPond durcheinander bringen und so unerwartete Effekte hervorrufen. Das tritt besonders dann auf, wenn viele Notensysteme verwendet werden und einige Vorschlagsnoten haben und andere nicht.
Schwierigkeit: mittel Erfordernisse: C++, MIDI Empfohlen: mit den Interna von LilyPond vertraut sein Mentoren: Mike Solomon, Carl Sorensen
Verbesserung der MusicXML Import- und Exportfunktionen:
Schwierigkeit: mittel Erfordernisse: MusicXML, Python, grundlegende Kenntnisse in LilyPond Mentoren: Reinhold Kainhofer, Mike Solomon
Kenntnis anderer Notensatzprogramme (zum Testen) wäre hilfreich.
Die Standardform von Binde- und Legatobögen ist oft nicht zufriedenstellend. Durch Schlüssel- oder Systemwechsel unterbrochene Bögen werden nicht gut behandelt. Teil der Aufgabe wäre es, Beispiele von unschöner Ausgabe zu sammeln und zu gruppieren um dann zu entscheiden, welche Ausgabe stattdessen gewünscht wäre. Schließlich muß der dazu notwendige Programmcode geschrieben werden.
Schwierigkeit: schwer Erfordernisse: C++, Erfahrung mit Heuristiken Empfohlene Kenntnisse: LilyPond-Kenntnisse, Sinn für Ästhetik Mentor: Mike Solomon
Schwierigkeit: leicht Erfordernisse: MetaFont, C++, gutes Auge für Details Empfohlene Kenntnisse: grundlegene LilyPond Kenntnis Mentor: Werner Lemberg
Die Standardpositionierung von normalen Balken, Balken über Systeme hinweg, unterbrochene und Knie-Balken sollte verbessert werden. Balken sollten sich am Kontext und benachbarten Noten orientieren (siehe Abschnitt 2.2). Wenn möglich, sollte die Rechenzeit für die Bebalkung verkürzt werden.
Schwierigkeit: mittel Erfordernisse: C++, Erfahrung mit Heuristiken Empfohlene Kenntnisse: Sinn für Ästhetik Mentoren: Mike Solomon, Carl Sorensen
Werkzeuge zur automatisierten Codeanalyse wie ‚valgrind memory leak detection‘ oder ‚callgrind code profiler‘ liefern wertvolle Information über möglicher Defizite in unserem C++ code. Eine Bereinigung der Warnungen würde uns erlauben automatisiert Patches, die zusätzliche Warnungen erzeugen, abzulehnen.
Schwierigkeit: mittel Erfordernisse: C++ Mentoren: Joe Neeman, Reinhold Kainhofer
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Authors
Guido Aulisi, Joe Austin, Federico Bruni, Nathan Chou, Dan Eble, John Gourlay, Marc Hohl, Masamichi Hosoda, Mark Knoop, Tobias Kretschmar, Vincent Le Ligeour, James Lowe, Thomas Morley, Paul Morris, David Nalesnik, Keith OHara, Benkő Pál, Knut Petersen, Julien Rioux, Ben Rudiak-Gould, Devon Schudy, Heikki Tauriainen
Jay Anderson, Masamichi Hosoda, Abraham Lee
Simon Albrecht, Frédéric Bron, Federico Bruni, Colin Campbell, Urs Liska, James Lowe, Thomas Morley, Jean-Charles Malahieude, Patrick Schmidt, Pierre Perol-Schneider, Greg Swinford, Martin Tarenskeen
Simon Albrecht, Federico Bruni, Colin Campbell, Phil Holmes, Ralph Palmer
Simon Albrecht, Colin Campbell, Eluze, Marc Hohl, Phil Holmes, Marek Klein, Alex Loomis, Kieren MacMillan, Thomas Morley, Tim McNamara, Paul Morris, David Nalesnik, Urs Liska, Ralph Palmer, Pierre Perol-Schneider, Neil Puttock, Tao
Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric, Walter Garcia-Fontes, Tommaso Gordini, Erika Griechisch, Denes Harmath, Masamichi Hosoda, Jean-Charles Malahieude, Till Paala, Yoshiki Sawada, Tomohiro Tatejima, Paco Tomillo
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, Torsten Hämmerle, Yuval Harel, Andrew Hawryluk, Christian Hitz, Karin Hoethker, Rutger Hofmann, Marc Hohl, Bernard Hurley, Yoshinobu Ishizaki, Chris Jackson, Felix Janda, David Jedlinsky, Heikki Junes, Michael Käppler, Thomas Klausner, Marek Klein, Michael Krause, Jean-Baptiste Lamy, Jonatan Liljedahl, Peter Lutek, Andrew Main, Kieren MacMillan, Hendrik Maryns, Thomas Morgan, David Nalesnik, Matthias Neeracher, Keith OHara, Justin Ohmie, Tatsuya Ono, Benkő Pál, Benjamin Peterson, Guy Gascoigne-Piggford, Anders Pilegaard, Henning Hraban Ramm, Nathan Reed, Julien Rioux, Johannes Rohrer, 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
Tom Cato Amundsen, Marc Hohl, Chris Jackson, Alexander Kobel, Abraham Lee, Keith OHara, Carsten Steger, Arno Waschk, Rune Zedeler
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, Guy Stalnaker, Arnold Theresius, Anh Hai Trinh, Eduardo Vieira, Stefan Weil, Rune Zedeler, Rodolfo Zitellini
Colin Campbell, Anthony Fok, Christian Hitz, Phil Holmes, Chris Jackson, Heikki Junes, David Svoboda
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
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Acknowledgements
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Publications
Sollten Sie hier die Erwähnung von wissenschaftliche Aufsätze vermissen, dann teilen Sie uns dies bitte mit indem Sie eine Nachricht an die bug-lilypond Mailingliste schicken. Falls Sie diese Mailingliste noch nicht abonniert haben, können Sie das auf dieser Seite ändern: info page.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof News
Achtung: Viele alte Ankündigungen und Listen der Änderungen finden sich in der Abstellkammer
June 22, 2020 - All Italian users are welcome to join the new Italian mailing list, where they can get help and discuss about LilyPond in their mother language.
We are happy to announce the release of LilyPond 2.21.3. This is a development version, but these are usually reliable. If you want to use the latest stable version of LilyPond, we recommend using the 2.20.0 version.
We are proud to announce the release of GNU LilyPond 2.20.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.
This version provides a number of updates, including updated manuals. We recommend all users to upgrade to this version.
| [ < ] | [ > ] | [ << ] | [ Nach oben ] | [ >> ] | [Anfang] | [Inhalt] | [Index] | [ ? ] |
@translationof Attic
Ankündigungen und Neuigkeiten nach 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
Ausführliche Liste der Änderungn nach 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 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
Änderungslog für Entwickler nach 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
We are happy to announce the release of LilyPond 2.21.2. This is a development version, but these are usually reliable. If you want to use the latest stable version of LilyPond, we recommend using the 2.20.0 version.
We are happy to announce the release of LilyPond 2.21.1. This is a development version, but these are usually reliable. If you want to use the latest stable version of LilyPond, we recommend using the 2.20.0 version.
We are happy to announce the release of LilyPond 2.21.0. If you want to use the latest stable version of LilyPond, we recommend using the 2.20.0 version.
We are happy to announce the release of LilyPond 2.19.84. This release is the final pre-release test version for the upcoming stable 2.20 release. If you require a stable version of LilyPond, we recommend using the 2.18 version.
We are happy to announce the release of LilyPond 2.19.83. This release is a further pre-release test version for the upcoming stable 2.20 release. If you require a stable version of LilyPond, we recommend using the 2.18 version.
We are happy to announce the release of LilyPond 2.19.82. This release is a further pre-release test version for the upcoming stable 2.20 release. If you require a stable version of LilyPond, we recommend using the 2.18 version.
We are happy to announce the release of LilyPond 2.19.81. This release is a further pre-release test version for the upcoming stable 2.20 release. If you require a stable version of LilyPond, we recommend using the 2.18 version.
We are happy to announce the release of LilyPond 2.19.80. This release is a pre-release test version for the upcoming stable 2.20 release. If you require a stable version of LilyPond, we recommend using the 2.18 version.
We are happy to announce the release of LilyPond 2.19.65. 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.
We are happy to announce the release of LilyPond 2.19.64. 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.
We are happy to announce the release of LilyPond 2.19.63. 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.
We are happy to announce the release of LilyPond 2.19.62. 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.
We are happy to announce the release of LilyPond 2.19.61. 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.
We are happy to announce the release of LilyPond 2.19.60. 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.
We are happy to announce the release of LilyPond 2.19.59. 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.
We are happy to announce the release of LilyPond 2.19.58. 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.
We are happy to announce the release of LilyPond 2.19.57. 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.
We are happy to announce the release of LilyPond 2.19.56. 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.
We are happy to announce the release of LilyPond 2.19.55. 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.
We are happy to announce the release of LilyPond 2.19.54. 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.
We are happy to announce the release of LilyPond 2.19.53. 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.
We are happy to announce the release of LilyPond 2.19.52. 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.
We are happy to announce the release of LilyPond 2.19.51. 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.
We are happy to announce the release of LilyPond 2.19.50. 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.
We are happy to announce the release of LilyPond 2.19.49. 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.
We are happy to announce the release of LilyPond 2.19.48. 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.
We are happy to announce the release of LilyPond 2.19.47. 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.
We are happy to announce the release of LilyPond 2.19.46. 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.
We are happy to announce the release of LilyPond 2.19.45. 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.
We are happy to announce the release of LilyPond 2.19.44. 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.
We are happy to announce the release of LilyPond 2.19.43. 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.
We are happy to announce the release of LilyPond 2.19.42. 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.
We are happy to announce the release of LilyPond 2.19.41. 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.
We are happy to see two students, Nathan Chou and Jeffery Shivers, working on LilyPond as participants in the Google Summer of Code this year. We hope they produce great results and stay in the developer community afterwards.
Nathan will tackle an annoying limitation, namely the unability of spanners to cross voices. His work will make a class of ugly workarounds obsolete. Jeffery will bring the ScholarLY package[1] to production quality and add a LaTeX package to it, making it possible to create beautiful critical reports from data encoded directly in the LilyPond score.
We are happy to announce the release of LilyPond 2.19.40. 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.
We are happy to announce the release of LilyPond 2.19.39. 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.
We are happy to announce the release of LilyPond 2.19.38. 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.
We are happy to announce the release of LilyPond 2.19.37. 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.
We are happy to announce the release of LilyPond 2.19.36. 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.
We are happy to announce the release of LilyPond 2.19.35. 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.
We are happy to announce the release of LilyPond 2.19.34. 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.
We are happy to announce the release of LilyPond 2.19.33. 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.
We are happy to announce the release of LilyPond 2.19.32. 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.
We are happy to announce the release of LilyPond 2.19.31. 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.
We are happy to announce the release of LilyPond 2.19.30. 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.
We are happy to announce the release of LilyPond 2.19.29. 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.
We are happy to announce the release of LilyPond 2.19.28. 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.
We are happy to announce the release of LilyPond 2.19.27. 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.
We are happy to announce the release of LilyPond 2.19.26. 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.
We are happy to announce the release of LilyPond 2.19.25. 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.
We are happy to announce the release of LilyPond 2.19.24. 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.
We are happy to announce the release of LilyPond 2.19.23. 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.
We are happy to announce the release of LilyPond 2.19.22. 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.
We are happy to announce the release of LilyPond 2.19.21. 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.
We are happy to announce the release of LilyPond 2.19.20. 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.
We are happy to announce the release of LilyPond 2.19.19. 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.
We are happy to announce the release of LilyPond 2.19.18. 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.
We are happy to announce the release of LilyPond 2.19.17. 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.
At long last, we are very happy to announce the release of LilyPond 2.19.16. 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.
We would like to acknowledge and thank Masamichi Hosoda for making this release possible with his work on updating GUB, the build tool.
We are happy to announce the release of LilyPond 2.19.15. 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.
We are happy to announce the release of LilyPond 2.19.14. 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.
We are happy to announce the release of LilyPond 2.19.13. 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.
We are happy to announce the release of LilyPond 2.19.12. 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.
We are happy to announce the release of LilyPond 2.19.11. 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.
We are happy to announce the release of LilyPond 2.19.10. 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.
We are happy to announce the release of LilyPond 2.19.9. 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.
We are happy to announce the release of LilyPond 2.19.8. 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.
We are happy to announce the release of LilyPond 2.19.7. 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.
We are happy to announce the release of LilyPond 2.19.6. 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.
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.
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.
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.
We are thrilled that the edition of the songs of Oskar Fried (1871-1941), published recently by our fellow contributors Urs Liska and Janek Warchoł [1], received the "Musikeditionspreis BEST EDITION 2014" of the German Music Publishers’ Association [2]. The ceremony took place at the Frankfurt Musikmesse.
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 [3].
[1] https://lilypondblog.org/category/fried-songs
[2] http://www.best-edition.de
[3] http://www.sound-rel.de
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.
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.
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.
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.
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.
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:
\override Voice.TextSpanner.bound-details.left.text = "rit." |
instead of the previous
\override Voice.TextSpanner #'(bound-details left text) = "rit." |
\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:
https://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
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ł
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
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
Colin Campbell, Eluze, Marc Hohl, Phil Holmes, Marek Klein, Ralph Palmer
Colin Campbell, Eluze, Marc Hohl, Marek Klein, Kieren MacMillan, Urs Liska, Ralph Palmer
Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric, Jean-Charles Malahieude, Till Paala, Yoshiki Sawada
and numerous other contributors.
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.
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.
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 (web-big-page)Bug reports in Abschnitt ‘Bug reports’ in Allgemeine Information.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Janek Warchoł has created a LilyPond blog. You can find it at lilypondblog.org!
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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!
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.
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.
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.
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.
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.
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.
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.
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.
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:
https://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
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 @ref{Bug reports}.
New features since 2.14.2 are listed in the „Changes“ manual on the website section about @ref{Development}.
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 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!
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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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.
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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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!
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 @ref{Development}.
Update: Due to a few Critical bugs, another release candidate will be required.
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.
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 @ref{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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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!
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.
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.
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.
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!
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.
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.
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 @ref{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 @ref{Bug reports}.
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.
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.
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 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!
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The release countdown is cancelled due to the discovery of a Critical regression.
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 @ref{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 @ref{Bug reports}.
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.
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.
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.
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 @ref{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 @ref{Bug reports}.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:
https://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.
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 @ref{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 @ref{Bug reports}.
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.
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.
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 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.
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.
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 @ref{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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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.
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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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.
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.
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.
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.
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!
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 @ref{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 @ref{Bug reports}.
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.
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.
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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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.
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 @ref{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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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.
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.
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.
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 @ref{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 @ref{Bug reports}.
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!
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 @ref{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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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 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!
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 @ref{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 @ref{Bug reports}.
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 @ref{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 @ref{Bug reports}.
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.
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.
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!
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.
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.
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!
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.
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.
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.
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 @ref{Contact}.
Achtung: 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: https://lilypond.org/web/
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.
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.
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.
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.
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.
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.
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!
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.
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.
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.
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.
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.
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.
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!
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.
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.
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.
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.
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.
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 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.
As you can see, we have a new website design. Many thanks to texi2html and CSS for being so flexible!
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!
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.
@ref{Changes},
@ref{Development}.
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 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 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...
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.
A new stable release of LilyPond is available.
Announcement,
@ref{Changes},
Download.
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,
@ref{Changes},
@ref{Old downloads}.
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.
@ref{Changes},
@ref{Old downloads}.
LilyPond 2.11.63 is available. This release has lots of updates to the documentation and translations. @ref{Old downloads}.
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,
@ref{Old downloads}.
LilyPond 2.11.61 has been released. It has updates to
documentation translations, and a new automatic accidentals style
(teaching) has been added.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
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.
@ref{Old downloads}.
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. @ref{Old downloads}.
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,
@ref{Changes},
@ref{Old downloads}.
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.
@ref{Changes},
@ref{Old downloads}.
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.
@ref{Changes},
@ref{Old downloads}.
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,
@ref{Old downloads}.
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,
@ref{Old downloads}.
LilyPond 2.11.53 is out. This release fixes a lot of bugs.
Bugfixes,
@ref{Old downloads}.
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,
@ref{Changes},
@ref{Old downloads}.
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,
@ref{Old downloads}.
Release 2.11.50 adds support for metronome marks with text, and
backslashed numbers for figured bass, contributed by
Reinhold Kainhofer.
Bugfixes,
@ref{Old downloads}.
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...
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 is out. It fixes a number of bugs, including bugs in beams formatting.
Bugfixes,
@ref{Old downloads}.
LilyPond 2.11.48 is out. This release fixes a few bugs, and
\compressMusic has been renamed
to \scaleDurations.
Bugfixes,
@ref{Old downloads}.
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...
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 now allows all text context properties to be markups,
except in \lyricmode. This release also fixes
regression tests maintenance for developers.
Bugfixes,
@ref{Old downloads}.
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,
@ref{Changes},
@ref{Old downloads}.
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 @ref{Contact}) is still used to announce releases and special events.
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...
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,
@ref{Changes},
@ref{Old downloads}.
Release 2.11.44 is available. Support for figured bass and chord
names has been added to the MusicXML
converter.
Bugfixes,
@ref{Old downloads}.
lilypond.orgのいくつかのページの日本語訳が出来ました。
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,
@ref{Old downloads}.
Release 2.11.42 is out. It fixes some formatting and spacing
bugs.
Bugfixes,
@ref{Old downloads}.
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.
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,
@ref{Old downloads}.
Release 2.11.37 is available. It has a few bugfixes, and documentation changes. (@ref{Old downloads})
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,
@ref{Old downloads}.
Release 2.11.33 is now available.
Bugfixes 2.10,
Bugfixes 2.11,
@ref{Old downloads}.
Release 2.11.32 is now available.
Bugfixes,
@ref{Old downloads}.
Release 2.11.31 is now available. It has more bugfixes, updates
for MusicXML import and lots of updates for the translations.
Bugfixes,
@ref{Old downloads}.
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,
@ref{Old downloads}.
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,
@ref{Old downloads}.
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.
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,
@ref{Old downloads}.
Release 2.11.26 supports page markers, eg. for use in
tables-of-contents. In addition, it fixes a number of bugs. Enjoy!
Bugfixes,
@ref{Old downloads}.
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,
@ref{Old downloads}.
This has lots of bugfixes.
Bugfixes 2.10,
Bugfixes 2.11,
@ref{Old downloads}.
Die Kapitel 1-5 (der Abschnitt für Anfänger) des LilyPond-Benutzerhandbuchs sind auf deutsch übersetzt — sie sind erhältlich für die @ref{Changes} online und @ref{Old downloads}.
This release has updates of the dot collision code.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release has some documentation updates.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
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.
This release fixes many bugs.
Bugfixes 2.10,
Bugfixes 2.11,
@ref{Changes},
@ref{Old downloads}.
This release fixes many bugs.
Bugfixes 2.10,
Bugfixes 2.11,
@ref{Changes},
@ref{Old downloads}.
This release fixes still more bugs, and included
singing support through festival contributed by Milan Zamazal.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release fixes still more bugs.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release fixes many bugs. (Bugfixes 2.10, Bugfixes 2.11, @ref{Changes}, @ref{Old downloads})
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,
@ref{Changes},
@ref{Old downloads}.
This release has a rewrite of the line-spanner code, responsible for
among other glissandi and text-crescendos, making them more flexible.
Bugfixes,
@ref{Changes},
@ref{Old downloads}
This release fixes a few minor but irritating bugs. In addition, the
2.11 release has updates of the tutorial.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release fixes lots of bugs. In particular, the tie formatting has
been further improved, and memory usage has been improved enormously.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release mirrors 2.11.12. Notably, it has the same memory
usage improvements.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release mostly has the same fixes as 2.11.11.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
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,
@ref{Changes},
@ref{Old downloads}.
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,
@ref{Changes},
@ref{Old downloads}.
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,
@ref{Changes},
@ref{Old downloads}.
This release has a couple of bugfixes, and —in 2.11.9—
further improvements in the regression test suite
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
New! Improved! With even more bugfixes!
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
lilypond.org auf deutsch - 31. Dezember 2006Die 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!
New! Improved! With even more bugfixes!
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release supports arbitrary fractional alterations, allowing
music with different microtonal conventions to be typeset.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
New! Improved! With even more bugfixes!
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
These releases complete the translation infrastructure for
Documentation.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
New! Improved! With even more bugfixes!
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
The vertical spacing improvements that were introduced in 2.11.0 now work
within a system as well as between systems.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release has graphical test results and several website build improvements.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
This release fixes several bugs.
Bugfixes,
@ref{Old downloads}.
From now on, our GUB binary builds include support for Linux/PPC. (@ref{Old downloads})
Fruit du travail d’une équipe de traducteurs, le tutoriel en français est maintenant disponible en ligne. Version 2.10, Version 2.11.
This release supports glissandi and harmonics in tablature.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
A new stable release of LilyPond is available.
Bugfixes,
@ref{Old downloads}.
This release has improved support for horizontal spacing.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
A new stable release of LilyPond is available.
Bugfixes,
@ref{Old downloads}.
This release has improved support for vertical spacing. (@ref{Changes}, @ref{Old downloads})
A new stable release of LilyPond is available. (Announcement, @ref{Changes}, @ref{Old downloads})
LilyPond development has moved over its source code to GIT, the fast version control system. Check out our repository at gnu.org.
This release has many more bugfixes.
Bugfixes,
@ref{Old downloads}.
This release has many more bugfixes.
Bugfixes,
@ref{Old downloads}.
This release has a new FretBoards context, and some further
bugfixes.
Bugfixes,
@ref{Changes},
@ref{Old downloads}.
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 (@ref{Publications}).
This release has further bugfixes.
Bugfixes,
@ref{Old downloads}.
This release has more bugfixes; from now on, binaries are also
available for x86/64.
Bugfixes,
@ref{Old downloads}.
This release has support for right hand guitar fingerings, and offers some bugfixes. (@ref{Changes}, Bugfixes, @ref{Old downloads})
This release cuts fragments of EPS directly from your finished score, and makes it easier to insert ties into lyrics. (@ref{Changes}, @ref{Old downloads})
Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
This release fixes many bugs. Among others, MacOS X QuickTime now honors tempo changes are in the MIDI output. (@ref{Changes}, @ref{Old downloads})
In this release, chords may be partially tied and lyric extenders have tunable padding. Moreover, many bugs were fixed (@ref{Changes}, @ref{Old downloads})
This releases fixes many bugs in the 2.9.14 release. (@ref{Old downloads})
This release contains a few minor bugfixes; the source tarball is also available. (@ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
This release supports doits and falls, and more tuning options for grace note spacing and tuplet brackets. (@ref{Changes}, @ref{Old downloads})
This release supports pdftex for lilypond-book, and uses PdfTeX for generating manuals, so page numbers and references are now clickable. (@ref{Changes}, @ref{Old downloads})
This release wraps improvements of the last two weeks. As a new feature, it supports tunable tuplet number formatting for nested tuplets. (@ref{Changes}, @ref{Old downloads})
This releases fixes a couple of bugs in 2.9.9. (@ref{Changes}, @ref{Old downloads})
This releases fixes many bugs in 2.9.8 and earlier. (@ref{Changes}, @ref{Old downloads})
2.9.8 has support for different spacing sections within a single score, and better infrastructure for automated regression testing. (@ref{Changes}, @ref{Old downloads})
2.8.4 fixes some minor bugs, and includes a backport of the infrastructure for automated regression testing. (@ref{Old downloads})
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
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
This
release has new features in beam formatting: beams may now be put on
single stems, and obey the beatGrouping property. MusicXML
converter. (@ref{Changes}, @ref{Old downloads})
The Automated Engraving essay has been updated with material from the FISL talk, with pages on modeling notation and algorithms for esthetics. Happy reading!
This release supports object rotation, hairpins with circled tips, hairpins that run to barlines before notes and improvements in the MusicXML converter. (@ref{Changes}, @ref{Old downloads})
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.
(@ref{Changes}, @ref{Old downloads})
This release has fixes for minor bugs and compilation issues. (@ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
The slides for Han-Wen’s talk at FISL 7 are now online. (@ref{Publications})
Important bugfixes include CJK font handling and a Darwin/x86 port. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
LilyPond now also runs on Intel based macs, offering a 400% speedup over the emulated PowerPC binaries. (@ref{Old downloads})
Version 2.8 is here! Read the release announcement. (@ref{Changes}, @ref{Old downloads})
This release has even more bug fixes. Please test before 2.8 is released. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
This release has more bug fixes. Please help us by testing it! (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes},
@ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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). (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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! (@ref{Old downloads})
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 @ref{Old downloads} get them!
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.
This release allows you to switch staff lines on and off individually (feature sponsored by Andrea Valle). (@ref{Changes}, @ref{Old downloads})
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.
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 @ref{Old downloads} page. Let us know how you fare!
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! (@ref{Changes}, @ref{Old downloads})
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). (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
This release has the following new features:
(@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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.
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). (@ref{Changes}, @ref{Old downloads})
This release updates the bugreporting address and reorganizes the documentation tree. (@ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
This release fixes a large number of bugs. Please upgrade before reporting bugs in the 2.7 series. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
This release fixes a few minor problems with the stable series. (@ref{Changes}, @ref{Old downloads})
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). (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
This is mainly a bugfix release. (@ref{Changes}, @ref{Old downloads})
Grâce à l’équipe des traducteurs, de nombreuses pages du site sont maintenant disponibles en français, notamment l’essai sur la gravure musicale.
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. (@ref{Changes}, @ref{Old downloads})
The Belgian newspaper De Standaard investigates what drives Free Software authors in an article titled Delen van KENNIS zonder WINSTBEJAG (Non-profit sharing of knowledge) using LilyPond as an example. This marks LilyPond’s first appearance in mainstream printed press.
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á. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
Lily 2.7.5 has a large number of bugfixes, among others, in slur formatting, spacing, rest collisions and tuplet bracket formatting. (@ref{Changes}, @ref{Old downloads})
LilyPond 2.7.4 has support for proportional notation, where the space for a note is proportional to the time it takes. (@ref{Changes}, @ref{Old downloads})
This release fixes a memory corruption bug that was triggered by \override’ing Beam settings. (@ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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, @ref{Old downloads}, @ref{Changes})
LilyPond 2.7.1 has no user-visible changes. However, due to restructuring „under the hood“, this version will be 10 to 20 % faster. (@ref{Old downloads})
This version fixes a few minor bugs found in 2.6.0, and also works on DOS-based Windows versions. (@ref{Changes}, @ref{Old downloads})
LilyPond 2.7.0 is out. It has support for paragraph text and pitched trill notation. (@ref{Changes}, @ref{Old downloads})
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. (@ref{Old downloads})
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 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. (@ref{Old downloads})
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. (@ref{Old downloads})
This is (hopefully) the last Release Candidate before 2.6. Give it a good shake to find those last bugs! (@ref{Old downloads})
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). (@ref{Old downloads})
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. (@ref{Old downloads})
There are now a native, standalone installers for Windows and MacOS. They also support PDF point & click. (@ref{Old downloads})
This release has many small bugfixes and updates to the documentation. (@ref{Old downloads})
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. (@ref{Old downloads})
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. (@ref{Changes},
@ref{Old downloads})
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. (@ref{Old downloads})
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. (@ref{Changes}, @ref{Old downloads})
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 @ref{Changes} file, or go straight to @ref{Old downloads}.
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 @ref{Changes} file and @ref{Old downloads}.
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. @ref{Old downloads}
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. @ref{Old downloads}
LilyPond 2.5.16 is out. This release fixes a few minor but irritating errors. A Fedora Core 3 binary is also available. @ref{Old downloads}
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 @ref{Changes} file and @ref{Old downloads}!
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 @ref{Changes} file and download @ref{Old downloads}!
LilyPond 2.4.5 is out. This release backports the tieWaitForNote feature and has support for tetex-3.0. @ref{Old downloads}
LilyPond 2.5.13 is available for Fedora Core 3. You need to install 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.
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 @ref{Changes} file and download @ref{Old downloads}!
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.
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 @ref{Changes} file and @ref{Old downloads}!
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. @ref{Old downloads}!
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. @ref{Old downloads}
LilyPond 2.5.9 is out. This release fixes a couple of annoying bugs in the direct PS output for piano braces. @ref{Old downloads}
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 @ref{Old downloads}!
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
LilyPond 2.4.2 is out. This release fixes a number of security problems with –safe, and adds a lot of polishing fixes. @ref{Old downloads}
LilyPond 2.4.1 is out. This release includes a number of small fixes that were made to 2.4.0 last week. @ref{Old downloads} and check out the changes in the ChangeLog.
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 @ref{Changes} file. @ref{Old downloads}
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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{}. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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.
LilyPond 2.3.19 is out. It’s mainly a bugfix release. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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!
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. @ref{Old downloads} and check out the changes in the ChangeLog.
LilyPond 2.2.6 fixes a few minor issues, among others, the disappearing metronome mark. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few annoying bugs fixed. @ref{Old downloads} and check out the changes in the ChangeLog.
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:
@ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
LilyPond 2.2.5 was released. It has a few bug fixes from 2.3.x. @ref{Old downloads} and check out the changes in the ChangeLog.
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. @ref{Old downloads} and check out the changes in the ChangeLog.
LilyPond 2.2.4 was released. It is mainly a bug fix release. @ref{Old downloads} and check out the changes in the ChangeLog.
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 @ref{Old downloads}.
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 @ref{Old downloads}.
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
@ref{Old downloads}.
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 @ref{Old downloads}.
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 @ref{Old downloads}.
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 @ref{Changes} or head straight to the @ref{Old downloads}.
LilyPond 2.3.1 is out. This release has many new and cool features. Check out the @ref{Changes} or head straight to the @ref{Old downloads}.
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!
LilyPond 2.2.0 is now available on Windows, and should find its way to the Cygwin mirrors soon.
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 @ref{Changes}. @ref{Old downloads}.
Binaries for LilyPond 2.2.0 are available for MacOS X, Slackware, Mandrake and Debian Woody. @ref{Old downloads}
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 @ref{Old downloads}.
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. @ref{Old downloads}.
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
@ref{Changes}.
@ref{Old downloads}
LilyPond 2.1.33 fixes a serious bug, and a few other irritations. @ref{Old downloads}
LilyPond 2.1.32 has more rewriting in the user manual. There is also an experimental implementation of optimal page breaking (Postscript backend only). @ref{Old downloads}.
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 @ref{Changes} and @ref{Old downloads}.
linuxmusician.com is running an interview with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main authors of LilyPond.
LilyPond 2.1.30 has editorial fixes for the manual, and experimental support for page layout in the PostScript backend. See the @ref{Changes} and @ref{Old downloads}.
LilyPond 2.1.29 fixes a couple of MIDI bugs, and has
experimental support for producing titles with
markup.
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
@ref{Changes} and
@ref{Old downloads}.
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 @ref{Changes} and @ref{Old downloads}.
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 @ref{Changes}. @ref{Old downloads}
LilyPond 2.1.25 fixes many bugs, and changes the conventions for altering accidental rules. @ref{Old downloads}
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
@ref{Changes}.
@ref{Old downloads}
LilyPond 2.1.22 has a
simplification of the \property syntax: it is
shorter and more consistent now. More information in the
@ref{Changes}.
@ref{Old downloads}
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 @ref{Changes}. @ref{Old downloads}
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 @ref{Changes}. @ref{Old downloads}
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
@ref{Changes}.
@ref{Old downloads}
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
@ref{Changes}.
@ref{Old downloads}
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 @ref{Changes}.
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 @ref{Changes}. @ref{Old downloads}
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 @ref{Changes}. @ref{Old downloads}
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 @ref{Changes}. @ref{Old downloads}
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.
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. @ref{Old downloads}
LilyPond 2.1.12 fixes many bugs and improves formatting of ottava brackets. More information in the @ref{Changes}. @ref{Old downloads}
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 @ref{Changes}. @ref{Old downloads}
LilyPond 2.1.10 has a load of bugfixes and a shorter syntax for octave checks. More information in the @ref{Changes}. @ref{Old downloads}
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 @ref{Changes}. @ref{Old downloads}
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
@ref{Changes}. @ref{Old downloads}
An update to the stable branch, version 2.0.2, was released today. It contains a couple of minor bugfixes. @ref{Old downloads}
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 @ref{Changes} and download here.
LilyPond 2.1.6 continues to improve the layout of lyrics. More information in the release notes and download here.
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 @ref{Changes} and download here.
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 @ref{Changes} and download here.
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 @ref{Changes} and download here.
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 @ref{Changes} and download here.
LilyPond 2.1.1 released. This release wraps together all the small fixes made during Han-Wen’s absence. See the @ref{Changes} and download here.
LilyPond 2.0.1 binaries for Mandrake 9.1 available from here thanks to Heikki Junes.
LilyPond 2.0.1 binaries for Slackware 9 available from here, thanks to Ricardo Hoffman.
LilyPond 2.0.1 binaries are available for Macos X, many thanks to Matthias Neeracher. @ref{Old downloads}
LilyPond 2.0.1 binaries are available for Windows (Cygwin version 1.5). @ref{Old downloads}. Thanks to Bertalan Fodor, our new Cygwin maintainer!
LilyPond 2.0.1 is released. It contains minor bugfixes. See the @ref{Changes} or download here directly.
PlanetCCRMA has been updated to include LilyPond 2.0. Go here to download. Thanks to Fernando Pablo Lopez-Lezcano!
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.
LilyPond 1.9.10 is released. This is the final LilyPond 2.0 release candidate. Check the @ref{Changes} and download here.
LilyPond 1.9.9 is released. This is the second LilyPond 2.0 prerelease. Check the @ref{Changes} and download here.
LilyPond 1.9.8 is released. This is the first LilyPond 2.0 prerelease. Check the @ref{Changes} and download here.
LilyPond 1.9.7 is released. LilyPond now has support for quarter tone accidentals! @ref{Old downloads}
LilyPond 1.9.6 is released. It has a lot of minor fixes and updates. @ref{Old downloads}
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. @ref{Old downloads}
LilyPond 1.8.2 is released. This release fixes a couple of minor bugs. @ref{Old downloads}
LilyPond 1.8 binaries are available for Windows (Cygwin version 1.5). @ref{Old downloads}
LilyPond 1.9.4 is released. This is an experimental release: read the announcement before trying.
LilyPond 1.9.3 is released. This release supports tagging for music version control, and has better fingering placement flexibility. Read the @ref{Changes} and get it here.
The LilyPond 1.9 development release is available. Read the @ref{Changes} and get it here.
Website: present treatise about music engraving, music printing software, and LilyPond’s unique faculties.
1.7.29 - release candidate 4 has been released. Packages for Red Hat, Debian, Cygwin are available.
| [Anfang] | [Inhalt] | [Index] | [ ? ] |
| [Anfang] | [Inhalt] | [Index] | [ ? ] |
Dieses Dokument wurde erzeugt von gub am 13. Juli 2020 durch texi2html 1.82.
Die Links in der Navigationsleiste haben die folgende Bedeutung:
| Button | Name | Gehe zu | Von 1.2.3 gehe zu |
|---|---|---|---|
| [ < ] | Zurück | Voriger Abschnitt in Lesereihenfolge | 1.2.2 |
| [ > ] | Nach vorne | Nächster Abschnitt in Lesereihenfolge | 1.2.4 |
| [ << ] | FastBack | Anfang dieses oder des letzten Kapitels | 1 |
| [ Nach oben ] | Nach oben | Abschnitt nach oben | 1.2 |
| [ >> ] | FastForward | Nächstes Kapitel | 2 |
| [Anfang] | Anfang | Titelseite des Dokuments | |
| [Inhalt] | Inhalt | Inhaltsverzeichnis | |
| [Index] | Index | Index | |
| [ ? ] | Über | Über (Hilfe) |
wobei das Beispiel annimmt, dass die aktuelle Position bei Unterabschnitt 1-2-3 in einem Dokument mit folgender Struktur liegt:
Dieses Dokument wurde erzeugt von gub am 13. Juli 2020 durch texi2html 1.82.
Andere Sprachen: English, català, česky, español, français, magyar, italiano, 日本語, nederlands, Português, 中文.
Über die automatische Sprachauswahl.