musescore / musescore/MuseScore
[MusicXML] Rhythmic slash notation badly handled
Nobody has claimed this yet.
- 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
- Enter some chords
- Toggle rhythmic slash notation
- Export to MusicXML
- Import exported file
Currently chords in slash notation are exported with invisible noteheads except for one which is marked as slash notehead (because MuseScore sets all noteheads except one to invisible). This should be exported by using a <slash> element at the beginning and the end of a section with rhythmic slash notation.
Supporting files, videos and screenshots
Entered notation
After ex- and reimport
Test files
What is the latest version of MuseScore Studio where this issue is present?
latest nightly build
Regression
No.
Operating system
macOS 15
Additional context
Wrong import of (properly encoded) slash notation was reported in #16216.
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.
Research direction
Start by opening rhythmic_slash.zip and reproducing the MusicXML export/import workflow described in the issue. Compare the exported XML and the reimported notation; done means rhythmic slash sections are represented with slash elements at their boundaries and survive the round trip correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, xml
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100