forked from gregorio-project/gregorio-project.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
structure.html
215 lines (153 loc) · 13.4 KB
/
structure.html
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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<!--
Gregorio web site.
Copyright (C) 2007-2015 The Gregorio project
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
-->
<title>Gregorio project website</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta name="description" content="Free software for typesetting Gregorian chant" lang="en">
<meta name="keywords" content="Gregorian chant, gregorio, gabc, gregoriotex" lang="en">
<meta name="author" content="The Gregorio project">
<link rel="shortcut icon" href="./illus/fav.ico">
<link rel="icon" href="./illus/fav.ico">
<link rel="stylesheet" href="./style.css" type="text/css" title="default">
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
<script type="text/javascript" src="./gregorio-menu.js"></script>
<script>
var context = 'gregorio';
var title = 'Gregorio project website'
</script>
</head>
<body>
<div id="ban">
<img src="./illus/harpedroite.png" title="" class="hd" alt="" />
<a id="haut" name="haut"></a>
<div id="banniere">
</div>
</div>
<script>write_gre_menu();</script>
<div class="flux">
<!-- IE patch-->
<div class="text">
<!-- End of header -->
<!-- header -->
<script>
context = 'notation';
</script>
<h1>Structure of Gregorian Chant notation</h1>
<p>This document was written by a monk of the abbey of <a href="http://www.barroux.org" title="">Sainte-Madeleine du Barroux</a> to describe his vision of the structure of the writing of Gregorian chant. It was originally concerned with defining an XML standard for describing Gregorioan chant. While Gregorio did at one point try to implement this XML standard, that feature was so little used that it has been abandoned. Gregorio still uses this structure, however, when analyzing its gabc code, so users interested in understanding how Gregorio "thinks" about a score may find it useful.</p>
<h2>Introduction</h2>
<p>Just as our sentences are composed of words, syllables and letters, it is possible to distinguish, in the typographical transcription of Gregorian chant, neumes, neumatic elements and neumatic glyphs.</p>
<p>Thus we have the following analogy (we will explain the details later):</p>
<ul><li>words → neumes</li>
<li>syllables → neumatic elements</li>
<li>letters → neumatic glyphs</li>
</ul>
<p>Here is an example of a neume, which we will analyze throughout this document:</p>
<div class="legende">
<img src="./illus/struct-1.png" title="" alt="" />
<br />Example of a neume
</div>
<p>The first element of this neume is <img src="./illus/struct-2.png" title="" alt="" />.</p>
<p>This element itself is composed of the glyph <img src="./illus/struct-3.png" title="" alt="" /> followed by the three glyphs <img src="./illus/struct-4.png" title="" alt="" />, <img src="./illus/struct-5.png" title="" alt="" /> and <img src="./illus/struct-6.png" title="" alt="" />.</p>
<p>Our example of a neume composed of 32 notes may be surprising. It is just a choice of vocabulary: we call a <em>neume</em> <strong>“the group of notes sung on the same syllable”</strong>. This example of a neume, found in the <em>Antiphonale Monasticum</em> (Solesmes, 2005, vol. I, p. 542-543), comes from the following piece:</p>
<div class="legende">
<img src="./illus/struct-7.png" title="" alt="" />
<br />Complete score
</div>
<h2>The neumatic elements</h2>
<p>Musically, the neumatic elements are a sequence of notes sung in a connected manner and forming a certain entity. The vocabulary used here to indicate these elements vary from one liturgical book to another. Here are the names usually given to the elements that compose the neume that we took as an example:</p>
<div class="legende">
<img src="./illus/struct-examples.png" title="" alt="" />
</div>
<h3>Role of the neumatic elements</h3>
<p>These elements give an indication of rhythm by the distinctions or articulations that they introduce to the thread of the melody. It would have been possible, without changing the melody of the first eight notes of our neume, to transcribe it like this: <img src="./illus/struct-change1.png" title="" alt="" /> instead of <img src="./illus/struct-change2.png" title="" alt="" />.</p>
<p>If the second transcription has been retained instead of the first, it does not seem daring to think that this choice was dictated by a musical reason. Some would translate this nuance in the manner of singing, by distinguishing the last punctum inclinatum with a little more “weight”, a very light sustain. Just to think of articulating the two neumatic elements well can at times be sufficient to render this nuance.</p>
<p>The distinction between neumatic elements is made by “neumatic cuts”. As we can see in the neume sung on <em>Dó</em>, these cuts are more or less in length. Depending on the liturgical book, their length may vary from half a square note to two square notes.</p>
<p>Whether the musical nuance indicated by a neumatic cut is short or long, it is not the role of the typographer to care about it. But to reproduce a piece that is already written, he needs to respect his model, taking care of the neumatic cuts he sees. Indeed, these nuances have their origins in the first Gregorian chant manuscripts that were transcribed into typography this way.</p>
<h3>Definition of the neumatic element</h3>
<p>We will come back later to the notion (still a bit confused) of neumatic cut, but we can already define the <em>neumatic element</em> as <strong>“a group of notes without a neumatic cut”</strong>.</p>
<h3>The list and the number of neumatic elements</h3>
<p>Here are the various types of neumatic elements that we can find in current Gregorian chant scores:</p>
<div class="legende">
<img src="./illus/struct-examples2.png" title="" alt="" />
</div>
<p>If we don't consider the different heights (pitches) of the notes and the liquescent forms, this list is quite exhaustive for the elements with one or two notes. Starting with the three-note elements, the number of elements grows sharply, and giving the list of all the elements would appear, if not impossible, at least tiresome, and not useful for constructing a lexical typography for chant.</p>
<p>The concept of a “neumatic glyph” will let us have a simpler vocabulary, easily exhaustive for the typographical transcription of Gregorian chant.</p>
<p>But before we talk about that, we must clarify the question of spaces that we can encounter in the thread of certain neumatic elements. Indeed it is not always easy to tell the difference between, on one hand, a space inside a neumatic element, and on the other hand, a neumatic cut separating two neumatic elements.</p>
<p>As the typographer is by definition neither a musician, a musicologist, nor a gregorianist, he needs a vocabulary adapted to his work. That's why we propose to simplify the notion of neumatic cut, from a typographical point of view, and to include in it all the spaces, excluding those found:</p>
<ul>
<li>in groups of two or three successive <em>puncta quadrata</em>, <em>strophae</em> or <em>virgae</em> on the same pitch;</li>
<li>in elements starting or ending with several <em>puncta inclinata</em>.</li>
</ul>
<p>Therefore, the following written forms will be considered as only one neumatic element:</p>
<div class="legende">
<img src="./illus/struct-list1.png" title="" alt="" />
</div>
<p>But the following written forms as two different elements:</p>
<div class="legende">
<img src="./illus/struct-list2.png" title="" alt="" />
</div>
<h3>Difficulties resulting from this choice in establishing a XML standard</h3>
<p>Let us take two examples:</p>
<ul>
<li>this neumatic element: <img src="./illus/struct-diff1.png" title="" alt="" /> called <em>scandicus flexus</em>, is written in the <em>Nocturnale Romanum</em> (Hartker Verlag, 2002, p. 501), in the following way: <img src="./illus/struct-diff2.png" title="" alt="" /></li>
<li>the element <img src="./illus/struct-diff3.png" title="" alt="" /> named <em>porrectus flexus</em>, is written this way: <img src="./illus/struct-diff4.png" title="" alt="" /> (Ibid., p. 499) but we could also choose to write it more aesthetically this way: <img src="./illus/struct-diff5.png" title="" alt="" />.</li>
</ul>
<p>If we consider the <em>scandicus flexus</em> and the <em>porrectus flexus</em> typographically sometimes as only one element and sometimes as two, it is very hard to establish a standard XML representation.</p>
<p>Do we have to revert to a more musical definition of the neumatic cut and abandon the one we just defined?</p>
<p>It does not seem so, because in a lot of cases, the distinctions are debatable and indeed debated. What can be said, for example, of the written forms of the <em>porrectus flexus</em> such as these: <img src="./illus/struct-diff6.png" title="" alt="" /> and <img src="./illus/struct-diff7.png" title="" alt="" /> ? In some manuscripts they are both written like this <img src="./illus/struct-diff8.png" title="" alt="" />.</p>
<p>Not to speak of the <em>salicus</em>, the subject of so many discussions. and transcribed with the following forms:</p>
<div class="legende">
<img src="./illus/struct-salicus.png" title="" alt="" />
<br />Different representations of the salicus
</div>
<p>The solution seems to be not to give a name to the different neumatic elements. But instead, it will certainly be useful to do this at the level of the <em>neumatic glyphs</em>.</p>
<h2>The neumatic glyphs</h2>
<p>What we have said above about the great number of existing and imaginable neumatic elements and the difficulty of naming them shows that it is necessary to turn back to the first and smallest units for the typographical composition of a gregorian chant score.</p>
<p>Spontaneously a typographer will seek to analyse what are the different shapes he needs to compose his scores, and he will come to uncover four principal genres of shapes: <img src="./illus/struct-8.png" title="" alt="" /> that will be set next to one another.</p>
<p>He will also seek to simplify his task by trying to find less elementary shapes that will enable him to compose one or several notes at a time. Such as for example the following shapes:<img src="./illus/struct-9.png" title="" alt="" /></p>
<p>Typography with lead characters evidently had to invent a typeface comprising this series of elementary forms or glyphs. For our part, we have never had the occasion to see such a typeface. The creators of digital fonts have proceeded in the same way, replacing the various neumatic glyphs with their tables of characters.</p>
<h3>Definition of the neumatic glyph</h3>
<p>We can thus define the <em>neumatic glyph</em> as <strong>“a graphical sign that, alone or with others, represents a neumatic element”</strong>.</p>
<h3>The list and the number of neumatic glyphs</h3>
<p>In the first pages of most of the liturgical books of the 20<sup>th</sup> century, we can find tables of “neumes”. These tables are unfortunately the source of a certain confusion between neumatic elements and neumatic glyphs. </p>
<p>On one hand, they are generally not sufficient to give an exhaustive list of all the kinds of neumatic elements. They are made to be read by singers, not typographers, so they go further than the simple enumeration of elementary glyphs. </p>
<p>What is the maximum number of notes in a neumatic element? It seems quite hard to fix this number. Where should we stop?</p>
<div class="legende">
<img src="./illus/struct-long.png" title="" alt="" />
<br />Example of an extremely long neumatic element
</div>
<p>For example we can find in this type of tables the following “neumes”:</p>
<div class="legende">
<img src="./illus/punctum-quadratum.png" style="width:15px;" title="" alt="" />
<img src="./illus/pes.png" style="width:15px;" title="" alt="" />
<img src="./illus/scandicus.png" title="" alt="" />
<img src="./illus/scandicus2.png" title="" alt="" />
<br>punctum, pes, scandicus, and scandicus
</div>
<p>It seems obvious that the typographer won't need to have in his case a sequence of glyphs corresponding to all the possible <em>scandicus</em> forms, more so, as we can sometimes find a <em>scandicus</em> with five or six notes. To compose this kind of neumatic element, it will be simpler to put together some <em>puncta</em> and some podatuses.</p>
<p>How can we establish a simple and complete list of neumatic glyphs?</p>
<p>It seems more manageable to limit ourselves to the written forms without a space. Then we need to choose a maximum number of notes. Taking into account these two conditions, finally we must seek all the possible written forms according to the different sequences of pitches and all the variations.</p>
<!-- footer -->
</div>
<div class="bottom">
</div>
<script>initialize_menu();</script>
</body>
</html>