musescore / musescore/MuseScore

Chord symbols are played incorrectly when they include natural signs

Open
#24,984 1 comment 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Oct 1, 2024.

P3 playback 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)

Summary

When a natural sign is added anywhere in a chord symbol (via Ctrl + Shift + H), only the root note is played back.

Example 1

F plays a major chord, Fnatural plays just an F.

https://github.com/user-attachments/assets/4d9a8d66-5bca-47f0-98df-6d4e4744b6e2

Example 2

Repro steps:

  1. Add a chord symbol with 9, 11 or 13, explicitly marking it "natural" (Ctrl/Cmd-Shift-H)

Result: The chord is correctly shown, but only its root note is played
Expected: The chord is shown, and it can be actually played

Screenshot 2024-09-30 at 1 55 59 PM

Please refer to https://musescore.org/en/comment/1260997 for more details if needed.

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

OS: macOS 14.6, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97

Regression

No.

Operating system

macOS 14.6.1 (23G93)

Additional context

While it's not super common to use natural signs in chords, it does happen sometimes. One of the main reasons is to highlight that previously altered tension note is no longer there. It's also used at music schools for educational purposes (e.g., Berklee has music theory classes where such notation is used).

PS Basically, it's the same idea as with the regular use of natural signs. Even if it is not used in every score, there is no reason to not properly treat natural signs in the context of chords, as it's just a means to highlight that a note is not altered, and ideally it should be applicable to any context regardless of where it's used.

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.