musescore / musescore/MuseScore

Parsing of interval qualities in chord symbols, when the chord quality already exist

Open
#27,660 0 comments 0 reactions 2 assignees View on GitHub

@bkunda is already working on this.

Since Apr 15, 2025.

feature request needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea
  1. Currently in chord symbol handling, the 'maj', 'aug' and 'dim' can each be used as interval quality, while 'min' can't be. This will make 'Mm7' unable to parse, although it can be written directly as '7'.
  2. Currently, if a chord is an extended chord and the interval is preceded by interval quality, it will be interpreted as an added chord. I tend to interpret the 7th as modified by the corresponding quality, and then add M9, P11 and M13 (just like the major scale).
  3. In principle, interval quality indicates the quality of the interval of the root note. However, there seems to be an issue with the parsing of 'dim'.
  4. Follow up on the previous one. How should 'M11' be handled? My opinion is that both 'maj' and 'min' should be interpreted as pure intervals in specific situations.
  5. 'MaugX' and 'maugX' can't be parsed properly.
Problem to be solved
  1. For example, the chord symbol 'CMm7' is unable to be parsed currently, when it should be interpreted as 'C7'.
  2. For example, the chord symbol 'CmM11' gets parsed as 'Cmadd11' currently, when it should be interpreted as 'CmM7(9)(11)'.
  3. For example, the chord symbol 'CMdim7' gets parsed as 'C - E♭ - G♭ - B' currently, when it should be interpreted as 'C - E - G - B𝄫'.
  4. (omitted)
  5. 'MaugX', 'maugX' should be able to be parsed like 'majaugX', 'minaugX'.
Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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.