Tie not displayed

[fablau]

Hello Simon and team,
Just encountered this problem. Look at the attached XML file, the D half-note in the right hand of the piano is tied to the next D height-note, but OSMD isn't displaying it. Any ideas why?

I have drawn in red where the tie should appear in the image below:

Thanks for looking into this.

TieIssue.xml.zip

[NyuBlara]

I also encounter this issue, using the following file and OSMD@1.8.8 :

Touront-O_gloriosa.musicxml.zip

At measures 58/59, which, properly rendered, display like so :

OSMD instead renders them as follows :

[fablau]

@NyuBlara, I see the untied note has a dot, which makes it wrong for the defined time signature (which I guess is 4/4). Maybe in your case, that's why? Just wondering. I am sure @sschmidTU has a better explanation for both of us.

[NyuBlara]

@fablau Thank you for pointing this out : if you look at the first screenshot (taken from MuseScore 3), you will notice a tuplet notated over the dotted half note, which is missing in the second picture (taken from OSMD).

The MusicXML file does indeed specify that this is a single-note tuplet (lines 1651-1672) :

<note>
  <pitch>
	  <step>A</step>
	  <octave>4</octave>
  </pitch>
  <duration>6</duration>
  <tie type="start"/>
  <voice>1</voice>
  <type>half</type>
  <dot/>
  <time-modification>
	  <actual-notes>3</actual-notes>
	  <normal-notes>2</normal-notes>
	  <normal-type>quarter</normal-type>
  </time-modification>
  <stem>up</stem>
  <notations>
	  <tied type="start"/>
	  <tuplet type="start"/>
	  <tuplet type="stop"/>
  </notations>
</note>

Which, if I'm not mistaken, means that this dotted half-note is actually interpreted as three quarter notes totaling the duration of one half, therefore fitting into the file's time signature (which is 2/2).

However, OSMD does not display this single-note tuplet, which is a separate issue.

[fablau]

Oh yes, I see that now... even though it's a very unusual way of writing a tuplet. I mean, why not simply write that note as a regular single half-note? In any case, I think OSMD isn't able to handle that kind of "tuplets" (if so we can still call them!)

[NyuBlara]

I'm not sure why the author decided to do this. Presumably, it might have been out of a self-perceived consistency, since the tie ends inside a tuplet, so they might have wanted it to begin in one as well.

In either case, I think it's fair to assume that the tie not displaying is due to the same underlying cause in both of our files, regardless of my example's triplet peculiarity.

[fablau]

Yes, I agree!