Lilypond Learning Manual

Total Page:16

File Type:pdf, Size:1020Kb

Lilypond Learning Manual ☛ ✟ ✡ ✠ ☛ ✟ ✡ ✠ The music typesetter This file provides an introduction to LilyPond version 2.19.84. For more information about how this manual fits with the other documentation, or to read this manual in other formats, see Section “Manuals” in General Information. If you are missing any manuals, the complete documentation can be found at http://lilypond.org/. Copyright ⃝c 1998–2015 by the authors. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections. A copy of the license is included in the section entitled “GNU Free Documentation License”. For LilyPond version 2.19.84 The LilyPond development team LilyPond Learning Manual i 1.1 Compiling a file ................................................... ................. 1 1.1.1 Entering input ................................................... ............. 1 Producing output ................................................... .............. 1 1.1.2 MacOS X ................................................... .................. 2 1.1.3 Windows................................................... ................... 6 1.1.4 Command-line ................................................... ............ 11 1.2 How to write input files ................................................... ........ 12 1.2.1 Simple notation ................................................... ........... 12 Pitches ................................................... ....................... 12 Durations (rhythms) ................................................... .......... 14 Rests ................................................... ......................... 15 Time signature ................................................... ............... 15 Tempo marks ................................................... ................. 15 Clef ................................................... .......................... 16 All together ................................................... .................. 16 1.2.2 Working on input files ................................................... .... 16 1.3 Dealing with errors ................................................... ............ 18 1.3.1 General troubleshooting tips ................................................. 18 1.3.2 Some common errors ................................................... ...... 18 1.4 How to read the manuals ................................................... ...... 18 1.4.1 Omitted material ................................................... ......... 18 1.4.2 Clickable examples ................................................... ........ 18 1.4.3 Overview of manuals ................................................... ...... 19 2.1 Single staff notation ................................................... ........... 20 2.1.1 Bar lines and bar checks ................................................... .. 20 Bar lines ................................................... ..................... 20 Bar checks................................................... .................... 20 2.1.2 Pitches and key signatures ................................................... 20 Pitch alterations ................................................... .............. 21 Key signatures................................................... ................ 21 Warning: key signatures and pitches ............................................. 21 2.1.3 Ties and slurs................................................... ............. 22 Ties ................................................... .......................... 22 Slurs ................................................... ......................... 23 Phrasing slurs ................................................... ................ 23 Warnings: slurs vs. ties ................................................... ....... 23 2.1.4 Articulations and dynamics .................................................. 23 Articulations ................................................... ................. 24 Fingerings ................................................... .................... 24 Dynamics................................................... ..................... 24 2.1.5 Adding text................................................... ............... 25 2.1.6 Automatic and manual beams ................................................ 25 2.1.7 Advanced rhythmic commands ............................................... 26 Partial measure ................................................... ............... 26 Tuplets ................................................... ....................... 26 1 Tutorial ................................................... ...... 1 2 Common notation............................................. 20 Table of Contents ii Grace notes................................................... ................... 27 2.2 Multiple notes at once ................................................... ......... 27 2.2.1 Music expressions explained .................................................. 27 Analogy: mathematical expressions .............................................. 28 Simultaneous music expressions: multiple staves .................................. 28 Simultaneous music expressions: single staff ...................................... 28 2.2.2 Multiple staves................................................... ............ 29 2.2.3 Staff groups................................................... ............... 30 2.2.4 Combining notes into chords ................................................. 30 2.2.5 Single staff polyphony................................................... ..... 31 2.3 Songs................................................... .......................... 31 2.3.1 Setting simple songs ................................................... ...... 31 2.3.2 Aligning lyrics to a melody................................................... 32 2.3.3 Lyrics to multiple staves ................................................... .. 35 2.4 Final touches ................................................... .................. 36 2.4.1 Organizing pieces with variables.............................................. 36 2.4.2 Adding titles................................................... .............. 37 2.4.3 Absolute note names ................................................... ...... 38 2.4.4 After the tutorial ................................................... ......... 39 3.1 How LilyPond input files work ................................................... 41 3.1.1 Introduction to the LilyPond file structure.................................... 41 3.1.2 Score is a (single) compound musical expression .............................. 43 3.1.3 Nesting music expressions ................................................... 45 3.1.4 Structure of a note entry ................................................... .. 46 3.1.5 On the un-nestedness of brackets and ties .................................... 47 3.2 Voices contain music ................................................... ........... 48 3.2.1 I’m hearing Voices ................................................... ........ 48 3.2.2 Explicitly instantiating voices ................................................ 53 3.2.3 Voices and vocals ................................................... ......... 57 3.3 Contexts and engravers ................................................... ........ 60 3.3.1 Contexts explained................................................... ........ 60 3.3.2 Creating contexts ................................................... ......... 61 3.3.3 Engravers explained................................................... ....... 63 3.3.4 Modifying context properties ................................................. 64 3.3.5 Adding and removing engravers .............................................. 68 3.4 Extending the templates ................................................... ....... 71 3.4.1 Soprano and cello ................................................... ......... 71 3.4.2 Four-part SATB vocal score .................................................. 74 3.4.3 Building a score from scratch................................................. 80 3.4.4 Saving typing with variables and functions ................................... 85 3.4.5 Scores and parts ................................................... .......... 87 4.1 Tweaking basics ................................................... ............... 89 4.1.1 Introduction to tweaks ................................................... .... 89 4.1.2 Objects and interfaces ................................................... .... 89 4.1.3 Naming conventions of objects and properties ................................ 90 4.1.4 Tweaking methods ................................................... ........ 90 The \override command................................................... ..... 90 The \revert command ................................................... ....... 91 The \once prefix ................................................... ............. 92 3 Fundamental concepts ........................................ 41 4 Tweaking output .............................................. 89 iii The \overrideProperty command .............................................. 92 The \tweak command ................................................... ........ 92 The \single prefix ..................................................
Recommended publications
  • Sibelius Artwork Guidelines Contents
    Sibelius Artwork Guidelines Contents Conditions of use ...........................................................................................................................3 Important information ..................................................................................................................4 Product names and logos.............................................................................................................5 Example copy..................................................................................................................................6 Endorsees ........................................................................................................................................7 Reviews............................................................................................................................................8 Awards...........................................................................................................................................11 House Style ...................................................................................................................................12 Conditions of use Who may use this material Authorized Sibelius distributors and dealers are permitted to reproduce text and graphics on this CD in order to market Sibelius products or PhotoScore, but only if these guidelines are adhered to, and all artwork is used unmodified and cleared by Sibelius Software before production of final proofs. Acknowledge trademarks Please
    [Show full text]
  • Scanscore 2 Manual
    ScanScore 2 Manual Copyright © 2020 by Lugert Verlag. All Rights Reserved. ScanScore 2 Manual Inhaltsverzeichnis Welcome to ScanScore 2 ..................................................................................... 3 Overview ...................................................................................................... 4 Quickstart ..................................................................................................... 4 What ScanScore is not .................................................................................... 6 Scanning and importing scores ............................................................................ 6 Importing files ............................................................................................... 7 Using a scanner ............................................................................................. 7 Using a smartphone ....................................................................................... 7 Open ScanScore project .................................................................................. 8 Multipage import ............................................................................................ 8 Working with ScanScore ..................................................................................... 8 The menu bar ................................................................................................ 8 The File Menu ............................................................................................ 9 The
    [Show full text]
  • Integrating Paper and Digital Music Information Systems Karen Lin and Tim Bell University of Canterbury, Christchurch, New Zealand
    Integrating Paper and Digital Music Information Systems Karen Lin and Tim Bell University of Canterbury, Christchurch, New Zealand Abstract Active musicians generally rely on extensive personal paper-based music information retrieval systems containing scores, parts, compositions, and arrangements of published and hand-written music. Many have a bias against using computers to store, edit and retrieve music, and prefer to work in the paper domain rather than using digital documents, despite the flexibility and powerful retrieval opportunities available. In this paper we propose a model of operation that blurs the boundaries between the paper and digital domains, offering musicians the best of both worlds. A survey of musicians identifies the problems and potential of working with digital tools, and we propose a system using colour printing and scanning technology that simplifies the process of moving music documents between the two domains. Keywords : user interfaces, user needs, optical music recognition 1. Introduction Traditionally musicians have stored and retrieved music scores using paper-based systems. Many musicians have built up personal libraries of music books, compositions, arrangements and sheet music. The acquisition or creation of documents is straightforward, but the retrieval or modification of scores is hindered by the inflexibility of the paper medium. A digital music library would have a number of benefits, including convenient retrieval (instead of searching through piles of music), ease of processing (such as part extraction), and communication (sending electronic copies to other performers). However working with digital documents also poses significant barriers for users more familiar with traditional paper documents. In this paper we explore the relationship between the paper and digital domains, and the possibility of allowing easy conversion between the two to allow documents to exist in both domains and be processed in whichever domain is the most convenient.
    [Show full text]
  • Musical Notation Codes Index
    Music Notation - www.music-notation.info - Copyright 1997-2019, Gerd Castan Musical notation codes Index xml ascii binary 1. MidiXML 1. PDF used as music notation 1. General information format 2. Apple GarageBand Format 2. MIDI (.band) 2. DARMS 3. QuickScore Elite file format 3. SMDL 3. GUIDO Music Notation (.qsd) Language 4. MPEG4-SMR 4. WAV audio file format (.wav) 4. abc 5. MNML - The Musical Notation 5. MP3 audio file format (.mp3) Markup Language 5. MusiXTeX, MusicTeX, MuTeX... 6. WMA audio file format (.wma) 6. MusicML 6. **kern (.krn) 7. MusicWrite file format (.mwk) 7. MHTML 7. **Hildegard 8. Overture file format (.ove) 8. MML: Music Markup Language 8. **koto 9. ScoreWriter file format (.scw) 9. Theta: Tonal Harmony 9. **bol Exploration and Tutorial Assistent 10. Copyist file format (.CP6 and 10. Musedata format (.md) .CP4) 10. ScoreML 11. LilyPond 11. Rich MIDI Tablature format - 11. JScoreML RMTF 12. Philip's Music Writer (PMW) 12. eXtensible Score Language 12. Creative Music File Format (XScore) 13. TexTab 13. Sibelius Plugin Interface 13. MusiXML: My own format 14. Mup music publication program 14. Finale Plugin Interface 14. MusicXML (.mxl, .xml) 15. NoteEdit 15. Internal format of Finale (.mus) 15. MusiqueXML 16. Liszt: The SharpEye OMR 16. XMF - eXtensible Music 16. GUIDO XML engine output file format Format 17. WEDELMUSIC 17. Drum Tab 17. NIFF 18. ChordML 18. Enigma Transportable Format 18. Internal format of Capella (ETF) (.cap) 19. ChordQL 19. CMN: Common Music 19. SASL: Simple Audio Score 20. NeumesXML Notation Language 21. MEI 20. OMNL: Open Music Notation 20.
    [Show full text]
  • Downloads." the Open Information Security Foundation
    Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing
    [Show full text]
  • GNU Wget 1.10 the Non-Interactive Download Utility Updated for Wget 1.10, Apr 2005
    GNU Wget 1.10 The non-interactive download utility Updated for Wget 1.10, Apr 2005 by Hrvoje Nikˇsi´cand the developers Copyright c 1996–2005, Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License” and “GNU Free Documentation License”, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Overview 1 1 Overview GNU Wget is a free utility for non-interactive download of files from the Web. It supports http, https, and ftp protocols, as well as retrieval through http proxies. This chapter is a partial overview of Wget’s features. • Wget is non-interactive, meaning that it can work in the background, while the user is not logged on. This allows you to start a retrieval and disconnect from the system, letting Wget finish the work. By contrast, most of the Web browsers require constant user’s presence, which can be a great hindrance when transferring a lot of data. • Wget can follow links in html and xhtml pages and create local versions of remote web sites, fully recreating the directory structure of the original site. This is sometimes referred to as “recursive downloading.” While doing that, Wget respects the Robot Exclusion Standard (‘/robots.txt’). Wget can be instructed to convert the links in downloaded html files to the local files for offline viewing.
    [Show full text]
  • Name Synopsis Description Options
    GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) NAME gpgtar −Encrypt or sign files into an archive SYNOPSIS gpgtar [options] filename1 [ filename2, ... ] directory1 [ directory2, ... ] DESCRIPTION gpgtar encrypts or signs files into an archive.Itisangpg-ized tar using the same format as used by PGP’s PGP Zip. OPTIONS gpgtar understands these options: --create Put givenfiles and directories into a vanilla ‘‘ustar’’archive. --extract Extract all files from a vanilla ‘‘ustar’’archive. --encrypt -e Encrypt givenfiles and directories into an archive.This option may be combined with option --symmetric for an archive that may be decrypted via a secret key orapassphrase. --decrypt -d Extract all files from an encrypted archive. --sign -s Makeasigned archive from the givenfiles and directories. This can be combined with option --encrypt to create a signed and then encrypted archive. --list-archive -t List the contents of the specified archive. --symmetric -c Encrypt with a symmetric cipher using a passphrase. The default symmetric cipher used is AES-128, but may be chosen with the --cipher-algo option to gpg. --recipient user -r user Encrypt for user id user.For details see gpg. --local-user user -u user Use user as the key tosign with. Fordetails see gpg. --output file -o file Write the archive tothe specified file file. --verbose -v Enable extra informational output. GnuPG 2.2.12 2018-12-11 1 GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) --quiet -q Trytobeasquiet as possible. --skip-crypto Skip all crypto operations and create or extract vanilla ‘‘ustar’’archives. --dry-run Do not actually output the extracted files.
    [Show full text]
  • With Yocto/Openembedded
    PORTING NEW CODE TO RISC-V WITH YOCTO/OPENEMBEDDED Martin Maas ([email protected]) 1st RISC-V Workshop, January 15, 2015 Monterey, CA WHY WE NEED A LINUX DISTRIBUTION • To build an application for RISC-V, you need to: – Download and build the RISC-V toolchain + Linux – Download, patch and build application + dependencies – Create an image and run it in QEMU or on hardware • Problems with this approach: – Error-prone: Easy to corrupt FS or get a step wrong – Reproducibility: Others can’t easily reuse your work – Rigidity: If a dependency changes, need to do it all over • We need a Linux distribution! – Automatic build process with dependency tracking – Ability to distribute binary packages and SDKs 2 RISCV-POKY: A PORT OF THE YOCTO PROJECT • We ported the Yocto Project – Official Linux Foundation Workgroup, supported by a large number of industry partners – Part I: Collection of hundreds of recipes (scripts that describe how to build packages for different platforms), shared with OpenEmbedded project – Part II: Bitbake, a parallel build system that takes recipes and fetches, patches, cross-compiles and produces packages (RPM/DEB), images, SDKs, etc. • Focus on build process and customizability 3 GETTING STARTED WITH RISCV-POKY • Let’s build a full Linux system including the GCC toolchain, Linux, QEMU + a large set of packages (including bash, ssh, python, perl, apt, wget,…) • Step I: Clone riscv-poky: git clone [email protected]:ucb-bar/riscv-poky.git • Step II: Set up the build system: source oe-init-build-env • Step III: Build an image (may
    [Show full text]
  • Power Tab Editor ❍ Appendix B - FAQ - a Collection of Frequently Asked Questions About the Power Tab Editor
    Help Topics ● Introduction - Program overview and requirements ● What's New? - Program Version history; what was fixed and/or added in each version of the program ● Quick Steps To Creating A New Score - A simple guide to creating a Power Tab Score ● Getting Started ❍ Toolbars - Information on showing/hiding toolbars ❍ Creating A New Power Tab File - Information on how to create a new file ❍ The Score Layout - Describes how each Power Tab Score is laid out ❍ Navigating In Power Tab - Lists the different ways that you can traverse through a Power Tab score. ❍ The Status Bar - Description of what each pane signifies in the status bar. ● Sections and Staves ❍ What Is A Section? - Information on the core component used to construct Power Tab songs ❍ Adding A New Section - Information on how to add a new section to the score ❍ Attaching A Staff To A Section - Describes how attach a staff to a section so multiple guitar parts can be transcribed at the same time ❍ Changing The Number Of Tablature Lines On A Staff - Describes how to change the number of tablature staff lines on an existing staff ❍ Inserting A New Section - Describes how to insert a section within the score (as opposed to adding a section to the end of a score) ❍ Removing A Section Or Staff - Describes how to remove a section or staff from the score ❍ Position Width and Line Height - Describes how to change the width between positions and the distance between lines on the tablature staves ❍ Fills - Not implemented yet ● Song Properties ❍ File Information - How to edit the score
    [Show full text]
  • Replacing PGP 2.X with Gnupg
    Replacing PGP 2.x with GnuPG This article is based on an earlier PGP 2.x/GnuPG compatability guide (http://www.toehold.com/~kyle/pgp- compat.html) written by Kyle Hasselbacher (<[email protected]>). Mike Ashley (<[email protected]>) edited and expanded it. Michael Fischer v. Mollard (<[email protected]>) transformed the HTML source to Doc- Book SGML and also expanded it further. Some of the details described here came from the gnupg-devel and gnupg-user mailing lists. The workaround for both signing with and encrypting to an RSA key were taken from Gero Treuner’s compatability script (http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/changes.html). Please direct questions, bug reports, or suggesstions to the maintainer, Mike Ashley. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 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". Introduction This document describes how to communicate with people still using old versions of PGP 2.x GnuPG can be used as a nearly complete replacement for PGP 2.x. You may encrypt and decrypt PGP 2.x messages using imported old keys, but you cannot generate PGP 2.x keys. This document demonstrates how to extend the standard distribution of GnuPG to support PGP 2.x keys as well as what options must be used to ensure inter- operation with PGP 2.x users.
    [Show full text]
  • Lilypond Cheatsheet
    LilyPond-MusicTypesetting Basic usage - LilyPond Version 2.14 and above Cheatsheet by R. Kainhofer, Edition Kainhofer, http://www.edition-kainhofer.com/ Command-line usage General Syntax lilypond [-l LOGLEVEL] [-dSCMOPTIONS] [-o OUTPUT] [-V] FILE.ly [FILE2.ly] \xxxx function or variable { ... } Code grouping Common options: var = {...} Variable assignment --pdf, --png, --ps Output file format -dpreview Cropped “preview” image \version "2.14.0" LilyPond version -dbackend=eps Use different backend -dlog-file=FILE Create .log file % dots Comment -l LOGLEVEL ERR/WARN/PROG/DEBUG -dno-point-and-click No Point & Click info %{ ... %} Block comment -o OUTDIR Name of output dir/file -djob-count=NR Process files in parallel c\... Postfix-notation (notes) -V Verbose output -dpixmap-format=pngalpha Transparent PNG #'(..), ##t, #'sym Scheme list, true, symb. -dhelp Help on options -dno-delete-intermediate-files Keep .ps files x-.., x^.., x_.. Directions Basic Notation Creating Staves, Voices and Groups \version "2.15.0" c d e f g a b Note names (Dutch) SMusic = \relative c'' { c1\p } Alterations: -is/-es for sharp/flat, SLyrics = \lyricmode { Oh! } cis bes as cisis beses b b! b? -isis/-eses for double, ! forces, AMusic = \relative c' { e1 } ? shows cautionary accidental \relative c' {c f d' c,} Relative mode (change less than a \score { fifth), raise/lower one octave \new ChoirStaff << \new Staff { g1 g2 g4 g8 g16 g4. g4.. durations (1, 2, 4, 8, 16, ...); append “.” for dotted note \new Voice = "Sop" { \dynamicUp \SMusic
    [Show full text]
  • Using Smartscore 2.Pdf
    Using SmartScore Scanning Music Be sure you have the necessary scanner drivers installed before attempting to scan from inside SmartScore. Most scanners come with software that enable programs such as SmartScore to control them. TWAIN drivers and/or Mac plug-ins are normally included in the software packaged with most scanners. It may be necessary for certain Mac users to perform a “Custom > TWAIN” installation from the CD accompanying your scan- ner; depending on the manufacturer. NOTE: Scanner drivers are often updated by scanner manufacturers and posted on their web sites. If problems occur during scanning, it is always a good idea to check the Internet for updated scanner drivers before calling Musitek Technical Support. Mac Users: Skip the next section. Turn to “Scanning in Macintosh” on page 6. Scanning in Windows: Using the SmartScore Scanning Interface a. Push the Scan button in the Navigator or in the Main Toolbar. Figure 1: Scan Button b. If there is no response, go to File > Scan Music > Select Scanner and choose appropriate TWAIN driver. If you do not see anything listed in the Select Scanner window, your drivers are probably not installed. Install or replace TWAIN driver from scanner CD or from “Driver Download” area of scanner manufacturer’s website. c. If the scanner still does not operate properly, go to “Choosing an alternative scanning interface” on page 5. USING SmartScore 1 Help > Using SmartScore Your scanner should immediately begin to operate with Scan or Acquire. A low-resolution pre-scan should soon appear in the Preview window. FIGURE 2: SmartScore scanning interface d.
    [Show full text]