musescore / musescore/MuseScore

Adding or deleting key signature in a part adds it to/removes it from that instrument only

Open
#23,934 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P1
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
  1. Create a score with more than one instruments
  2. Add a few bars of notes in one instrument
  3. Open the part for that instrument
  4. Add a key signature a few bars in
  5. Return to the score and note that the key signature has only been applied to that instrument (like a 'local' key sig).

Note that deletion suffers from the same problem in reverse:

  1. Create a score with more than one instrument
  2. Add a key signature a few bars in (in the score)
  3. Open one of the parts, find the key signature there and delete it
  4. Return to the score and see that it's only been deleted in that instrument
Supporting files, videos and screenshots

Adding

Score:
image

Key signature added in Violin I part:
image

Returning to score, key sig appears only in that part:
image

Deleting

Score:
image

After deleting the key sig in the Vl 1 part:
image

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

3.6.2; 4.0.2; 4.1.1; 4.2.1; 4.3.2; master
[the deletion problem only arises from 4.2.1 on, as this operation was simply prevented in parts in earlier versions]

Regression

No.

Operating system

Linux (but presumably any)

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.