No subject


Tue Jul 7 09:37:32 CEST 2009


<score>
 <scoredef key.sig=3D"3s" meter.count=3D"3" meter.unit=3D"4">
   <staffdef n=3D"1"/>
 </scoredef>
 <section>
   <measure>
     <staff n=3D"1">
       <layer n=3D"1">
         <tuplet num.place=3D"above" num.format=3D"count" bracket.visible=
=3D"false">
           <note pname=3D"a" oct=3D"4" dur=3D"8"/>
           <note pname=3D"c" oct=3D"5"/>
           <note pname=3D"e"/>
           <note pname=3D"g"/>
           <note pname=3D"e"/>
           <note pname=3D"g"/>
           <note pname=3D"a"/>
         </tuplet>
       </layer>
       <layer n=3D"2">
         <tuplet num.place=3D"below" num.format=3D"count" bracket.visible=
=3D"false">
           <note pname=3D"e" oct=3D"4" dur=3D"16"/>
           <note pname=3D"d"/>
           <note pname=3D"c" dur=3D"8"/>
           <note pname=3D"e"/>
           <note pname=3D"a"/>
           <note pname=3D"g"/>
         </tuplet>
       </layer>
     </staff>
   </measure>
 </section>
</score>

Either the logical duration of the <tuplet> or the <note> needs to be expli=
cit,
or the tuplet factor needs to be explicit.  For example: "7 in the
time of 6" for
the first layer. The "7" can be extracted (painfully) from the data, but th=
e
"6" cannot.  Relying on the logical duration of the <measure> will work in
this particular case, but not in the general case. Suppose that you have:

<measure in 3/4 meter>
    <tuplet/>
    <tuplet/>
</measure>

Who is to say that the first tuplet takes two beats and the second tuplet
takes one beat, or vice-versa?

An unrelated question: you didn't specify oct/dur values for all
notes.  Is this just
due to being parsimonious for illustration purposes, or is this an
allowed property
of (note) attributes in MEI to inherit unset attribute values from previous
elements (notes)?

-=3D+Craig

_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de
https://lists.uni-paderborn.de/mailman/listinfo/mei-l=



More information about the mei-l mailing list