LilyPond 2.11.61-1 Beta / 2.10.33-1

LilyPond is an automated engraving system. It formats music beautifully and automatically.
It has a friendly syntax for its input files.

Main features:>
- Music language input.
- The input is done in the form of a textual music language.
- Entry may be done with the text editor of your choice, and using the national language of your choice.
- The ASCII input language can integrate with TeX, HTML and Texinfo, thus allowing musicological treatises to be written from a single source.
- The music and its layout are strictly separated, so score and parts (possibly in different styles and keys) and scores can be generated from the same source, and changes always take effect in both places.
- The output can be improved by upgrading the program.
- Pieces can be printed in different (typographical) house styles, or according to different notational conventions.
- Automated high-quality formatting.
- Automatic spacing, line breaking and page breaking.
- Handling of polyphonic collisions for notes, dots, and rests.
- Automatic placement of accidentals, beams, slurs.
- Users dont need typographical expertise to produce good notation.
- No user interaction necessary during running, Running the program can be automated, which is convenient for mass converting databases of digitized music, and printing algorithmic compositions.
- The Feta font has been tailored especially for LilyPond, and was designed carefully mimicking the finest hand-engraved scores. It is available as a scalable font, but also as a Metafont.
- Support for many notation constructs.
- Special notation
- Chord names.
- Drum notation.
- Figured bass.
- Grace notes.
- Fret diagrams.
- Basic tablature notation.
- Cluster notation and rhythmic grouping signs.
- Tremolos, both for single notes and chords.
- Tuplets in arbitrary ratios.
- Polymetric notation.
- Mensural notation.
- Automatic cue-notes,.
- Automatic part combining for orchestral scores.
- Quarter tone accidentals.
- Ambituses.
- Metronome markings.
- Harmonics.
- Measure repeats (percent style).
- EasyNotation note heads.
- Blanking arbitrary notation elements.
- Arpeggio signs.
- Ottava brackets.
- Nested analysis brackets.
- Piano pedals.
- Starting and stopping staves anywhere
- System separators
- Robust design
- Lyrics in any language.
- Output in PostScript, PDF, PNG, MIDI, SVG.
- No limits on the number of staves, voices, measures, lengths of texts, etc.
- Extensible with built-in LISP interpreter.
- Excellent support
- Runs on Unix, including MacOS X and Linux, and Windows.
- Active user community.
- Extensive documentation.
- Supported by many other programs,
- RoseGarden NoteEdit and PowerTab and Denemo.
- Imports ABC, ETF and MIDI.

Enhancements:
- setEasyHeads has been renamed to easyHeadsOn, and a new command easyHeadsOff reverts note heads to normal heads.
- fatText and emptyText have been renamed to extLengthOn and extLengthOff, respectively.
- Underlining is now possible with the underline markup command.
- It is now possible to specify, using the page-count variable in the paper block, the number of pages that will be used.
- A new page breaking function, ly:minimal-breaking, is dedicated to books with many pages or a lot of texts.
- A table of contents is included using markuplines able-of-contents. Elements are added to it using the ocItem command.
- Text spreading over several pages is entered using the markuplines keyword. Builtin markup list commands, such as justified-lines or wordwrap-lines may be used, and new ones created using the define-markup-list-command Scheme macro.
- Particular points of a book may be marked with the label command. Then, the page where these points are placed can be refered to using the page-ref markup command.
- Page breaking and page turning commands (pageBreak,
- oPageBreak, etc) can be used at top-level, between scores and top-level markups.
- The following options are now changed as a -d sub-option: --backend, --safe, --preview and --no-pages (which became -dno-print-pages). The -b option does not exist any more.
- Improved testing procedure now catch changes in CPU and memory performance, page layout, MIDI results and warnings. This helps to reduce the number of regression errors during development, resulting in more stable releases.