|
From: | Lukas-Fabian Moser |
Subject: | Re: GregorianTranscriptionStaff |
Date: | Mon, 1 Aug 2022 16:44:06 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 |
Am 01.08.22 um 09:05 schrieb Werner LEMBERG:
GregorianTranscriptionStaff currently shows a time signature. Is that desirable?As discussed in https://gitlab.com/lilypond/lilypond/-/merge_requests/1515#note_1045453533 I think it makes sense to have time signatures if you transcribe polyphonic music that uses Gregorian chant notation, like pieces from the Notre Dame School period (12th to 13th century). However, this is no longer 'classical' Gregorian chant, so maybe the default should be to not show a time signature. Are there any experts who could shed more light on this topic? Maybe we should ask on the 'lilypond-user' list, too.
fwiw, I'm a bit confused about the GregorianTranscriptionStaff context - for example, in the typical liturgical situations where one uses a "modern" staff for notating Gregorian chant, one usually doesn't use stems. The Notre Dame examples you cited, on the other hand, are different matter: they use what's called "modal notation" where certain types of ligatures are used to encode one of six known rhythmic models. And at least some of the transcriptions in Apel are given with a time signature (of 6/8 as usual).
But the context type was added by Jürgen Reuter (e9ac8723c) who obviously knows his stuff, so I'm sure he had a meaningful specific application in mind; maybe it would be a good idea to specify the intended application more clearly in the documentation. CC'ing Jürgen.
Lukas
[Prev in Thread] | Current Thread | [Next in Thread] |