musescore / musescore/MuseScore

Add support for arpeggios on grace notes

Open
#33,702 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P3
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 musicxml importer imports them.

The behavior of the imported grace arpeggios is very unreliable. Steps:

  1. Import the attached grace1Arp.mxl.
  2. When imported it looks like this:
Image
  1. Change the view from Page View to Continuous View
  2. The grace arpeggio repositions itself next to the main note like this:
Image

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

grace1Arp.mxl.zip

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.