1 %% 11:49 AM Wednesday, December 28, 2022
2 %% Yukio Yoshida
3 %% Location; C:\yukio\sheet-poem.com\lilypond\2022
4 %% This is texinfo's file // TeX run==> pdf / makeinfo run===>html
5 %% So, linux running Only. // Windows-TeX does not has makeinfo.
6 %% html===>name.ly // pdf===>pname.ly
7 %% Web<===Up;html//run ./run--texi.sh
8 \input colordvi.tex
9 \font\cmbBIG=cmr10 at 60pt
10 \font\BigBf=cmr10 at 48pt
11 \font\bigcm=cmr10 at 38truept
12 \font\largcmb=cmbx10 at 14truept
13 \font\largcmbxs=cmbxsl10 at 14truept
14 \font\ninerm=cmr9
15 \font\eightrm=cmr8
16 \font\eightit=cmmi8
17 \font\eighttt=cmtt8
18 \font\seventt=cmtt10 at 7pt
19 \font\sevencmsy=cmsy10 at 7pt
20 \font\ninett=cmtt9
21 \font\ninecmsy=cmsy9
22 \font\fivett=cmtt10 at 5pt
23 \voffset -.6in
24 %%%%%%%%% Start; Texinfo %%%%%%%%%%%%%%%%
25 \input texinfo
26
27
28 @setfilename invitation.info
29 @settitle Invitation
30 @documentlanguage en
31 @documentencoding utf-8
32 @setchapternewpage odd
33
34
35 @iftex
36 @letterpaper
37 @finalout
38 @end iftex
39
40
41
42 @titlepage
43 @c -------------pdf titlepage part #1 -------------------------------------------
44 @iftex
45 @tex
46 \vskip 4pc
47 \centerline {\Red{\cmbBIG Invitation}}
48 \kern 5pt
49 \centerline {\Red{\bigcm Write a Score//Music Notation}}
50 \kern 5pt
51 \centerline {\Red{\bigcm Use LilyPond}}
52 \kern 2pc
53 \centerline {\bigcm On}
54 \kern 2pt
55 \centerline {\cmbBIG WSL}
56 %% \centerline {GNU/Linux 4.4.0-19041-Microsoft x86\_64}
57 \centerline {GNU/Linux 5.10.16.3-microsoft-standard-WSL2 x86\_64}
58 \centerline {(Windows 11 \& Linux)}
59 \vfill
60 @end tex
61 @vskip 0pt plus 1filll
62 @center {14 02 2023 Vol #1}
63 @center writer:@ @i{Yukio Yoshida}(In Japan)
64
65 @page
66
67 @tex
68 \def\MPP {M\raise 5pt\hbox{P}\kern -5pt p{}}
69 \vbox {\null}
70 \vfill
71 \moveleft 1in\vbox{\Red {\P\thinspace \it{Fierst of all; about LilyPond}}}\par
72 \kern 1pc
73 \centerline {\bf Preface(LilyPond)}
74 \smallskip
75 It must have been during a rehearsal of the EJE (Eindhoven Youth Orchestra),
76 somewherein 1995 that Jan, one of the cranked violists told Han-Wen,
77 one of the distorted French horn players, about the grand new project
78 he was working on. It was an automated system for printing music
79 (to be precise, it was \MPP{}, a preprocessor for MusiX\TeX{}. As it happened,
80 Han-Wen accidentally wanted to print out some parts from a score,
81 so he started looking at thesoftware, and he quickly got hooked.
82 It was decided that \MPP{} was a dead end. After lots of philosophizing and
83 heated email exchanges, Han-Wen started LilyPond in 1996. This time, Jan
84 got sucked into Han-Wen's new project.\par
85 \smallskip
86 In some ways, developing a computer program is like learning to play an
87 instrument. In the beginning, discovering how it works is fun, and
88 the things you cannot do are challenging. After the initial excitement,
89 you have to practice and practice. Scales and studies can be dull, and
90 if you are not motivated by others.teachers, conductors or audience.
91 it is very tempting togive up. You continue, and gradually playing becomes
92 a part of your life. Some days it comes naturally, and it is wonderful, and
93 on some days it just does not work, but you keep playing, day after day.\par
94 \smallskip
95 Like making music, working on LilyPond can be dull work, and on some days
96 it feels like plodding through a morass of bugs. Nevertheless,
97 it has become a part of our life, and we keep doing it. Probably the most
98 important motivation is that our program actually does something useful for people.
99 When we browse around the net we find many people who use LilyPond, and
100 produce impressive pieces of sheet music. Seeing that feels unreal,
101 but in a very pleasant way.\par
102 \smallskip
103 Our users not only give us good vibes by using our program, many of them also
104 help us by giving suggestions and sending bug reports, so we would like to
105 thank all users that sent us bug reports, gave suggestions or contributed in
106 any other way to LilyPond.\par
107 \smallskip
108 Playing and printing music is more than a nice analogy. Programming together is
109 a lot of fun, and helping people is deeply satisfying, but ultimately, working
110 on LilyPond is a way to express our deep love for music.
111 \Blue{{\sl May it help you create lots of beautiful music!}}\par
112 \leftline {\it Han-Wen and Jan.}
113 \leftline {Utrecht/Eindhoven, The Netherlands, July 2002.}
114 \rightline{---Excerpt from LilyPond[ver1.6-lilypond.pdf-]---}
115 \vskip 0pt plus 1filll
116 \vfill
117 \vbox{\null}
118 @end tex
119 @end iftex
120 @end titlepage
121
122
123 @ifhtml
124 @html
125 <div align="center">
126 <span style="font-size: 40px;">
127 Invitation Write a Score//Music notation<br />
128 use Lilypond<br />
129 on<br />
130 WSL<br />
131 <span style="font-size: 18px;">
132 <!--
133 GNU/Linux 4.4.0-19041-Microsoft x86_64<br />
134 (Windows 10 & windows 11 & Linux)
135 -->
136 GNU/Linux 5.10.16.3-microsoft-standard-WSL2 x86_64<br />
137 (windows 11 & Linux)
138 </span>
139 </span>
140 </div>
141 <div align="left">
142 <span style="font-size: 14px;">
143 13 02 2023 Vol #1<br />
144 Writer: <i>Yukio Yoshida</i>(In Japan)</span>
145 </div>
146 <hr />
147 @end html
148 @end ifhtml
149
150 @ifnottex
151 @node Top, Concept Index, (dir), (dirTop)
152
153
154 @unnumbered LilyPond(Sheet Music Typesetting)
155 @end ifnottex
156
157 @ifhtml
158 @html
159 <span style="color: red;">
160 <span styls="font-siza: 10px;">Fierst of all; about LilyPond</span><br />
161 </span>
162 <br />
163 <br />
164 <p style="font-size: 20.6px;">
165 <div align="center">
166 <blockquote><blockquote>
167 <table border="1"><tr><td>
168 <table border="1"><tr><td>
169 <div align="center"><p style="font-size: 34px;"><b>Preface(LilyPond)</b></p></div>
170 It must have been during a rehearsal of the EJE(Eindhoven Youth Orchestra),
171 somewherein 1995 that Jan, one of the cranked violists told Han-Wen,
172 one of the distorted French horn players, about the grand new project
173 he was working on. It was an automated system for printing music
174 (to be precise, it was MPP, a preprocessor for MusiXTeX. As it happened,
175 Han-Wen accidentally wanted to print out some parts from a score,
176 so he started looking at thesoftware, and he quickly got hooked.
177 It was decided that MPP was a dead end. After lots of philosophizing and
178 heated email exchanges, Han-Wen started LilyPond in 1996. This time, Jan
179 got sucked into Han-Wen's new project.<br />
180
181 In some ways, developing a computer program is like learning to play an
182 instrument. In the beginning, discovering how it works is fun, and
183 the things you cannot do are challenging. After the initial excitement,
184 you have to practice and practice. Scales and studies can be dull, and
185 if you are not motivated by others.teachers, conductors or audience.
186 it is very tempting togive up. You continue, and gradually playing becomes
187 a part of your life. Some days it comes naturally, and it is wonderful, and
188 on some days it just does not work, but you keep playing, day after day.<br />
189
190 Like making music, working on LilyPond can be dull work, and on some days
191 it feels like plodding through a morass of bugs. Nevertheless,
192 it has become a part of our life, and we keep doing it. Probably the most
193 important motivation is that our program actually does something useful for people.
194 When we browse around the net we find many people who use LilyPond, and
195 produce impressive pieces of sheet music. Seeing that feels unreal,
196 but in a very pleasant way.<br />
197
198 Our users not only give us good vibes by using our program, many of them also
199 help us by giving suggestions and sending bug reports, so we would like to
200 thank all users that sent us bug reports, gave suggestions or contributed in
201 any other way to LilyPond.<br />
202
203 Playing and printing music is more than a nice analogy. Programming together is
204 a lot of fun, and helping people is deeply satisfying, but ultimately, working
205 on LilyPond is a way to express our deep love for music.
206 <span style="color: blue;"><b>
207 May it help you create lots of beautiful music!</b></span><br>
208 Han-Wen and Jan<br />
209 Utrecht/Eindhoven, The Netherlands, July 2002.<br />
210 </td></tr></table>
211 </td></tr></table>
212 <div align="right">
213 <i>Excerpt from LilyPond[ver1.6-lilypond.pdf-]</i>
214 </div>
215 </blockquote></blockquote>
216 </div>
217 </p>
218 <br />
219 <br />
220 @end html
221 @end ifhtml
222
223
224
225
226 @iftex
227 @iftex
228 @headline{@sevenrm context Voice@hfill @folio}
229 @end iftex
230 @iftex
231 @tex
232 ~@vfill
233 \centerline{{\bigcm context Voice}}
234 \vskip 2pc
235 @end tex
236 @end iftex
237 @iftex
238 @center @b{Knowledge for writing sheet music(using LilyPond)}
239 @center {---LilyPond language in the description of the musical score manuscript---}
240
241 @sp 2
242 @end iftex
243
244 @iftex
245 @noindent
246 LilyPond's @Red{default is @b{to read @t{nederlands.ly}(In Netherlands notation)}} and process
247 the manuscript given. Strings such as @b{Note Names}@t{(sharp, flat ...)} in music are
248 differences between countries(cultures).@ @ It is necessary to replace it with a target flight.@*
249 Those provided by Lilypond are@*
250 ................ @t{english}.ly , @t{deutsch}.ly , @t{norsk}.ly , @t{svenska}.ly , @t{italiano}.ly ,
251 @t{catalan}.ly , @t{espanol}.ly , @t{portugues}.ly , @t{suomi}.ly , @t{vlaams}.ly ...............@*
252 These are the declaration items at @i{the start of the musical score manuscript file}
253 (described in the order below). For example,
254 @*
255 @code{\version "2.24.0"}@*
256 @code{\include "italiano.ly"}
257 @*
258 @i{Version specification}: This manuscript is written in ver2.24.0---.
259 It is a @i{clear statement} to the "lilypond processing (token)".@*
260 In music manuscript coding, lilypond's-running does not choose OS. Also
261 The ly(both old and new manuscript file) will run if it is (@i{LilyPond environment construction})@i{OS},
262 and @i{even in the latest lilypond version}, too.@*
263 @end iftex
264 @iftex
265 @hrule
266 @*
267 @end iftex
268 @iftex
269 @noindent
270 Default typesetting is output in Note(@i{quarter}) , Beat(@i{4/4}) , Clef(@i{treble}) , and
271 Major(@i{C}). Midi is created with "@i{acoustic grand}(piano)" if there is no designated instrument.
272 @sp 1
273 @end iftex
274
275 @iftex
276 @cartouche
277 @end iftex
278 @iftex
279 @noindent
280 @b{Notes}@ Scale(pitch) basic code;@*
281 @hskip 10pt " @kbd{c d e f g a b} " Scale(pitch explicit symbol)@*
282 @end iftex
283 @iftex
284 @hskip 10pt @image{h-example-1-1, 6.in,}
285 @end iftex
286 @iftex
287 @end cartouche
288 @end iftex
289 @iftex
290 @*
291 @b{Notes}@ Note value(length of note) Basic code;@*
292 " @code{ c d e f g a b } " to specify the scale,
293 specify the numerical value @code{1 2 4 8 16 32 64 128} with the subscript.@*
294 @i{Descriptions of}@ " @Red{ @code{ c4@ a'1@ g,2@ }}..... " @i{as note symbols}@*
295 @end iftex
296 @iftex
297 @*
298 @noindent
299 @b{1}(Whole)@result{}@b{2}(Half)@result{}@b{4}(Quarter)@result{}@b{8}(Eigth)@result{}
300 @b{16}(Sixteenth) ...... @hfill @*
301 @noindent
302 1=whole sound divided evenly by all sounds, the following diagram;
303 @Red{Rests are also notes}@*
304 @end iftex
305 @iftex
306 @hskip -20pt @image{h-example-2-1, 5.5in,}@*
307 @end iftex
308
309 @sp 1
310
311 @iftex
312 In Lilypond, for a note without a note value,
313 @Red{ the note value is searched before and before it }, and the note value
314 @Red{ is evaluated}@*
315 {@largcmb
316 For example; " @code{ a4 c8 d e f g r c4 } " is interpreted as
317 " @code{ a4 c8 d8 e8 f8 g8 r8 c4 } "}@*
318 @end iftex
319
320 @sp 2
321
322 @iftex
323 @center { --- \clef treble \key c\major ---- }
324 @center { As c\major @hskip 20pt notes-writing are @code{c' d' e' f' g' a' b'} }
325 @end iftex
326 @iftex
327 @hskip 100pt @image{c-major-1, 6.5in,}
328 @end iftex
329 @iftex
330
331 @sp 1
332
333 Major scale list:@*
334 @b{Cycle of 5th: UP @i{and} DOWN}(The minor scale is omitted,
335 there is nature+harmony ...so,there are many sample notations.)@*
336 @end iftex
337 @iftex
338 @*
339 @b{\clef treble \key c\major}@*
340 @end iftex
341 @iftex
342 @hskip 100pt @image{c-major2-1, 6.5in,}@*
343 @end iftex
344
345 @sp 1
346
347 @iftex
348 {@largcmb
349 @hskip -40pt @Red{\key g\major}@hskip 16pc @Red{\key f\major}}@*
350 @hskip -40pt @image{pg-major-1, 3.5in,}@qquad @image{pf-major-1, 3.5in,}@*
351 @end iftex
352
353 @iftex
354 {@largcmb
355 @hskip -40pt @Red{\key d\major}@hskip 16pc @Red{\key bes\major}}@*
356 @hskip -40pt @image{pd-major-1, 3.5in,}@qquad @image{pbes-major-1, 3.5in,}@*
357 @end iftex
358
359 @iftex
360 {@largcmb
361 @hskip -40pt @Red{\key a\major}@hskip 16pc @Red{\key ees\major}}@*
362 @hskip -40pt @image{pa-major-1, 3.5in,}@qquad @image{pees-major-1, 3.5in,}@*
363 @end iftex
364
365 @iftex
366 {@largcmb
367 @hskip -40pt @Red{\key e\major}@hskip 16pc @Red{\key aes\major}}@*
368 @hskip -40pt @image{pe-major-1, 3.5in,}@qquad @image{paes-major-1, 3.5in,}@*
369 @end iftex
370
371 @iftex
372 {@largcmb
373 @hskip -40pt @Red{\key b\major}@hskip 16pc @Red{\key des\major}}@*
374 @hskip -40pt @image{pb-major-1, 3.5in,}@qquad @image{pdes-major-1, 3.5in,}@*
375 @end iftex
376
377 @iftex
378 {@largcmb
379 @hskip -40pt @Red{\key fis\major}@hskip 16pc @Red{\key ges\major}}@*
380 @hskip -40pt @image{pfis-major-1, 3.5in,}@qquad @image{pges-major-1, 3.5in,}@*
381 @end iftex
382
383 @iftex
384 {@largcmb
385 @hskip -40pt @Red{\key cis\major}@hskip 16pc @Red{\key ces\major}}@*
386 @hskip -40pt @image{pcis-major-1, 3.5in,}@qquad @image{pces-major-1, 3.5in,}@*
387 @end iftex
388
389 @iftex
390 @sp -1
391 @center{Here,both are back. ..... The changes are now back.}
392 @center{(c\major @code{ c' d' e' f' g' a' b' })}
393 @end iftex
394 @iftex
395 @hskip 10pc @image{c-major-1, 6.5in,}
396 @end iftex
397
398
399 @iftex
400 @center{{@largcmb @Red {No matter how much \clef changes,}}}
401 @center{{@largcmb @Red {the notes description convention of}}}
402 @center{{@largcmb @Red {\key name\major and name\miner is unchanged.}}}
403 @end iftex
404
405 @vskip 0pt plus 1filll
406 @page
407 @tex
408 \centerline{{\bigcm Refer \#1}}
409 \vskip 2pc
410 @end tex
411 @iftex
412 @tex
413 \centerline {\largcmb Automatic processing:}
414 \centerline {\largcmb LilyPond processing result sample(file name is pompei4.ly)}
415 @end tex
416 @sp 1
417 Create a pompei4.ly file with a text editor as shown below.@*
418 File-name;@ @t{pompei4.ly}--------------------------------------------------------
419 @verbatim
420 %% #(set-default-paper-size "letter")
421 \version "2.22.2"
422 #(set-global-staff-size 14)
423 \paper { paper-height = 48\mm
424 paper-width = 160\mm
425 page-top-space = 0.00\mm
426 top-margin = 0.00\mm
427 bottom-margin = 0.00\mm }
428 \header { tagline = \markup { \null } }
429 altoOne = { \clef alto
430 \autoBeamOff
431 %1-
432 \repeat volta 3 { \repeat volta 2 {
433 fis'2.^\markup { \column { " " \line {\hspace #-12 \teeny \italic
434 "As a feeling; like walking slowly and step by step in your heart." }}}
435 _\mp\<\( | a'4. g' | e'2. | g'4. fis' |
436 a'2. | e'4. fis'\!\) | } g'2. | } \break }
437
438 bassOne = { \clef bass
439 \autoBeamOff
440 %1-
441 \repeat volta 3 { \repeat volta2 {
442 bes,4 ces\mp^\< bes, | ges,2.\! | fes,4\mp^\< aes, ges, |
443 aes,2.\! | ges,4\mp^\< bes, aes, | fes,2.\! | } ges,2. | } \break }
444
445 %% --- get sheet music
446 \book {
447 \markup { \column {
448 \line {\hspace #8 "Passing in cemetery, We are going into a town."}
449 \line {\hspace #8 "Passing out cemetery, We are going out the town"}
450 } }
451 \score { \context ChoirStaff = "UP" <<
452 \context Staff = "Up" { \key d\major \time 3/4 \altoOne }
453 \context Staff = "Down" { \key ces\major \time 3/4 \bassOne }
454 >>
455 \layout { indent = 0.00\mm }
456 }
457
458 %% --- get midi music
459 \score { \unfoldRepeats
460 \context ChoirStaff = "UPDOWN" <<
461 \context Staff = "Up" { \key d\major \time 3/4 \tempo 4 = 62
462 \set Staff.midiInstrument = "acoustic grand" \altoOne }
463 \context Staff = "Down" { \key ces\major \time 3/4 \tempo 4 = 62
464 \set Staff.midiInstrument = "acoustic grand" \bassOne }
465 >>
466 \midi { tempoWholesPerMinute = #(ly:make-moment 62 4) }
467 }
468 \markup { \vspace #-6 \column {
469 \line {\hspace #8 "This , Our life is the same?"}
470 \line {\hspace #8 "Born to live life, Life in the dead leaves!"}
471 } }
472 }
473 @end verbatim
474 ---------------------------------------------------------------------------------@*
475 Where the pompei4.ly file is,@*
476 windows OS =====> @t{lilypond --pdf --png pompei4.ly}[Enter]@*
477 Linux OS =======$ @t{lilypond --pdf --png pompei4.ly}[Enter]@*
478 When you open the created pompei4.pdf(pompei4.png), it is as follows.@*
479 @sp 1
480 @image{pompei4-1, 6.5in,}
481 @*
482 As you can see; Text can be processed with @code { \markup @{ text @}},
483 whether inside @code{ \score @{.....@} } or outside @code{ \score @{.....@} }.
484 On the contrary, this @code{ \markup @{ \score @{...@}@} } is also possible,too.@*
485 "@code{\markup}" is a kind of Line Editor function,and
486 you can write pronunciation notation characters,
487 special characters,... straight and continue writing the manuscript.
488 Once you get used to it, you can also create a document(sentence only) with only
489 @code{\markup} of lilypond.@*
490 @*
491 Therefore, it is possible to display The score,a score,score-book,score-document,
492 ...etc, in pdf/paper and display only by writing the LilyPond manuscript.@*
493 @sp 2
494 What we are talking about here is the "Formatting text" inside the LilyPond environment,
495 not the "Formatting Text" outside the LilyPond environment.
496 In the outside world, there are various [Word Processors],[@TeX{}(system)],[Hypertext(system)],
497 [Ghostscript]...@ It will be a word processor for general use in paper(documentation).@*
498 @*
499 @bullet{} For example;LibreOffice/OpenOffice(open source)@*
500 If you paste it into Word Processer--musical score,sheet music,sheet music book,
501 musical score document--you can easily and easily put it on paper.@*
502 Reference==>@uref{https://github.com/OOoLilyPond/OOoLilyPond/wiki#ooolilypond}@*
503 @*
504 @bullet{} On the other hand, there is a typesetting method for converting musical scores,
505 musical scores, musical score books, and musical score documents into paper.
506 Also, there is a display specification based on HyperText.@
507 @b{LilyPond} also provides a typesetting (@TeX {})system and a program for HyperText
508 that can display the score at the document position(see usage.pdf for details)@*.
509 @end iftex
510 @vskip 0pt plus 1filll
511
512 @page
513 @tex
514 \centerline{{\bigcm Refer \#2}}
515 \vskip 2pc
516 @end tex
517 @iftex
518 @tex
519 \centerline {\largcmb Automatic processing:}
520 \centerline {\largcmb LilyPond processing result sample(file name is example-4.ly)}
521 @end tex
522 @sp 1
523 Create a example-4.ly file with a text editor as shown below.@*
524 File-name;@ @t{example-4.ly}--------------------------------------------------------
525 @verbatim
526 \version "2.22.2"
527 %% #(set-default-paper-size "letter")
528 #(set-global-staff-size 16)
529 \paper{
530 paper-height = 30.00\mm
531 paper-width = 120.00\mm
532 page-top-space = 00.00\mm
533 top-margin = 0.00\mm
534 bottom-margin = 0.00\mm
535 }
536
537 \header { tagline = \markup { \null } }
538 %%%%%%%%% soprano part %%%%%%%%%%%%%%%%%%%%%
539 soprano = { \hide Staff.BarLine
540 \autoBeamOff
541 %% 9-12
542 e''1 e''4. r8 | d''2 fis''1 | R1. | R1.
543 \undo \hide Staff.BarLine \bar "|." \break
544 }
545 sopranoL = \lyricmode {
546 \override Score . LyricText #'font-shape = #'italic
547 \tiny
548 Do -- minus te -- cum,
549 }
550
551 %%%%%%% bass; part %%%%%%%%%%%%%%%%
552 bass = { \hide Staff.BarLine
553 \autoBeamOff
554 %% 9-12
555 R1. | R1. | b,1 b,4. r8 | cis2 e1
556 \undo \hide Staff.BarLine \bar "|." \break
557 }
558 bassL = \lyricmode {
559 \override Score . LyricText #'font-shape = #'italic
560 \tiny
561 Do -- minus te -- cum,
562 }
563
564 %% get sheet & midi music ---------------------------------------------------------------
565 \score {
566 <<
567 %% \context ChoirStaff = "FourPartStaffaddchorus" <<
568 %% use \hide Staff.BarLine
569 \context StaffGroup <<
570 \context Voice = "soprano" { \clef soprano \key d\major \time 3/2
571 \set Staff.instrumentName = "soprano" \soprano }
572 \new Lyrics = "mainSL" \lyricsto "soprano" { \sopranoL }
573
574 \context Voice = "bass" { \clef bass \key d\major \time 3/2
575 \set Staff.instrumentName = "bass " \bass }
576 \new Lyrics = "mainBL" \lyricsto "bass" { \bassL }
577 >>
578 >>
579 \layout { }
580 \midi { tempoWholesPerMinute = #(ly:make-moment 58 4) }
581 }
582 @end verbatim
583 ---------------------------------------------------------------------------------@*
584 Where the example-4.ly file is,@*
585 windows OS =====> @t{lilypond --pdf --png example-4.ly}[Enter]@*
586 Linux OS =======$ @t{lilypond --pdf --png example-4.ly}[Enter]@*
587 When you open the created example-4.pdf(example-4.png), it is as follows.@*
588 @sp 1
589 @image{example-4-1, 6.5in,}
590 @*
591 context Staff@*
592 Usually "@kbd{\new Staff}"(=@kbd{\context Staff}) is the way to call the staff.@*
593 However, in example-4.ly,@*
594 it is described as "@kbd{\context Voice}"(=@kbd{\new Voice}) instead.@*
595 ----------------------------------------------------------------------------------@*
596 As a rough reference, sopurano = ....lilypond code(music) description is processed
597 by calling \score {[cpu(music) processing] with \soprano.@ @ ...the(memory) stacks
598 is named soprano(Same for bass).
599 @kbd{\context Voice = "soprano"},@kbd{\context Voice = "bass"} is the name,
600 It means the associated(soprano, bass) Staff.@*
601 ..... Therefore @code{\new Lyrics = "mainSL" \lyricsto "soprano" {\sopranoL}} holds.
602 The lyrics of sopranoL are called into \score {with \sopranoL and synchronized
603 with the soprano naming Staff. It will be a musical score(same for bass).@*
604 ----------------------------------------------------------------------------------@*
605 By the way,@*
606 @code{\context Voice = "soprano" \context Voice = "bass"} Rewrite this part@*
607 Write @code{\context Staff = "soprano" \context Staff = "bass"} .......@*
608 (verify)@kbd{lilypond --pdf --png example-4.ly}(running) and get example-4.pdf@*
609 @b{@it{It's obvious if you do (there is no lyrics part!?).}}@*
610 @*
611 It is better to write in the staff call of "\new Voice @{" or "\context Voice @{"
612 ....in the composition process, avoiding the staff call of "\new Staff @{" or
613 "\context Staff @{" is more important than its convenience.@*
614 @sp 2
615 @iftex
616 @tex
617 \centerline {\largcmb Automatic processing:}
618 \centerline {\largcmb LilyPond processing result sample(file name is example-5.ly)}
619 @end tex
620 @*
621 Create a example-5.ly file with a text editor as shown below.@*
622 File-name;@ @t{example-5.ly}--------------------------------------------------------
623 @verbatim
624 \version "2.22.2"
625 #(set-global-staff-size 16)
626 \paper{
627 paper-height = 20.00\mm
628 paper-width = 100.00\mm
629 page-top-space = 0.00\mm
630 top-margin = 0.00\mm
631 bottom-margin = 0.00\mm
632 }
633 \header { tagline = \markup { \null } }
634
635 soprano = { \bar " "
636 %% 45-47
637 \time 4/1
638 << { s\breve ees'\breve ~ | ees'1 s1 s\breve } \\
639 { <c' g'>\breve ~ c'\breve ~ | c'\longa ~ } >> |
640 \time 3/2
641 << { s1. } \\ { c'1 s2 } >> \bar "|." \break }
642 \score {
643 \context Voice = "soprano" { \clef soprano \key ees\major \time 3/2
644 \set Staff.instrumentName = "soprano" \soprano }
645 \layout { \override Score.BarNumber.break-visibility = ##(#f #t #t)
646 \set Score.currentBarNumber=45 }
647 }
648 @end verbatim
649 ---------------------------------------------------------------------------------@*
650 Where the example-5.ly file is,@*
651 windows OS =====> @t{lilypond --pdf --png example-5.ly}[Enter]@*
652 Linux OS =======$ @t{lilypond --pdf --png example-5.ly}[Enter]@*
653 When you open the created example-5.pdf(example-5.png), it is as follows.@*
654 @sp 1
655 @image{example-5-1, 6.5in,}
656 @*
657 The 47th bar should be described as @code{c'1 s2 \bar "|." \break}, but
658 since the 46th bar is described separately from the top and bottom ...
659 @code{from the bottom. Since c'\longa ~} and Tie are being sent ...
660 The code description in bar 47 is processed as above. @ @ @b{However},
661 LilyPond's musical score code description is not absolute for each person.@*
662 @Red{With the exception} of LilyPond,
663 @Red{information sent by that staff is received within that staff in principle}.
664 @sp 1
665 Other;@*
666 Lilypond also has a feature called "@Red{ @code {\skip argument}}" that is similar to " @Red{s} " note.
667 (In notation.pdf)It is recommended to verify with(page-59,286,799). @*
668 @end iftex
669 @vskip 0pt plus 1filll
670
671 @page
672 @tex
673 \centerline{{\bigcm Refer \#3}}
674 \vskip 2pc
675 @end tex
676 @iftex
677 @*
678 @image{example-7-1, 6.5in}
679 @*
680 @end iftex
681 @vskip 0pt plus 1filll
682
683 @page
684
685
686
687 @ifnottex
688 @node Concept Index, context Voice, Top, Top
689
690 @top
691 @unnumbered Write a Score
692 @end ifnottex
693
694 @ifhtml
695 @menu
696 * Concept Index::
697 * context Voice::
698 * Formatting text::
699 * context Staff::
700 * context Score::
701 @end menu
702 @end ifhtml
703
704
705
706
707 @ifnottex
708 @node context Voice, Formatting text, Concept Index, Top
709
710 @unnumbered context Voice
711 @end ifnottex
712
713 @ifhtml
714 @html
715 <blockquote><blockquote><blockquote>
716 <span style="font-size: 18px;">
717 @end html
718 @center @b{Knowledge for writing sheet music(using LilyPond)}
719 @center ---LilyPond language in the description of the musical score manuscript---
720 @cartouche
721
722 @end cartouche
723 LilyPond's default is @b{to read @t{nederlands.ly}(In Nederlands notation)} and process
724 the manuscript given. Strings such as @b{Note Names}@t{(sharp, flat ...)} in music are
725 differences between countries(cultures).@ @ It is necessary to replace it with a target flight.@*
726 Those provided by Lilypond are@*
727 ................ @t{english}.ly , @t{deutsch}.ly , @t{norsk}.ly , @t{svenska}.ly , @t{italiano}.ly ,
728 @t{catalan}.ly , @t{espanol}.ly , @t{portugues}.ly , @t{suomi}.ly , @t{vlaams}.ly ...............@*
729 These are the declaration items at @i{the start of the musical score manuscript file}
730 (described in the order below). For example,
731
732 @html
733 <br />
734 <code>\version "2</code>.<code>24</code>.<code>0"</code><br />
735 <code>\include "italiano</code>.<code>ly"</code><br />
736 <br />
737 @end html
738
739 @i{Version specification}: This manuscript is written in ver2.24.0---.
740 It is a @i{clear statement} to the "lilypond processing (token)".@*
741 In music manuscript coding, lilypond's-running does not choose OS,@*
742 The ly(both old and new manuscript file) will run if it is (@i{LilyPond environment construction})@i{OS},
743 and @i{even in the latest lilypond version}, too.@*
744 @html
745 <hr />
746 @end html
747 Default typesetting is output in Note(@i{quarter}) , Beat(@i{4/4}) , Clef(@i{treble}) , and
748 Major(@i{C}).@*
749 Midi is created with "@i{acoustic grand}(piano)" if there is no designated instrument@*
750 @*
751 @cartouche
752 @html
753 <b>Notes</b>  
754    
755 Scale(pitch) basic code;<br />
756          
757 " <code>c d e f g a b</code> " Scale(pitch explicit symbol)<br />
758 <img src="h-example-1.svg" alt="[picture of music]" /><br /><!-- -->
759 @end html
760 @end cartouche
761 @html
762 <b>Notes</b>  
763    
764 Note value(length of note) Basic code;<br />
765 " <code>c d e f g a b</code> " to specify the scale,
766 specify the numerical value " <code>1 2 4 8 16 32 64 128</code> "
767 with the subscript.<br />
768 <i>Descriptions of<i>   
769 "<span style="color: red;">
770 <code> c4   a'1   g,2   ..... </code></span>"
771 <i>as note symbols</i>.<br />
772 @end html
773 @noindent
774 @b{1}(Whole)@result{}@b{2}(Half)@result{}@b{4}(Quarter)@result{}@b{8}(Eigth)@result{}
775 @b{16}(Sixteenth) ...... @*
776 @noindent
777 1=whole sound divided evenly by all sounds, the following diagram;
778 @html
779    (<span style = "color: red;">Rests are also notes</b></span>).
780 @end html
781 @*
782 @html
783 <img src="h-example-2.svg" alt="[picture of music]" /><br /><!-- -->
784 <br />
785 In Lilypond, for a note without a note value,
786 <span style="color: red;">
787 the note value is searched before and before it,</span> and the note value
788 <span style="color: red;"> is evaluated</span>.<br />
789 <span style="font-size: 16px">
790 For example; " <code>a4 c8 d e f g r c4</code> " is interpreted as
791 " <code>a4 c8 d8 e8 f8 g8 r8 c4</code> "<br />
792 @end html
793 @sp 1
794 @html
795 <p align="center">
796 ---- \clef treble \key c\major ----<br />
797 As c\major   notes-writing are <t> c' d' e' f' g' a' b'</t> <br />
798          
799          
800          
801          
802          
803     
804 <img src="c-major.svg" alt="[picture of music]" /><!-- -->
805 </p>
806 @end html
807 @ifhtml
808 Major scale list:@*
809 @b{Cycle of 5th: UP @i{and} DOWN}(The minor scale is omitted,
810 there is nature+harmony ...so,there are many sample notations.)@*
811 @*
812 @b{\clef treble \key c\major}
813 @end ifhtml
814 @html
815 <p align="center">
816          
817          
818          
819          
820          
821     
822 <img src="c-major2.svg" alt="[picture of music]" /><br />
823 <b>Deployment;</b>
824 </p>
825 <div align="center">
826 <table>
827 <td>
828 <p>
829 \key g\major    <t> c' d' e' fis' g' a' b'</t>
830 <br />
831 <img src="g-major.svg" alt="[picture of music]" /><!-- -->
832 </p>
833 <p>
834 \key d\major    <t> cis' d' e' fis' g' a' b'</t>
835 <br />
836 <img src="d-major.svg" alt="[picture of music]" /><!-- -->
837 </p>
838 <p>
839 \key a\major    <t> cis' d' e' fis' gis' a' b'</t>
840 <br />
841 <img src="a-major.svg" alt="[picture of music]" /><!-- -->
842 </p>
843 <p>
844 \key e\major    <t> cis' dis' e' fis' gis' a' b'</t>
845 <br />
846 <img src="e-major.svg" alt="[picture of music]" /><!-- -->
847 </p>
848 <p>
849 \key b\major    <t> cis' dis' e' fis' gis' ais' b'</t>
850 <br />
851 <img src="b-major.svg" alt="[picture of music]" /><!-- -->
852 </p>
853 <p>
854 \key fis\major    <t> cis' dis' eis' fis' gis' ais' b'</t>
855 <br />
856 <img src="fis-major.svg" alt="[picture of music]" /><!-- -->
857 </p>
858 <p>
859 \key cis\major    <t> cis' dis' eis' fis' gis' ais' bis'</t>
860 <br />
861 <img src="cis-major.svg" alt="[picture of music]" /><!-- -->
862 </p>
863 <p>
864 Here; ..... The changes are now back.<br />
865 (c\major    <t> c' d' e' f' g' a' b'</t>)
866 <br />
867 <img src="c-major.svg" alt="[picture of music]" /><!-- -->
868 </p>
869 </td>
870 <td>
871    
872 </td>
873 <td>
874 <p>
875 \key f\major    <t> c' d' e' f' g' a' bes'</t>
876 <br />
877 <img src="f-major.svg" alt="[picture of music]" /><!-- -->
878 </p>
879 <p>
880 \key bes\major    <t> c' d' ees' f' g' a' bes'</t>
881 <br />
882 <img src="bes-major.svg" alt="[picture of music]" /><!-- -->
883 </p>
884 <p>
885 \key ees\major    <t> c' d' ees' f' g' aes' bes'</t>
886 <br />
887 <img src="ees-major.svg" alt="[picture of music]" /><!-- -->
888 </p>
889 <p>
890 \key aes\major    <t> c' des' ees' f' g' aes' bes'</t>
891 <br />
892 <img src="aes-major.svg" alt="[picture of music]" /><!-- -->
893 </p>
894 <p>
895 \key des\major    <t> c' des' ees' f' ges' aes' bes'</t>
896 <br />
897 <img src="des-major.svg" alt="[picture of music]" /><!-- -->
898 </p>
899 <p>
900 \key ges\major    <t> ces' des' ees' f' ges' aes' bes'</t>
901 <br />
902 <img src="ges-major.svg" alt="[picture of music]" /><!-- -->
903 </p>
904 <p>
905 \key ces\major    <t> ces' des' ees' fes' ges' aes' bes'</t>
906 <br />
907 <img src="ces-major.svg" alt="[picture of music]" /><!-- -->
908 </p>
909 <p>
910 Here; ..... The changes are now back.<br />
911 (c\major    <t> c' d' e' f' g' a' b'</t>)
912 <br />
913 <img src="c-major.svg" alt="[picture of music]" /><!-- -->
914 </p>
915 </td>
916 </table>
917 </div>
918 <br />
919 <br />
920 @end html
921 @ifhtml
922 @cartouche
923 meaning;[ -- For example --- @t{\clef treble \key g \major} The specified score is@*
924 ---------------
925 The author; @result{} " @t{f} "(note) must be written as " @t{fis} "(note).@*
926 ---------------
927 The performer; @result{} All " f " notation notes in the score must be played in " fis "(sound). ]@*
928 Or ....
929 meaning;[ -- For example --- @t{\clef treble \key a \major} The specified score is@*
930 ---------------
931 The author; @result{} " @t{c@ @ f@ @ g} "(note) must be written as " @t{cis@ @ fis@ @ gis} "(note).@*
932 ---------------
933 The performer; @result{} All " c@ @ f@ @ g " notation notes in the score must be played in " cis@ @ fis@ @ gis "(sound). ]@*
934 @*
935 ---------------
936 @bullet{} @i{These are the basic precautions when writing a score}.
937 ---------------@*
938 @end cartouche
939 @*
940 A clef is a symbol at the beginning of a line of music, and...
941 Clef is a word(noun) that refers to a state that envelops a kind of diversity.@*
942 Simply put, the clef symbol indicates the (c)position of its Scale(pitch)-on the staff-@*
943 @end ifhtml
944
945 @html
946 </blockquote></blockquote></blockquote>
947 @end html
948
949 @html
950 <blockquote><blockquote>
951 @end html
952 @ifhtml
953 About the \clef and \key:@*
954 Just move the \key sign notation with clef.@ @bullet{}@ But!@ @
955 @result{}@result{}@result{}
956 @i{The description of notes by \key does not change.}@*
957 @end ifhtml
958 @ifhtml
959 @html
960 <span style="font-size: 18px;">
961   
962 <code>\clef ???????</code>  <=====  
963 <code><span style="color: red;">treble</span></code> <i>or</i>
964 <code><span style="color: red;">soprano</span></code> <i>or</i>
965 <code><span style="color: red;">alto</span></code> <i>or</i>
966 <code><span style="color: red;">tenor</span></code> <i>or</i>
967 <code><span style="color: red;">bass</span></code>
968   
969 </span>
970 @end html
971 (LilyPond has othe \clef, too. see==>notation.pdf)@*
972 @end ifhtml
973 @html
974 <br />
975 <div align="center">
976 <table>
977 <td>
978 <p>
979 <img src="clef-g.svg" alt="[picture of music]" /><!-- -->
980 </p>
981 <p>
982 <img src="clef-d.svg" alt="[picture of music]" /><!-- -->
983 </p>
984 <p>
985 <img src="clef-a.svg" alt="[picture of music]" /><!-- -->
986 </p>
987 <p>
988 <img src="clef-e.svg" alt="[picture of music]" /><!-- -->
989 </p>
990 <p>
991 <img src="clef-b.svg" alt="[picture of music]" /><!-- -->
992 </p>
993 <p>
994 <img src="clef-fis.svg" alt="[picture of music]" /><!-- -->
995 </p>
996 <p>
997 <img src="clef-cis.svg" alt="[picture of music]" /><!-- -->
998 </p>
999 </td>
1000 <td>
1001     
1002 </td>
1003 <td>
1004 <p>
1005 <img src="clef-f.svg" alt="[picture of music]" /><!-- -->
1006 </p>
1007 <p>
1008 <img src="clef-bes.svg" alt="[picture of music]" /><!-- -->
1009 </p>
1010 <p>
1011 <img src="clef-ees.svg" alt="[picture of music]" /><!-- -->
1012 </p>
1013 <p>
1014 <img src="clef-aes.svg" alt="[picture of music]" /><!-- -->
1015 </p>
1016 <p>
1017 <img src="clef-des.svg" alt="[picture of music]" /><!-- -->
1018 </p>
1019 <p>
1020 <img src="clef-ges.svg" alt="[picture of music]" /><!-- -->
1021 </p>
1022 <p>
1023 <img src="clef-ces.svg" alt="[picture of music]" /><!-- -->
1024 </p>
1025 </td>
1026 </table>
1027 </div>
1028 <br />
1029 <br />
1030 @end html
1031 @ifhtml
1032 @cartouche
1033 As you can see, all lilypond outputs automatically typesetting.
1034 The author specified \clef \key \time, and then followed \key.
1035 Just write @t{c d e f g a b }with \time in mind.@*
1036 For example;(soprano.ly)@*
1037 @multitable columnfractions .4 .4
1038 @item
1039 @cartouche
1040 @verbatim
1041 \version "2.22.2"
1042 #(set-global-staff-size 18)
1043 %% #(set-default-paper-size "letter")
1044 \paper { paper-height = 35.00\mm }
1045 soprano = { \autoBeamOff
1046 %% 1-4(1-12)
1047 \repeat volta 2 { \repeat volta 2 {
1048 r8 gis'8[ ais'] b'4. cis''8 disis''!2~ disis''8 | ais'4 dis''2 gis'2. | }
1049 fis'4 e' dis'4. fis'8 e'2 | ais'4 dis''2 gis'2. | } \bar "|."
1050 }
1051 %% get sheet
1052 \score { \context ChoirStaff <<
1053 \context Voice = "SopOne" {
1054 \clef soprano \key b\major \time 3/2 \tempo 4 = 58
1055 \set Staff.instrumentName = \markup{"soprano"} \soprano }
1056 >>
1057 \layout {}
1058 }
1059 %% get midi
1060 \score { <<
1061 \new Staff { \clef soprano \key b\major \time 3/2
1062 \set Staff.midiInstrument = "pad 4 (choir)"
1063 \unfoldRepeats \soprano }
1064 >>
1065 \midi { tempoWholesPerMinute = #(ly:make-moment 58 4) }
1066 }%% End score.
1067 @end verbatim
1068 @end cartouche
1069 @tab
1070 @html
1071 <span style="font-size: 18px;">
1072 Any OS; (prompt)<t>lilypond --pdf --png soprano.ly</t></span>[Enter]<br />
1073 <br />
1074 <p>
1075 <img src="soprano.svg" alt="[picture of music]" /><!-- -->
1076 </p>
1077 <a href="soprano.midi">soprano.midi</a> (<a href="soprano.mp3">soprano.mp3</a>)<br />
1078 @end html
1079 Typesetting is output like this.(midi=It’s a one minute and ten second performance.)@*
1080 @*
1081 @*
1082 @i{This is just an example(because there are various forms of description)}@*
1083 @html
1084 <span style="color: red;">
1085 \soprano
1086 </span>
1087 @end html
1088 means soprano = @{... description ....@} is called to this location for processing.@*
1089 The staff call is usually \new Staff @{@*
1090 However, it is better to call the staff with \context Voice @{@*
1091 @*
1092 Also,
1093 @html
1094 <span style="color: red;">
1095 \context Voice = "SopOne"
1096 </span>
1097 @end html
1098 @{... description ....@}@*
1099 It is an act of giving the name "SopOne" to this music-processed memory stacks.@*
1100 (Because you can specify a word etc. to this "SopOne".)@*
1101 @*
1102 @*
1103 --------
1104 Please refer to "notation.pdf" for the correspondence between note spelling and lyrics.@*
1105 @*
1106 @*
1107 @end multitable
1108 @end cartouche
1109 About \time; For example@*
1110 @code{\time 3/2} describes the score with the length of three half notes as one unit.@*
1111 @result{}@i{The upper number indicates the number of beets par measure}.@*
1112 @result{}@i{The lower number indicates the note that gets one beet(2=half note, 4=quarter note,
1113 8=eight note ...etc}.@*
1114 @end ifhtml
1115 @*
1116 @ifhtml
1117 @html
1118 <br />
1119 <br />
1120 <div align="center">
1121 <span style="font-size: 22px;">
1122 <span style="color: red;">
1123 When writing a score, it is recommended to keep notation.pdf + usage.pdf at hand.<br />
1124 </span></span>
1125 </div>
1126 @end html
1127 @end ifhtml
1128
1129 @html
1130 </blockquote></blockquote>
1131 <br />
1132 <br />
1133 @end html
1134
1135 @end ifhtml
1136
1137
1138
1139
1140 @iftex
1141 @headline{@sevenrm Formatting text@hfill @folio}
1142 @end iftex
1143 @tex
1144 \centerline{{\bigcm Formatting text}}
1145 \vskip 2pc
1146 @end tex
1147 @iftex
1148
1149 I'm sorry, I'll omit it. For details, we recommend referring to "notation.pdf".`@*
1150 @largcmb{
1151 [.....\share\doc\lilypond\html\Documentation\notation.pdf(6,832KB) + usage.pdf(521KB) ]}@*
1152
1153 @end iftex
1154 @vskip 0pt plus 1filll
1155 @page
1156
1157
1158
1159
1160 @ifnottex
1161 @node Formatting text, context Staff, context Voice, Top
1162
1163 @unnumbered Formatting text
1164 @end ifnottex
1165 @ifhtml
1166 @html
1167 <blockquote><blockquote><blockquote>
1168 @end html
1169
1170 I'm sorry, I'll omit it. For details, we recommend referring to "notation.pdf".`@*
1171 [.....\share\doc\lilypond\html\Documentation\notation.pdf(6,832KB) + usage.pdf(521KB) ]@*
1172
1173 @html
1174 </blockquote></blockquote></blockquote>
1175 @end html
1176 @end ifhtml
1177
1178
1179
1180
1181 @iftex
1182 @headline{@sevenrm context Staff@hfill @folio}
1183 @end iftex
1184 @tex
1185 \centerline{{\bigcm context Staff}}
1186 \vskip 2pc
1187 @end tex
1188 @iftex
1189
1190 I'm sorry, I'll omit it. For details, we recommend referring to "notation.pdf".`@*
1191 [.....\share\doc\lilypond\html\Documentation\notation.pdf(6,832KB) + usage.pdf(521KB) ]@*
1192
1193 @end iftex
1194 @vskip 0pt plus 1filll
1195
1196 @page
1197
1198
1199
1200
1201 @ifnottex
1202 @node context Staff, context Score, Formatting text, Top
1203
1204 @unnumbered context Staff
1205 @end ifnottex
1206 @ifhtml
1207 @html
1208 <blockquote><blockquote><blockquote>
1209 @end html
1210
1211 I'm sorry, I'll omit it. For details, we recommend referring to "notation.pdf".@*
1212 [.....\share\doc\lilypond\html\Documentation\notation.pdf(6,832KB) + usage.pdf(521KB) ]@*
1213
1214 @html
1215 </blockquote></blockquote></blockquote>
1216 @end html
1217 @end ifhtml
1218
1219
1220
1221
1222 @iftex
1223 @headline{@sevenrm context Score@hfill @folio}
1224 @end iftex
1225
1226 @tex
1227 \centerline{{\bigcm context Score}}
1228 \vskip 2pc
1229 @end tex
1230 @end iftex
1231 @iftex
1232 @*
1233 @image{example-7-1, 6.5in}
1234 @*
1235 @end iftex
1236 @vskip 0pt plus 1filll
1237 @iftex
1238 @sp 1
1239 LilyPond,@*
1240 The outer world of \score called \book {....}, which bundles "the musical scores" and
1241 "scores created by \score{....}" .... has a kind of document world area.
1242 In this area The music cover can also be typeset without relying on @TeX{}.
1243 @vskip 0pt plus 1filll
1244 @page
1245 @iftex
1246 @*
1247 @image{example-8-1, 6.5in}
1248 @*
1249 @end iftex
1250 @end iftex
1251 @page
1252
1253
1254
1255
1256 @ifnottex
1257 @node context Score, , context Staff, Top
1258
1259 @unnumbered context Score
1260 @end ifnottex
1261 @ifhtml
1262 @html
1263 <blockquote><blockquote><blockquote>
1264 @end html
1265
1266 I'm sorry, I'll omit it. For details, we recommend referring to "notation.pdf".`@*
1267 [.....\share\doc\lilypond\html\Documentation\notation.pdf(6,832KB) + usage.pdf(521KB) ]@*
1268
1269 @html
1270 </blockquote></blockquote></blockquote>
1271 <br />
1272 <br />
1273 @end html
1274 @*
1275 `:
1276 @end ifhtml
1277
1278
1279 @bye