MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
[originally discussed in w3c/musicxml/discussions/552]
The MusicXML file below found in the internet (and shortened) demonstrates the handling of <octave-shift> as done by Sibelius 18.12.0. Here is the (correct) rendering of the file with Finale 27.4:
According to #21499, MuseScore should be able to handle this. However, I get the following, incorrect result.
Since Finale apparently handles <octave-shift> similarly to Sibelius (it also works if I remove the <software>...Sibelius...</software> tag), the intended fix in #21499 should be extended to cover Finale MusicXML files, too.
This is probably the same issue as #24729, i.e., a wrong interpretation of <offset>. Not sure, though. As mentioned in w3c/musicxml/discussions/552, PR #21499 does work for other examples.
Issue type
Import/export issue
Description with steps to reproduce
[originally discussed in w3c/musicxml/discussions/552]
The MusicXML file below found in the internet (and shortened) demonstrates the handling of
<octave-shift>
as done by Sibelius 18.12.0. Here is the (correct) rendering of the file with Finale 27.4:According to #21499, MuseScore should be able to handle this. However, I get the following, incorrect result.
Since Finale apparently handles
<octave-shift>
similarly to Sibelius (it also works if I remove the<software>...Sibelius...</software>
tag), the intended fix in #21499 should be extended to cover Finale MusicXML files, too.Supporting files, videos and screenshots
Sibelius test file
What is the latest version of MuseScore Studio where this issue is present?
OS: openSUSE Leap 15.5, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-242560303, revision: github-musescore-musescore-ac76040
Regression
I was unable to check
Operating system
openSUSE Leap 15.5
Additional context
No response
Checklist