<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">As usual, Craig is faster at the keyboard than I.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Also, it seems I forgot about the use of <beam> within <beam> as a method of dealing with beamed grace notes. Ah, well, can’t remember everything. <sigh/> So, it seems the
side effect is a useful one. </span><span style="font-family:Wingdings;color:black">J</span><span style="font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">As for Craig’s last 3 examples, I wouldn’t attempt to represent them in a single layer. This kind of notation is mostly used to indicate 2 “somethings” -- either 2 “voices” from
a single instrument or a single “voice” being played on 2 strings. In either case, it’s easier to treat it/them as 2 layers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">p.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mei-l [mailto:mei-l-bounces+pdr4h=virginia.edu@lists.uni-paderborn.de]
<b>On Behalf Of </b>Craig Sapp<br>
<b>Sent:</b> Monday, August 11, 2014 5:25 PM<br>
<b>To:</b> Music Encoding Initiative<br>
<b>Subject:</b> Re: [MEI-L] Questions about Beaming<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Christopher,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">You can wait for someone else to comment more precisely, but in the meantime here are examples as points of discussion:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><img width="562" height="147" id="_x0000_i1025" src="cid:image002.jpg@01CFB58F.E7C1EAF0"><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">In this case <beamSpan> is needed to represent the first beam on the bottom staff. If there were both <beam> and <beamSpan> at the same time for this case, I would interpret this as "use the <beamSpan> directions unless the notation renderer
cannot handle it (particularly Finale...), in which case fall back to the <beam> directions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The only case I have come across for nested beams would be that grace-note beams are independent of regular beams:<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><img width="382" height="170" id="_x0000_i1026" src="cid:image003.png@01CFB58F.E7C1EAF0"><o:p></o:p></p>
</div>
<p class="MsoNormal">In this case the beam organization would be:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <beam> grace-A, grace-B </beam><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <beam> regular-A, regular-G# <beam>grace-A, grace-B</beam>, regular-A </beam><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">How would the following example be encoded in MEI (from a hypothetical violin repertory, indicating string numbers via beaming)? This might also be implemented as a single layer with nested beams:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><img width="562" height="110" id="_x0000_i1027" src="cid:image005.jpg@01CFB58F.E7C1EAF0"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">The following example would then require <beamSpan>s (or a mixture of <beamSpan>s and <beam>s):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p></o:p></p>
<div>
<p class="MsoNormal"><img width="562" height="127" id="_x0000_i1028" src="cid:image007.jpg@01CFB58F.E7C1EAF0"><o:p></o:p></p>
</div>
<p class="MsoNormal">Now I am wondering how this can be encoded as in a single layer:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><img width="562" height="115" id="_x0000_i1029" src="cid:image009.jpg@01CFB58F.E7C1EAF0"><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-=+Craig<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 11 August 2014 13:23, Christopher Antila <<a href="mailto:christopher@antila.ca" target="_blank">christopher@antila.ca</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Greetings MEI List Members:<br>
<br>
I have another set of questions related to importing MEI to music21!<br>
<br>
This time I'm having issues with beams, so I hope someone can help<br>
clarify the MEI Guidelines. Though it may seem like I'm splitting hairs,<br>
I'm really looking for answers to two specific questions: (1) what's the<br>
order of precedence in beam specification? And (2) what do nested <beam><br>
elements mean?<br>
<br>
Elaboration.<br>
<br>
1.) There are (at least?) three ways to encode beams: <beam>,<br>
<beamSpan>, and @beam. What's the order of precedence for when more than<br>
one of these are specified for the same element? My feeling is that a<br>
<beamSpan> shall be overridden by a <beam>, which shall be overridden by<br>
the @beam attribute. Why? While <beamSpan> cannot indicate a beam<br>
number, <beam> can imply a beam number, and @beam specifically requires<br>
beam numbers. Even though an "order of precedence" is probably beyond<br>
the scope of what MEI will want to specify, it would be helpful to<br>
disambiguate the different levels of specificity in the Guideliness---if<br>
indeed I'm understanding the situation properly.<br>
<br>
2.) On the topic of the <beam> element's implied beam numbers, what do<br>
nested <beam> elements mean? To me these seem to specify the primary<br>
then secondary then tertiary, etc., beams for deeper and deeper nesting.<br>
However, the Guidelines (pg.82) say the "visual rendition of a set of<br>
beamed notes is presumed to be handled by rendering processes," which<br>
implies that secondary beaming cannot be encoded with <beam> elements.<br>
In fact, we could take this further and say that primary beams also<br>
cannot be specified with <beam> elements: the elements between <beam><br>
tags are merely "explicitly beamed," in that they have at least one<br>
beam, but the Guidelines do not actually specify that they must share<br>
*the same* beam, since that decision is a visual one, and therefore<br>
"presumed to be handled by rendering processes." (Except, of course,<br>
when something like @breaksec will specify an aspect of the visual<br>
rendition...?)<br>
<br>
An attempted "common sense" reading of the Guidelines suggests that<br>
everything within a set of <beam> tags will share the same primary beam.<br>
Secondary beams will be specified by some built-in default, by a<br>
@beam.group attribute, or the @breaksec attribute. If this is the<br>
intended interpretation, it leaves open the question of how to handled<br>
nested <beam> elements.<br>
<br>
Thank you in advance for your feedback. As always, I would be happy to<br>
help clarify my questions if required.<br>
<span style="color:#888888"><br>
<br>
<span class="hoenzb">Christopher</span><br>
</span><br>
_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>