[MusicXML Import] Ottava ends at wrong place visually

• Nov 12, 2014 - 23:52
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

1. Open attached mscz (produced in 1.3).
2. 'File'>'Export'.
3. Choose 'MusicXML'.
4. 'Save'.
5. Open MusicXML.

Expected result:
Ottava ends at wrong place visually - Expected Result.png

Actual result: The ottava sounds correct, but it visually ends one note early.
Ottava ends at wrong place visually - Actual Result.png

Note: Also attached is the produced MusicXML - it opens fine in 1.3.

Using MuseScore 2.0 Nightly Build bbe146b - Mac 10.7.5.

Attachment Size
Ottava ends at wrong place visually.mscz 1.89 KB
Ottava ends at wrong place visually.xml 8.11 KB
Ottava ends at wrong place visually - Expected Result.png 65.8 KB
Ottava ends at wrong place visually - Actual Result.png 62.53 KB

Comments

• Nov 12, 2014 - 23:57

I'm assuming the problem is with import - perhaps it is both that and export?

I don't know what the issue is, and it doesn't seem possible to reproduce without the Voice entry.

Hopefully, someone with more knowledge will be able to find out.

Reply

• Dec 9, 2014 - 21:23

Initial investigation result: ottava segment length (in ticks) is correct after xml import, but track2 is not set and end element is incorrect. Still looking for the exact cause.

I suspect is it caused by the different timing in staff one and staff two. Something like incorrectly assuming the ottava ends at the note with lyric "ri" in staff one and then anchoring the ottava end to the note in staff 2 that starts at the same time as the note in staff 1.

Reply

• Dec 10, 2014 - 20:44

Cause found: missing initialization of track2 anchors the ottava at a note in the first staff. Will be fixed shortly, but I first want to verify if the same issue occurs with other spanners and verify correct handling of the corner cases. Takes a few days.

Reply