Franco Pasut Blog

Table of Contents 1. A Very Brief Introduction 2. What are note stems? 3. Stem Handling in Polyphonic Notation 4. Musical Examples 5. The quick construction 6. Example of a more detailed quick construct 1. A Very Brief Introduction I’ve finally understood the “logic” behind LilyPond’s syntax as it relates to the different ways of writing multiple voices. I’m writing down my “discovery” right away before I forget it—after all, that’s exactly what this “blog” is for! Polyphony is a compositional technique in which several independent melodic lines are layered and performed simultaneously, creating a sonic texture in which each voice retains its autonomy while harmonizing with the others. The evolution of polyphony marked the transition from a linear conception of music (e.g., Gregorian monody) to one based on architectural complexity (e.g., counterpoint). LilyPond handles polyphony excellently, even on the same staff, as is the case with the piano. Whe...

Table of Contents 1. LilyPond, extracting score fragments: a detailed guide 2. Output format: PDF and PNG. 3. Extracting a fragment from the beginning of a score 4. Increasing Image Resolution 5. Quickly Exporting a Snippet 1. LilyPond, extracting score fragments: a detailed guide This article was written using LilyPond version 2.24.4 and refers to page 3.5.1 of the official manual . The page provides correct but incomplete instructions: the code is incomplete because the musical portion is missing. Starting from the example in the manual but simplifying the musical parameters, I have written a complete template that includes a musical fragment. The template extracts a fragment from the input file that begins after the first half note in the second measure (2 1 4) and ends after the first half note in the third measure (3 1 4). \version "2.24.4" \layout { clip-regions = #(list (cons (make-rhythmic-location 2 1 4) (make-rhy...

Table of Contents 1. Why Nano? 2. Pasting from the clipboard 3. Moving between lines 4. Plugins or no plugins? 5. Setting as the default editor 6. Why NOT Nano? 1. Why Nano? Nano is a command line text editor, known for being one of the simplest and most intuitive available in the GNU/Linux world. It is found in most Linux distributions and is a tool that anyone can use “at first glance.” At the bottom of the screen is a description of the most commonly used commands, where the symbol ^ represents the Ctrl key and the symbol “M” indicates the Alt key (which was once called Meta and is still called that in Emacs). For example: ^O means: press Ctrl + O to save the current document. Another example: M-U means: press Alt + U to undo the last command. The Ctrl + Enter key activates the links contained within the documents opened in Nano. Here is the “main menu” in English: The wider the terminal window, the more commands are displayed. ...