musescore / musescore/MuseScore
Add support for arpeggios on grace notes
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
Engraving bug (incorrect score rendering)
Description with steps to reproduce
It is unclear at the moment whether MuseScore is supposed to support arpeggios on grace chords, so I am unsure whether this is a bug in MuseScore or a bug in the musicxml import (and perhaps other importers).
The situation is this.
- The UI seems not to allow arpeggios on grace notes, but
- The
musicxmlimporter imports them.
The behavior of the imported grace arpeggios is very unreliable. Steps:
- Import the attached
grace1Arp.mxl. - When imported it looks like this:
- Change the view from Page View to Continuous View
- The grace arpeggio repositions itself next to the main note like this:
My LLM is saying this is because the arpeggio layout function called by doLayout assumes all arpeggios are attached to non-grace notes. (Switching to Continuous View is a way to get MuseScore to call doLayout.) Once the repositioning happens, the only way I have found to get back the correct positioning is to save the imported mxl as a mscz and reload it. But even then the correct positioning only lasts until the next doLayout call.
If MuseScore is not supposed to support arpeggios on grace notes, we should probably suppress importing them. Otherwise, it seems some work is needed on the MuseScore side to support them. Since my work is mainly with imports, I would like to know what the correct approach should be.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
4.7.2
Regression
I was unable to check
Operating system
macOS 14.7.8
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.