musescore / musescore/MuseScore

Problems with key signs

Open
#28,612 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Click the "Create Key Signatures" button.
  • First problem:
  1. Drag any accidental onto the staff, so that additional lines are required.
    Actual behavior: additional lines are not visible at first, but when creating key signatures, additional lines are visible.
    Expected behavior: additional lines should be visible initially.
  • Second problem:
  1. Also drag any accidental onto the staff, so that it is as high or as low as possible.
    Actual behavior: the program simply does not take this accidental into account, and when creating key signatures, empty key signatures appear. At the same time, clearing key signatures does not help to get rid of this key signature and it cannot be selected. And when dragging another (or the same) accidental, the previous accidental disappears, although if you do this quickly and in a certain way, this will not help. Closing the Key Signs window and opening it helps to get rid of the accidental.
    Expected behavior: this should not happen.
  • Also, I would like to be able to add vertical and horizontal sliders (the vertical one is to make the key sign higher or lower than the third additional line, and the horizontal one is to be able to create key signs with a large number of accidentals)
  • P.S. I have no idea how, but I managed to create a key sign with one accidental (sharp), but it is located under the 19th or 20th line (if I'm not mistaken, because it is very difficult to count such a number of additional lines).
  • P.P.S. It is not clear why square and round brackets are needed in the panel with various accidentals in the "Key Signs" window, because they simply do nothing.
  • P.P.P.S. This panel itself is somehow undeveloped. Personally, I find it very difficult to understand on which (or between which) main ruler(s) I put the accidental sign.
  • P. P. P. P. S. I just realized that you can scale the window and thus put accidentals on very high or low rulers, and in P. S. I managed to make key signs without changing the window size. And yes, it seems that the need to add sliders disappears, but I think that is not so.
  • P. P. P. P. P. S. In some cases, sharp and/or flat signs may not display correctly in the description of the main accidentals when hovering over them.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/47071114-2948-450e-a5d9-6134d9c55905

https://github.com/user-attachments/assets/12f86993-13c4-4dbb-9ac7-49fb657cc251

Here, if anything, the sharps look incorrect. Sometimes the flats become incorrect, but now this only happens with sharps.

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

I was unable to check

Operating system

Windows 10

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.

Research direction

No source files or tests are named. Start by reproducing the reported cases from the Create Key Signatures button and inspect the accidental placement, additional-line rendering, clearing, selection, and hover descriptions. Done means the reported edge placements and accidental displays behave consistently without leaving unselectable or empty key signatures.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.