[MEI-L] Encoding Notre Dame Polyphonic Neumes

Joshua Stutter josh at yokermusic.scot
Fri Mar 22 15:13:09 CET 2019 

Karen,

> I don’t think using the neume names is appropriate for this repertory
> as the theorists didn’t use these.
You're right here, I've already dispensed with them.

> The alignment is a more complex issue. Ideally you would probably want
> to number the perfections and then you would simply tag your tenor
> notes as occurring within a certain perfection.
I've already /kind of/ solved the alignment issue by using <section> as
an alignment group. I'm against tagging in a particular perfection as
that is implying that the music proceeds in a constant modal rhythm and
has length, which may not be exactly correct. All I'm attempting to do
is to align the notes together that occur at the same time and leave the
rhythm up to a further editor or a performer's interpretation,
especially with this two-part music which may be completely without
formal rhythm.

However, I'm still no closer to even beginning to customise the ODD to
fit my needs, there's some sort of SVG error which I do not understand.
Either going through Roma or cloning the MEI github and attempting to
build directly gives me this error (see my message 16th of this month)
and the MEI customization page is still broken.

Joshua.

On 17/03/2019 10:02, Karen Desmond wrote:
> Hi Joshua,
>
> Quick comment. first, I’m really glad someone is looking at modal
> notation. My first instinct though would be to not use the neumes
> module, as many of the things you are trying to do may have support
> within the measural module - where you have elements like ligatures,
> and note values like longs and breves, though I know of course that
> this not mensural and eventually would need at least its own
> notationtype attribute (and module?). I don’t think using the neume
> names is appropriate for this repertory as the theorists didn’t use
> these. For modal notation probably the most important thing you want
> to encode is how many notes within a ligature and for the specific
> case of the conjunctura, that the type of ligature is a conjunctura
> (possibly using the form element of conjunctura). You’re right that
> properly encoding the divisio is important - whether it truly
> functions as a rest, or a divisio syllabarum, etc.
>
> The alignment is a more complex issue. Ideally you would probably want
> to number the perfections and then you would simply tag your tenor
> notes as occurring within a certain perfection. However in the duplum
> the ligatures could begin in one perfection and end in another - i.e.
> if in a discant section in mode 1 you had a 3-note ligature, the notes
> would be long breve long but the first long is in the first perfection
> and the third is the second perfection, unless of course you had
> perfection be a sub-element of ligature in the tag hierarchy. 
>
> Best
>
> Karen
>
> On Sat, Mar 9, 2019 at 9:27 AM Joshua Stutter <josh at yokermusic.scot>
> wrote:
>
>     Dear all,
>
>     Fairly new MEI user, trying to encode some 13th-century Notre Dame
>     notation into MEI for a class. MEI has good support for many
>     neumes, but I'm attempting to get them to work in a polyphonic
>     context, align correctly and with good semantics. Here is a small
>     example which I'm attempting to encode:
>
>     Small Notre Dame example.
>
>     Most of the neumes can be notated and typed with the exception of
>     the complex neume FGBGA which does not have a name. This is fine
>     as this music does not stick to the usual neume types.
>
>     My first issue arises when trying to show the first tenor note D
>     is aligned with the porrectus GFG. How would I go about achieving
>     this without using semantically-incorrect spacers or invisible
>     rests or durations? What I really wish for is the possibility to
>     encode sections of polyphony in groups that are aligned together,
>     i.e. the first three neumes in the organal voice in one group,
>     then the porrectus in a new group with the tenor virga.
>
>     The second issue is the vertical lines. They are not barlines, nor
>     always rests. They are divisiones with a complex and
>     context-sensitive function. Sometimes they function as rests,
>     sometimes they are alignment marks, sometimes syllable marks.
>
>     The first attached file 'benedicamus-domino.mei' encodes this
>     example naively. Nothing is aligned and I use <barLine> where
>     divisiones are.
>
>     The second attached file 'benedicamus-domino-wish.mei' is how I
>     wish to encode this file, using a made-up element <alignmentGrp>
>     that can contain anything a <section> contains. I have also
>     replaced the <barLine> with another made-up element <divisio>.
>
>     Needless to say, I'm not concerned with the output in verovio, as
>     very little neumatic notation is supported anyway, but instead
>     encoding the alignment and elements correctly. Is something like
>     this possible in MEI already or will I have to dabble in ODD? If I
>     must, are there any links to a good workflow and documentation for
>     using ODD with MEI?
>
>     Thanks in advance for responding to this quite complex question,
>
>     Joshua Stutter.
>
>     _______________________________________________
>     mei-l mailing list
>     mei-l at lists.uni-paderborn.de <mailto:mei-l at lists.uni-paderborn.de>
>     https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
> -- 
> ---
> Karen Desmond
> Visiting Fellow, Clare Hall, and Visiting Scholar, Faculty of Music,
> University of Cambridge (Lent/Easter 2019)
> Assistant Professor of Music, Brandeis University
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20190322/82cd0342/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: notre-dame-example.jpg
Type: image/jpeg
Size: 74075 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20190322/82cd0342/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20190322/82cd0342/attachment.sig>

More information about the mei-l mailing list