LilyPond

LilyPond
Original author(s) Bertrand Bordage, Ian Hulin, Reinhold Kainhofer, Joe Neeman, Neil Puttock, Mike Solomon, Nicolas Sceaux, et. al.[1]
Developer(s) David Kastrup, Werner Lemberg, Han-Wen Nienhuys, Jan Nieuwenhuizen, Carl Sorensen, Janek Warchoł, et. al.[1]
Initial release 1996 (1996)
Stable release 2.18.2 (March 17, 2014 (2014-03-17)[2]) [±]
Preview release 2.19.51 (November 20, 2016 (2016-11-20)[3]) [±]
Repository git.savannah.gnu.org/cgit/lilypond.git
Development status Active
Written in C++, Scheme, Metafont, PostScript, Python[4]
Operating system
Size 20–100 MB
Available in English, Catalan, Dutch, French, German, Hungarian, Italian, Japanese, Spanish
Type Music software, scorewriter
License GPLv3[6]
Website lilypond.org
Standard(s) EPS, MIDI, MusicXML, PDF, PS, SVG

LilyPond is a computer program and file format for music engraving. One of LilyPond's major goals is to produce scores that are engraved with traditional layout rules, reflecting the era when scores were engraved by hand.

LilyPond is cross-platform, and is available for several common operating systems; released under the terms of the GNU General Public License, LilyPond is free software.

History

The LilyPond project was started in 1996 by Han-Wen Nienhuys and Jan Nieuwenhuizen, after they decided to abandon work on MPP (MusiXTeX PreProcessor), a project they began collaborating on in 1995.[7][8] Its name was inspired both by the Rosegarden project and an acquaintance of Nienhuys and Nieuwenhuizen named Suzanne, a name that means lily in Hebrew (שׁוּשָׁן).[9]

Version 1.0

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

Version 2.0

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

Design

LilyPond is mostly written in C++ and uses Scheme (interpreted by GNU Guile) as its extension language, allowing for user customization.[12] It has a relatively large codebase; as of March 21, 2015, the source comprises over 600,000 lines of C++ and 120,000 lines of Scheme and Python code.[13]

Screenshot of LilyPond running on Linux

It uses a simple text notation for music input, which LilyPond interprets and processes in a series of stages.[14] In the final stage, music notation is output to PDF (via PostScript) or other graphical formats, such as SVG or PNG. LilyPond also has the facility to generate MIDI files that correspond to the music notation output.

LilyPond is a text-based application, so it does not contain its own graphical user interface to assist with score creation. It does, however, have a flexible input language that strives to be simple, easing the learning curve for new users. LilyPond adheres to the WYSIWYM paradigm; the workflow for typesetting music notation with LilyPond is similar to that of preparing documents with LaTeX.

LilyPond supports experimental musical notation. Its guitar facilities support alternative tunings, such as major-thirds tuning.[15]

Software features

Symphony No. 5 music sheet printed from a digitally engraved PDF file produced by LilyPond; released by the Mutopia Project

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

Overview of input syntax

The native input language for LilyPond is comprehensive, consisting of many commands needed for expressing any sort of articulation, dynamic, meter, etc. The ability to embed Scheme code within a LilyPond source file permits arbitrary extensions to the input language and assists with algorithmic composition. Some general syntactic features are listed below.

LilyPond's interface with Pango requires the input character encoding to be UTF-8.[23] One benefit of this is that more than one language can be included in the same source file.

Example of LilyPond input file

\version "2.19.22"

\include "english.ly"

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

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

\score {
  \new PianoStaff = "pianostaff" <<
    \new Staff = "RH" \relative c' {
      \accidentalStyle Score.piano
      \clef "treble"
      \time 2/4
      \set Score.currentBarNumber = #51
      \tempo "Slow and steady" 4 = 60
      <e gs,>4 \acciaccatura { cs16[ ds] } <e gs,>4 | % m. 51
      <ds gs,>4 \acciaccatura { e16[ ds] } <cs gs>4 | % m. 52
      <cs gs>4 \acciaccatura { ds16[ cs] } <c g>4  | % m. 53
      <cs gs>4 \acciaccatura { ds16[ e] } <es bs gs>4 | % m. 54

      <e gs,>4 \acciaccatura { cs16[ ds] } e16 f gs a | % m. 55
      <gs c,>8 \acciaccatura { as16[ gs] }
      <es b>8 ~ <es b>16 ds b as | % m. 56

      b16 d8 bf32 f' g16 af bf c | % m. 57
      <df df,>16 ( c af ) <e' e,> ( ds b ) <g' g,> ( ds | % m. 58

      \time 3/4
      <gs gs,>16 ) \noBeam d,16 f gs
      a16 e f b
      c16 d, ( f gs | % m. 59

      a16 b ) e, ( f
      gs16 b c ) f, (
      gs16 as b c ) | % m. 60
    }

    \new Dynamics = "Dynamics_pf" {
      s4 \p \< s4 | % m. 51
      s4 s4 | % m. 52
      s4 \mp \> s4 | % m. 53
      s4 s4 \! | % m. 54
      s4 \p s4 | % m. 55
      s1 * 2/4 | % m. 56
      s4 \< s4 | % m. 57
      s4 s4 | % m. 58
      \override DynamicText.extra-spacing-width = #'(-0.75 . 0.75)
      s16 \mf s16 \p s8 s4 s4 | % m. 59
      s2. | % m. 60
    }

    \new Staff = "LH" \relative c, {
      \clef "bass"
      \time 2/4
      cs4. cs8 | % m. 51
      cs4. d8 | % m. 52
      f4. a8 | % m. 53
      f4. d8 | % m. 54

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

      \time 3/4
      d4. d8 ~ d4 | % m. 59
      ef2 f4 | % m. 60
    }
  >>
}

Corresponding output

More complex output

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

Collaboration with other projects

First measures of Adeste Fideles, generated by LilyPond.

Several graphical scorewriters—such as Rosegarden, NoteEdit, Canorus, Denemo, and TuxGuitar—can export files directly to LilyPond format. Other graphical applications serve as front ends to LilyPond, including Frescobaldi and the LilyPondTool plugin for jEdit. Denemo integrates the PDF output of LilyPond in its display, allowing some editing operations on the final typeset score.

The Mutopia Project, which distributes free content sheet music, uses LilyPond to typeset its music, as does Musipedia, a collaborative music encyclopedia.

Emacs' org-mode contains support for embedding LilyPond scores into documents.[24]

Integration into MediaWiki

Lilypond is available in MediaWiki via the Score extension code. This, for example, transforms the notation

<score vorbis="1">\relative c' { f d f a d f e d cis a cis e a g f e }</score>

into

\relative c' { f d f a d f e d cis a cis e a g f e }

The above excerpt is a simplified version of Solfeggio in C Minor by C.P.E. Bach. More complex scores, including lyrics, are also possible within MediaWikis. See Pastime with Good Company for an example.

Comparison to other scorewriters

Finale and Sibelius are two proprietary scorewriters often compared to LilyPond. Andrew Hawryluk, a LilyPond user, wrote a series of articles comparing output quality between Finale and LilyPond.[25]

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

See also

References

  1. 1 2 "Authors". LilyPond Development team. Retrieved 2015-03-21.
  2. ↑ Holmes, Phil (2014-03-17). "LilyPond 2.18.2 released" (Mailing list). info-lilypond.
  3. ↑ "LilyPond – Music notation for everyone". November 20, 2016. Retrieved November 20, 2016.
  4. ↑ "Source tarball". lilypond.org. Retrieved 4 March 2016.
  5. ↑ "Downloads for LilyPond 2.18.2". lilypond.org. Retrieved 4 March 2016.
  6. ↑ COPYING
  7. ↑ "GNU LilyPond Learning Manual: Preface". Retrieved 2015-03-21.
  8. ↑ "MusiXTeX PreProcessor README". Retrieved 2010-03-31.
  9. ↑ Kroger, Pedro (2004). "Re: The origin of the name lilypond". lilypond-user mailing list. lists.gnu.org. Archived from the original on 8 Sep 2004. Retrieved 19 March 2014.
  10. ↑ Nienhuys, Han-Wen (1998-07-31). "GNU LilyPond 1.0 released". gnu-music-discuss (Mailing list). Retrieved 2010-02-16.
  11. ↑ Nienhuys, Han-Wen (2003-09-24). "LilyPond 2.0 – make beautiful music prints". info-lilypond (Mailing list). Retrieved 2010-02-16.
  12. ↑ "LilyPond programming languages". Retrieved 2015-03-21.
  13. ↑ "GNU LilyPond Music Typesetter – Code Analysis". Retrieved 2015-03-21.
  14. ↑ "Overview of LilyPond architecture". Retrieved 2015-03-21.
  15. ↑ Griewank, Andreas (1 January 2010), Tuning guitars and reading music in major thirds, Matheon preprints, 695, Rosestr. 3a, 12524 Berlin, Germany: DFG research center "MATHEON, Mathematics for key technologies" Berlin
  16. ↑ Nienhuys, Han-Wen; Nieuwenhuizen, Jan. "Obsessed with putting ink on paper". Retrieved 2010-02-15.
  17. ↑ "Proportional notation". Retrieved 2015-03-21.
  18. ↑ "LilyPond Learning Manual: 1.2.2 Working on input files". Retrieved 2015-03-21.
  19. ↑ "LilyPond Notation Reference: 1.1.1 Writing pitches". Retrieved 2015-03-21.
  20. ↑ "LilyPond Notation Reference: 1.3.1 Expressive marks attached to notes". Retrieved 2015-03-21.
  21. ↑ "LilyPond Notation Reference: 1.3.2 Expressive marks as curves". Retrieved 2015-03-21.
  22. ↑ "LilyPond Notation Reference: 1.2.4 Beams". Retrieved 2015-03-21.
  23. ↑ "LilyPond Notation Reference: 3.3.3 Text encoding". Retrieved 2015-03-21.
  24. ↑ github.com
  25. ↑ Hawryluk, Andrew. "Finale and LilyPond". Retrieved 2010-02-15.

External links

This article is issued from Wikipedia - version of the 10/28/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.