112:
88:
projects in computational musicology. More importantly, GUIDO is designed in a way that when using such custom extensions, the resulting GUIDO data can still be processed by other applications that support GUIDO but are not aware of the custom extensions, which are gracefully ignored. This design also greatly facilitates the incremental implementation of GUIDO support in music software, which can speed up the software development process significantly, especially for research software and prototypes.
91:
GUIDO has been split into three consecutive layers: Basic GUIDO introduces the main concepts of the GUIDO design and allows to represent much of the conventional music of today. Advanced GUIDO extends Basic GUIDO by adding exact score-formatting and some more advanced musical concepts. Finally,
87:
GUIDO Music
Notation is designed as a flexible and easily extensible open standard. In particular, its syntax does not restrict the features it can represent. Thus, GUIDO can be easily adapted and customized to cover specialized musical concepts as might be required in the context of research
66:). Later developments have been done by the SALIERI Project by Holger H. Hoos, Kai Renz and Jürgen F. Kilian. GUIDO Music Notation has been designed to represent music in a logical format (with the ability to render to sheet music), whereas
299:
Holger H. Hoos, Keith A. Hamel, Kai Renz, Jürgen Kilian: The GUIDO Music
Notation Format - A Novel Approach for Adequately Representing Score-level Music. Proceedings of ICMC'98, p. 451-454, ICMA, San Francisco,
296:
Holger H. Hoos, Keith A. Hamel, Kai Renz, and Jürgen Kilian: Representing Score-Level Music Using the GUIDO Music-Notation Format. Computing in
Musicology, Vol 12, MIT Press, 2001.
306:
Kai Renz: Algorithms and Data
Structures for a Music Notation System based on GUIDO Music Notation. PhD thesis. Fachbereich Informatik, Technische Universität Darmstadt, 2002.
303:
Holger H. Hoos, Keith A. Hamel, Kai Renz, Jürgen Kilian: GUIDO Music
Notation - Towards an Adequate Representation of Score-level Music. Proceedings of JIM'98, LMA-CNSR, 1998.
84:
GUIDO is not primarily focused on conventional music notation, but has been invented as an open format, capable of storing musical, structural, and notational information.
104:
input format. Two obvious differences are the specification of octaves and durations, as shown in the example below. Both formats are to some extent inspired by the
78:
which means that simple musical concepts are represented in a simple way and only complex notions require more complex representations.
39:
59:
47:
92:
Extended GUIDO can represent user-defined extensions, like microtonal information or user defined pitch classes.
370:
111:
316:
28:
35:
20:
364:
343:
116:
23:
format designed to logically represent all aspects of music in a manner that is both
321:
101:
55:
354:
79:
326:
67:
24:
43:
31:, who pioneered today's conventional musical notation 1,000 years ago.
63:
51:
110:
105:
27:-readable and easily readable by human beings. It was named after
357:– Classroom introduction and exercises for GUIDO Music Notation.
331:
348:
70:
is more narrowly focused on typesetting sheet music.
100:Basic GUIDO notation is similar to that of the
8:
74:The basic idea behind the GUIDO design is
351:– Renders GUIDO to sheet music online
7:
14:
40:Technische Universität Darmstadt
355:Music 253, Stanford University
60:University of British Columbia
48:University of British Columbia
1:
108:format for typesetting text.
96:Example of a GUIDO input file
34:GUIDO was first designed by
387:
76:representational adequacy
120:
287:
114:
115:Opening phrases of "
17:GUIDO Music Notation
288:
132:"treble"
378:
349:GUIDO Noteserver
284:
281:
277:
274:
271:
268:
265:
262:
259:
256:
253:
250:
247:
244:
241:
237:
234:
231:
228:
225:
222:
218:
215:
211:
208:
205:
201:
198:
195:
192:
189:
186:
182:
179:
175:
172:
169:
166:
163:
160:
157:
154:
151:
148:
145:
142:
139:
136:
133:
130:
127:
124:
386:
385:
381:
380:
379:
377:
376:
375:
361:
360:
340:
317:Guido of Arezzo
313:
293:
286:
285:
282:
279:
275:
272:
269:
266:
263:
260:
257:
254:
251:
248:
245:
242:
239:
235:
232:
229:
226:
223:
220:
216:
213:
209:
206:
203:
199:
196:
193:
190:
187:
184:
180:
177:
173:
170:
167:
164:
161:
158:
156:"4/4"
155:
152:
149:
146:
143:
140:
137:
134:
131:
128:
125:
122:
98:
29:Guido of Arezzo
12:
11:
5:
384:
382:
374:
373:
363:
362:
359:
358:
352:
346:
344:GUIDO Homepage
339:
338:External links
336:
335:
334:
329:
324:
319:
312:
309:
308:
307:
304:
301:
297:
292:
289:
121:
97:
94:
82:
81:
36:Holger H. Hoos
21:music notation
19:is a computer
13:
10:
9:
6:
4:
3:
2:
383:
372:
369:
368:
366:
356:
353:
350:
347:
345:
342:
341:
337:
333:
330:
328:
325:
323:
320:
318:
315:
314:
310:
305:
302:
298:
295:
294:
290:
144:"D"
118:
117:O Sanctissima
113:
109:
107:
103:
95:
93:
89:
85:
80:
77:
73:
72:
71:
69:
65:
61:
57:
53:
49:
45:
41:
37:
32:
30:
26:
22:
18:
371:Scorewriters
322:GNU LilyPond
99:
90:
86:
83:
75:
33:
16:
15:
56:Keith Hamel
46:, now at
38:(then at
365:Category
327:MusicXML
311:See also
102:LilyPond
68:LilyPond
25:computer
291:Sources
44:Germany
150:\meter
64:Canada
54:) and
52:Canada
300:1998.
126:\clef
106:LaTeX
332:MIDI
159:>
153:<
147:>
141:<
138:\key
135:>
129:<
255:2/4
168:1/2
367::
267:/2
230:/4
214:4.
194:/4
178:4.
165:1*
119:"
62:,
50:,
42:,
283:]
280:1
278:/
276:a
273:1
270:b
264:#
261:c
258:d
252:#
249:c
246:b
243:a
240:2
238:/
236:a
233:g
227:#
224:f
221:8
219:/
217:g
212:/
210:a
207:b
204:2
202:/
200:a
197:g
191:#
188:f
185:8
183:/
181:g
176:/
174:a
171:b
162:a
123:[
58:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
