In the template, change these lines to define how many octaves your music covers.#(define lower-octave -2).Each system is defined in the chromatic.ly file.)#(define notation-style “6-6-tetragram”) (See below for a list of notation system names that can be entered here. Next edit the following line near the top of the template so it refers to your desired notation.Open the template in any basic text editor and change the following line to refer to your LilyPond music file:\include “bach-invention-09-common.ly”.You will also need a template file like this one: bachinvention09template.ly.You will need a copy of the chromatic.ly file which contains the definitions of various alternative music notation systems.You can also download them from the Mutopia project or other online sources. #Lilypond vs code how toThe LilyPond website explains how to write such files from scratch. You will need a LilyPond music file (.ly) in standard LilyPond format, in a form similar to bachinvention09common.ly.Using LilyPond to transnotate music into an alternative notationĪssuming you have already installed LilyPond, here is how you would use it to transnotate music into an alternative notation. (Both of these approaches are possible because of the code that Dalley contributed to LilyPond.) See the main LilyPond wiki page for more about working more directly with LilyPond rather than using Dalley’s files. It is also possible to use LilyPond for alternative notation systems without using Kevin’s “chromatic.ly” and template files. There are some non-functioning features (see below). Most of the content on this page comes from Dalley’s website, and documents his approach to using LilyPond for alternative notation systems - using his “chromatic.ly” and template files. How to Use Dalley’s “chromatic.ly” Approach Andrew Wagner set up a git repository for the patches and additional files on to help organize and facilitate future work. Mark Hanlon also contributed by updating and maintaining Kevin’s code so that it would continue to work with more recent versions of LilyPond (although it is no longer compatible with newer LilyPond releases). #Lilypond vs code PatchHowever, it has been superseded by a newer patch by another developer that adds this functionality to LilyPond.) (He submitted a patch for internal-ledger-lines but it was never finished. Now most of these patches have been incorporated into Lilypond, as you can see here. He wrote a set of patches (initially for LilyPond version 2.11.0) that provided for basic chromatic staff functionality. Kevin Dalley volunteered his time and skills to add features to LilyPond to support chromatic-staff notation systems. See the main LilyPond wiki page for the most current information. This page documents some earlier important work by Kevin Dalley.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |