Line extenders #3188

craigsapp · 2022-12-31T15:59:34Z

craigsapp
Dec 31, 2022
Collaborator

What is the status of line extenders in verovio? They are implemented for <dir> but not for <harm>, for example.

Here is an example for discussion:

MEI data for above example

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="https://music-encoding.org/schema/dev/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="https://music-encoding.org/schema/dev/mei-all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei" meiversion="5.0.0-dev">
 <meiHead>
  <fileDesc>
   <titleStmt>
    <title />
   </titleStmt>
   <pubStmt />
  </fileDesc>
  <encodingDesc>
   <appInfo>
    <application isodate="2022-12-31T06:09:23" version="3.15.0-dev-6887ca9">
     <name>Verovio</name>
     <p>Transcoded from Humdrum</p>
    </application>
   </appInfo>
  </encodingDesc>
  <workList>
   <work>
    <title />
   </work>
  </workList>
 </meiHead>
 <music>
  <body>
   <mdiv xml:id="mevugrg">
    <score xml:id="s1j42n4n">
     <scoreDef xml:id="s1wpp16w" midi.bpm="400.000000">
      <staffGrp xml:id="shhfsym">
       <staffDef xml:id="staffdef-L1F1" n="1" lines="5">
        <clef xml:id="clef-L2F1" shape="G" line="2" />
        <meterSig xml:id="metersig-L3F1" count="4" unit="4" />
       </staffDef>
      </staffGrp>
     </scoreDef>
     <section xml:id="section-L1F1">
      <measure xml:id="measure-L1" n="1">
       <staff xml:id="staff-L1F1" n="1">
        <layer xml:id="layer-L1F1N1" n="1">
         <note xml:id="note-L5F1" dur="1" oct="4" pname="c" accid.ges="n" />
        </layer>
       </staff>
       <dir xml:id="dir-L5F2" tstamp2="2m+0" vgrp="100" staff="1" tstamp="1.000000">cresc.</dir>
       <harm xml:id="harm-L5F3" tstamp2="2m+0" place="above" type="deg" place="below" staff="1" tstamp="1.000000" n="3">I</harm>
      </measure>
      <measure xml:id="measure-L6" n="2">
       <staff xml:id="staff-L6F1N1" n="1">
        <layer xml:id="layer-L6F1N1" n="1">
         <note xml:id="note-L7F1" dur="1" oct="4" pname="d" accid.ges="n" />
        </layer>
       </staff>
      </measure>
      <measure xml:id="measure-L8" n="3">
       <staff xml:id="staff-L8F1N1" n="1">
        <layer xml:id="layer-L8F1N1" n="1">
         <note xml:id="note-L9F1" dur="1" oct="4" pname="e" accid.ges="n" />
        </layer>
       </staff>
       <dynam xml:id="dynam-L9F2" staff="1" tstamp="1.000000" vgrp="100">pp</dynam>
       <harm xml:id="harm-L9F3" place="above" type="deg" place="below" staff="1" tstamp="1.000000" n="3">iii</harm>
      </measure>
     </section>
    </score>
   </mdiv>
  </body>
 </music>
</mei>

Here are the dir and harm of the first and last measure:

<dir xml:id="dir-L5F2" tstamp2="2m+0" vgrp="100" staff="1" tstamp="1.000000">cresc.</dir>
<harm xml:id="harm-L5F3" tstamp2="2m+0" place="above" type="deg" place="below" staff="1" tstamp="1.000000" n="3">I</harm>

<dynam xml:id="dynam-L9F2" staff="1" tstamp="1.000000" vgrp="100">pp</dynam>
<harm xml:id="harm-L9F3" place="above" type="deg" place="below" staff="1" tstamp="1.000000" n="3">iii</harm>

tstamp2 is used to generate a line extender for <dir>. I would say that this behavior is not great: dir@extender should be set to true in order for a line to be displayed. It may be useful to specify the duration of a <dir> without displaying a line. An example application would be for MIDI rendering: the tstamp2 can be used to calculate the gradual loudness increase of the "cresc." even if there were not a line after the dir.
Using endid rather than tstamp2 does not produce a line after cresc.. Ideally this would also be implemented (provided that @extender="true").
When endid is used to attach to another element, and the line is expected to be exactly horizontal, then the two elements should be set to the same vertical group. (generic lines are not necessarily horizontal, but line extenders on dir (harm, fing, etc.) should be expected to be horizontal by default. Notice that the "cresc" and the "pp" do not align.
Related to the non-alignment of the "cresc." and "pp": I put @vgrp="100" on both of them and they still do not align. Is that a regression? (I am thinking it is)
I tried tstamp2 for the <harm> data in the first measure and it does not draw a line after the I. It would be good to implement that (for which I would create an issue, but I see that line extensions need some discussion first).
For example, dynamics such as "cresc." will typically require a dashed line as the extender, but harm, fing and maybe other elements (such as text which uses @con) typically use a solid line as an extender.
Related to this: how can the extender be stylized? When @extender="true" how can line attributes be conveyed? I am presuming that in this case a <line> would be added as a child to the <harm>, <dir> etc. element to control these values.
Related to the above bullet point, if there is a line chid of harm, does (should) harm@extender="true" still need to be set? I would say that if there is a line child, then that means harm@extender should be ignored if empty, and perhaps the line should be suppressed from the rendering if harm@extender="fase". (to allow a stored line to be hidden or shown depending on the style of notation that is desired.)
And if the parent element contains a @tstamp2 or @endid, then the child line should adopt that attribute unless it is overridden in the child line.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Line extenders #3188

{{title}}

Replies: 0 comments

Select a reply

Line extenders #3188

craigsapp Dec 31, 2022 Collaborator

Replies: 0 comments

craigsapp
Dec 31, 2022
Collaborator