You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Supporting files, videos and screenshots
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
The text was updated successfully, but these errors were encountered:
And while at it consider making it easier to enter a natural, like by a simple H rather than Ctrl/Cmd+Shift+H, simular to how it is possible already for RNA input
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Please refer to https://musescore.org/en/comment/1260997 for more details if needed.
Repro steps:
Result:
Expected:
Supporting files, videos and screenshots
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
The text was updated successfully, but these errors were encountered: