craigsapp
commented
2 months ago Most likely this is an error in the converter from MusicXML into MEI which is the internal format of verovio.
It is also possible that the MusicXML export from Musescore (or Sibelius or Dorico, etc.) is not correct. If the input data is incorrect, then verovio cannot be expected to convert or display it properly.
If you are using Musescore, then you can also export directly to MEI, so you must give the starting data to make this more clear where and how the input data was created, and this will in turn give a clue for where the problem occurs, which is definitely not in the final conversion of MEI into SVG with verovio.
In other words, this is not a rendering problem in verovio, but rather a data error: either in the originating program's output to MusicXML or MEI, or the problem is in the verovio import of MusicXML.
First do this test: load your MusicXML file back into the program that created it. If the problem occurs in your notation program with the reloaded MusicXML data, then the problem is in your program's export of MusicXML, and not with verovio's import of MusicXML. In that case you need to report the MusicXML export problem to your music typesetting program's developers rather than to the verovio developers.
The problem is related to a non-optimal encoding of a tie between notes in two different layers/voices. The tie that is causing problems starts on a note in voice/layer 2 (eighth note D5) and ends on a note in voice/layer 1 (half note D5). Either the exporting program is not adding the tie-end to the exported MusicXML (which can be verified by loading the MusicXML export back into the original program), or the import of MusicXML into verovio is confused because the tie end in voice/layer 1 is actually given in the MusicXML data sequence before the tie start in voice/layer 2.
In the original program, it would be better to start and end the tie on notes in the second voice/layer rather than starting in voice/layer 2 and ending it in voice/layer 1. This would avoid the problem, although if the MusicXML-to-MEI converter inside of verovio is processing this wrong, it would be good to fix.
Here is an example MEI file and resulting notation showing that verovio can handle cross voice/layer ties:
The first measure has a tie that starts in layer 2 (blue notes) and ends in a layer 1 note (red notes). I colored the tie in purple that does this:
A simpler encoding would be to place that tie end on the note in layer 2:
Click here to view MEI data for the above example notation.
```xmlTranscoded from Humdrum
As with the previous issues you have submitted, you must provide a complete (short) example that demonstrates the problem, similar to the MEI example I provide above. If you do not provide this data, then the problem cannot be fix.
There is also a separate issue with ties like this in piano music (that is beyond the scope of this issue, but is related). In piano music there is only one note played on D5, so ideally in the MEI data there will be additional information that indicates that both D5's in layer 1 and 2 tie to the ending note in layer 1.
There should be a tie from the layer 1 to layer 2 added as an invisible tie and probably some indication that the two ties are @sameas so that MIDI output will produce one note rather than produce two note attacks on the starting notes. Currently both measures in the above example produce incorrect MIDI output because of this problem: in the first measure there are three MIDI notes: two note attacks on the eighth notes, and an additional third note attack for the blue note for the half note at the ending tie. In the second measure there are two note attacks on the eighth note, but there is also a third note attack on the red note. There should be only one MIDI note instead of three in both cases.
This is complicated to deal with in conversion from MusicXML, as the converter would have to automatically detect that this is keyboard music, where only one note at a time can sound. It would also be similarly complicated to do this analysis in the MEI-to-MIDI conversion, although it might be good to add such analysis capability to verovio to adjust the MEI data for keyboard music to add the invisible ties and/or @sameas information.
Describe the problem Sometimes, the slur can become excessively long, (as picture show below)stretching across many measures and passing through notes, which severely affects the readability of the sheet music.
Expected behavior