musescore / musescore/MuseScore

Impossibile to reinstate alterations when in "Input by duration" mode

Open
#27,311 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Mar 25, 2025.

Input by duration P2 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

When using the new "Input by duration" system, it's impossible to write a note with an alteration which is already in key signature and has not been altered inside the measure. For example, in C major you can't write a note with a natural, in F major you can't write a B flat, in G major you can't write F sharp etc.
This is a major issue when you have to reinstate an alteration after a barline, as it is required for a decent readable engraving.
[And I really love this new input mode, it looks way faster then the "Input by note name" mode.]

Supporting files, videos and screenshots

Here's an example in BbM/Gm key.
As you can see, I can't write B flat and C natural after a barline, but only if those notes have been already altered inside a measure.
You can also see in the video how reinstate the alteration is necessary after the barline.

https://github.com/user-attachments/assets/a2886a28-6807-4812-8b15-667e62ba3cc6

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

It's the same in 4.5 and 4.5.1

Regression

No.

Operating system

Windows 11

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.