musescore / musescore/MuseScore

Courtesy Accidentals working inconsistently

Open
#28,896 11 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

community UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Go to Plugins > Composing/Arranging Tools > Courtesy Accidentals > Add

This may (or may not) add the correct courtesy accidentals. They are often missed. And when it does, there are no parentheses, even when this option is checked in the Configure window. I have found that going to the Configure window, unchecking and rechecking use parentheses, and clicking Add, may or may not add them correctly.

I would expect that once I've configured the plugin, simply tapping ADD should consistently find all places where they are required, and place them.

Thanks for your consideration!

Supporting files, videos and screenshots

In the attached screenshot, please look at mm 44-45, bass clef, voice one. The A naturals in 44 should get a parenthesized flat in 45.

I would happily have uploaded a file, but this forum doesn't accept MuseScoreStudio documents (?)

Image

What is the latest version of MuseScore Studio where this issue is present?

4.5.2

Regression

I was unable to check

Operating system

Mac OS 13.7.6

Additional context

Screenshot of MSS version and build

Image

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.