From c1055f6d1e3fc4247ba7f621d77e07410bd8b722 Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Sun, 20 Dec 2020 00:30:11 -0500 Subject: Add times --- 2020/info/04.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to '2020/info') diff --git a/2020/info/04.md b/2020/info/04.md index 16d2d28e..303cb2a0 100644 --- a/2020/info/04.md +++ b/2020/info/04.md @@ -77,7 +77,7 @@ pond of lilies and Lilypond, and move on to showcase some of its functionalities using Org Mode and lilypond-mode. One disclaimer, however: I am not a Lilypond developer. -So what is Lilypond? Lilypond is a file format and music engraving +(00:40) So what is Lilypond? Lilypond is a file format and music engraving system for producing high-quality sheet music. It translates textual representations of music to graphical objects. It's similar to LaTeX in that its input format describes the visual layouts of the score, @@ -92,7 +92,7 @@ and so on. Above all, it works with Emacs. In fact, Lilypond ships with Emacs Lisp libraries, including a major mode for editing Lilypond files. -So the input files are similar to source files. They contain +(01:47) So the input files are similar to source files. They contain expressions formed with curly braces, comments that start with the percent sign, and the code is indented. Notes are entered using lowercase letters, and rests with the letter r. In this case, the @@ -105,13 +105,13 @@ you to read the manual for more information. Now let's switch to a terminal window. With Lilypond installed, let's create a test file with the extension .ly and open it in Emacs. -At the top of the file is the version statement, which tells Lilypond +(02:50) At the top of the file is the version statement, which tells Lilypond which version to use when compiling the file. Here I'm using version 2.20.0. I've added the clef and time signature. Let's add some notes. I'm going to close this now and compile the file by running lilypond followed by the file name. So now let's view the output. Okay. -So here's a more complex example for randomizing note sequences. The +(03:27) So here's a more complex example for randomizing note sequences. The idea is to create new reading materials each time the code blocks are evaluated. As usual, we begin with a header. I've added the title and composer. Then we add the note sequences to use in the composition. In @@ -124,19 +124,19 @@ view the results. Okay. And if I run this again, it should create a new composition. Great. You can also audition a piece using the midi command, which creates a midi file of the score. -Note also that the ob library-- sorry, the ob-lilypond library comes +(04:34) Note also that the ob library-- sorry, the ob-lilypond library comes with two modes. The one I'm using now is called arrange mode and is useful for assembling complete scores. The basic mode on the other hand allows you to mix text and music by embedding Lilypond snippets and export them using typical Org Mode commands. -Now to demonstrate the basic mode in action. I'm going to export this +(05:00) Now to demonstrate the basic mode in action. I'm going to export this document to a PDF file. In this case, the :file header argument is required, so you have to provide one and include the file name. Again, you can run the code and view the results. Here it is. So now let's export this to a PDF file. And here it is, what it generates. -Now I'm going to show you the workflow I used to produce music books +(05:39) Now I'm going to show you the workflow I used to produce music books in Emacs, combining Lilypond and LaTeX for a perfect marriage. I begin by sketching the first draft of the manuscript using pencil and paper. Then I move to Emacs to input the notes in a git repository. This is a @@ -150,7 +150,7 @@ files and building the PDF, I use GNU Make, so all I have to do is open the shell and run the make command. Don't worry, I'll provide a link to the source code on the last slide. -As I moved forward with the project, I found at least two things +(06:41) As I moved forward with the project, I found at least two things missing. One, I had no access to a metronome, at least not from the editor, so I built one for casual use and made it available in the MELPA repository. I also missed bar numbers in the source file. This @@ -161,7 +161,7 @@ difficult or slow to write on the keyboard-- accents and tuplets, for example--so I use template expansion extensively for this purpose, mainly yasnippet. -So what do I think? Well, I think Lilypond can be a +(07:23) So what do I think? Well, I think Lilypond can be a sharp paradigm shift for people used to GUI alternatives, but the results are impressive. You don't have to dive too deeply to start using Lilypond. Likewise, the ability to extend the software, I think, -- cgit v1.2.3