musescore / musescore/MuseScore
Parsing of interval qualities in chord symbols, when the chord quality already exist
Open
@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
- 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'.
- 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).
- 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'.
- 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.
- 'MaugX' and 'maugX' can't be parsed properly.
Problem to be solved
- For example, the chord symbol 'CMm7' is unable to be parsed currently, when it should be interpreted as 'C7'.
- For example, the chord symbol 'CmM11' gets parsed as 'Cmadd11' currently, when it should be interpreted as 'CmM7(9)(11)'.
- For example, the chord symbol 'CMdim7' gets parsed as 'C - E♭ - G♭ - B' currently, when it should be interpreted as 'C - E - G - B𝄫'.
- (omitted)
- '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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.