musescore / musescore/MuseScore
MusicXML import of Sibelius ottava handling broken
@miiizen is already working on this.
Since Sep 14, 2024.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
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
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
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.