blob: eba5459d8fb4c75410a16972eff55e9668cfc873 (
about) (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
@ignore
Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
When revising a translation, copy the HEAD committish of the
version that you are working on. See TRANSLATION for details.
@end ignore
@ignore
hmm, the one big page is too big, but it was really inviting to
read. this is not. maybe just scrap this menu and introduction
to index?
@end ignore
@setfilename automated-engraving.info
@settitle Obsessed with putting ink on paper
@documentencoding UTF-8
@documentlanguage en
@set web
@include macros.itexi
@afourpaper
@ifnottex
@node Top
@top
@chapheading
@end ifnottex
@unnumberedsec What is behind LilyPond?
@sourceimage{hader-collage,,,.jpeg}
LilyPond is not unique in making music notation: there are a lot of
programs that print music, and nowadays most of the newly printed
music is made with computers. Unfortunately, that also shows: just
ask any musician that plays classical music: new scores do not look as
nice as old ones.
What is the difference between hand-work and machine work, and what
has caused it? How can we improve the situation? This essay explains
problems in music notation (software), and our approach to solving
them.
@menu
* introduction:: Introduction -- what's wrong with computer music notation.
* software:: What's wrong with software -- or how Finale is not the end-all of music software.
* problem-statement:: How not to design software -- or modeling music notation.
* divide-and-conquer:: Divide and conqueror -- a blue print for automated notation.
* implementing-notation:: Impressive, but does it also work in theory -- a practical approach to capturing notation.
* engraving:: Music engraving -- the art of printing music.
* implementing-typography:: Implementing typography -- hackers attack the engraving problem.
* formatting-architecture:: A flexible program architecture -- lets us write engraving software
* scoring-esthetics:: Beautiful numbers -- how LilyPond participates in the Miss World contests.
* benchmarking:: Notation benchmarking -- is a flexible architecture enough?
* schubert:: Notation benchmarking -- project too?
* typography-features:: Typographical features -- unique to LilyPond.
* input-format:: Input format -- how to enter music.
* conclusion:: Conclusion.
@end menu
@contents
@c This essay is also available in @ref{big-page.html,one big page}.
@include automated-engraving/introduction.itexi
@include automated-engraving/software.itexi
@include automated-engraving/problem-statement.itexi
@include automated-engraving/divide-and-conquer.itexi
@include automated-engraving/implementing-notation.itexi
@include automated-engraving/engraving.itexi
@include automated-engraving/implementing-typography.itexi
@include automated-engraving/formatting-architecture.itexi
@include automated-engraving/scoring-esthetics.itexi
@include automated-engraving/benchmarking.itexi
@include automated-engraving/schubert.itexi
@include automated-engraving/typography-features.itexi
@include automated-engraving/input-format.itexi
@include automated-engraving/conclusion.itexi
@bye
|
