[MEI-L] Bracketed Lines in MEI

Roland, Perry D. (pdr4h) pdr4h at eservices.virginia.edu
Thu Oct 1 00:03:14 CEST 2015


Makes sense.  I’ll add the extra attributes (@staff, @layer, @place, @tstamp, @tstamp2, @dur, and @dur.ges) to my to-do list for the next release.

--
p.


From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of Andrew Hankinson
Sent: Wednesday, September 30, 2015 5:57 PM
To: Music Encoding Initiative
Subject: Re: [MEI-L] Bracketed Lines in MEI

Sibelius positions it within its own timing system, which gives you (in a measure of 4/4) 1024 positions. However, most often than not the lines are tied to a note, which is at a specific position.

I've got a process that tries to find the nearest note to a given position, and then uses that for the start/end IDs. Failing that, it will record @tstamp/@tstamp2 for start/end relative to the measure/staff/layer. It will also record the @dur.ges, just to store the "performed" duration from Sibelius (e.g., dur.ges="256p" would mean that the duration is a quarter-note in Sibelius ticks).

So @tstamp/@tstamp2 and @staff/@layer are the most critical parts of ensuring we can preserve the location of the note, beyond @start/end id.

On Sep 30, 2015, at 5:49 PM, Roland, Perry D. (pdr4h) <pdr4h at eservices.virginia.edu<mailto:pdr4h at eservices.virginia.edu>> wrote:


Ok, but are @startid and @endid sufficient?  How does Sibelius position the line?

--
p.


From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of Andrew Hankinson
Sent: Wednesday, September 30, 2015 5:42 PM
To: Music Encoding Initiative
Subject: Re: [MEI-L] Bracketed Lines in MEI

No, I'm not using any of those particular attributes since I can't really extract those from the Sibelius original.

I will go ahead and create a pull request that adds these attributes to line.

Thanks!

On Sep 30, 2015, at 5:35 PM, Roland, Perry D. (pdr4h) <pdr4h at eservices.virginia.edu<mailto:pdr4h at eservices.virginia.edu>> wrote:


Line is the appropriate entity.  I can hear the sighs now, but the ligature element in MEI is not intended for these brackets – “The ligature element should not be used for brackets in modern notation that indicate notes that were part of a ligature in the original source.” (from the description of ligature in the schema) and so it’s currently in the MEI.mensural module – it disappears when MEI.mensural is not invoked.  Creation of a similar entity for CMN or merging of ligatures in both repertoires is a possibility, but the topic needs discussion.

Currently, a line can only be positioned relative to the objects referenced by its @startid and @endid attributes using @start(ho|to|vo) and @end(ho|to|vo).  But, I don’t think there’s any reason not to allow @tstamp, @tstamp2, @staff, @layer and @place.  Even so, I think the best (that is, most precise) way to position lines is by associating them with specific events or time stamps.  The @staff, @layer, @place attributes can only be useful for making sure the lines associated with a particular staff are considered when processing that staff’s data, for instance when rendering a single staff (e.g., part extraction).

In any case,have a look at the mei-all_anyStart.odd in /develop-perry.  Line has undergone some significant changes.  Its new attributes:

form:                   dashed, dotted, solid, wavy
width:                 narrow, medium, wide, or numeric value + unit (cm|mm|in|pt|pc|px|vu)
endsym:             angledown -- 90 degree turn down (similar to Unicode 231D at end of line, 231C at start).
angleup -- 90 degree turn up (similar to Unicode 231F at end of line, 231E at start)
angleright -- 90 degree turn right (syntactic sugar for "angledown" for vertical or angled lines).
angleleft -- 90 degree turn left (syntactic sugar for "angleup" for vertical or angled lines).
arrow -- Filled, triangular arrowhead (similar to SMuFL U+EB78).
arrowopen -- Open triangular arrowhead (similar to SMuFL U+EB8A).
arrowwhite -- Unfilled, triangular arrowhead (similar to SMuFL U+EB82).
harpoonleft -- Harpoon-shaped arrowhead left of line (similar to arrowhead of Unicode U+21BD).
harpoonright -- Harpoon-shaped arrowhead right of line (similar to arrowhead of Unicode U+21BC).
none -- No start symbol.
endsymsize:      1-9 (relative size)
startsym:            [same as endsym]
startsymsize:     [same as endsym]

Andrew, when you say you’re supporting MEI 3.0.0 in SibMEI, are you using these new attributes?

--
p.


From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of Andrew Hankinson
Sent: Wednesday, September 30, 2015 4:42 PM
To: Music Encoding Initiative
Subject: [MEI-L] Bracketed Lines in MEI

Hello all,

I'm looking at the following:

<image001.png>

It seems that the best element to use in this case would be 'line'; however, the line element currently does not support durational attributes (@dur, @dur.ges, @tstamp, @tstamp2) or positional (@staff, @layer, @place).

Is there a better element to use for this object, or should a modification be proposed for the schema?

Many thanks,
-Andrew
_______________________________________________
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

_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20150930/75ea55a1/attachment.html>


More information about the mei-l mailing list