musescore / musescore/MuseScore

chords.xml: Maj13 voicing duplicates Maj13#11 (F# instead of F)

Open
#32,668 2 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

I think there is a data issue in the chord definitions: Maj13 and Maj13#11 currently have the same voicing, so Maj13 behaves like a #11 chord.

Location: engraving/data/chords.xml

Excerpt from chords.xml:

<chord id="9">
    <name>Maj13#11</name>
    <xml>major-13th</xml>
    <degree>add#11</degree>
    <voicing>C E G B D F# A</voicing>
</chord>
<chord id="10">
    <name>Maj13</name>
    <xml>major-13th</xml>
    <voicing>C E G B D F# A</voicing>
</chord>

Maj13 and Maj13#11 should not be identical(?).
In standard usage, plain Maj13 implies a natural 11, not an explicit #11.
Since both entries use F#, the plain Maj13 entry is effectively encoded as Maj13#11.

Supporting files, videos and screenshots

The chords.xml file you can get here on github.

In which versions of MuseScore Studio is this issue present?

I found it in prerelease 5.0 but looking in git it looks the same in v 4.6.5

Regression

Choose option...

Operating system

Probably all OS:s

Additional context

No response

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.