musescore / musescore/MuseScore

Using Articulation Shortcuts (Or any shortcut using Shift) Change Note Input Behaviour

Open
#26,528 0 comments 0 reactions 1 assignee View on GitHub

@bkunda is already working on this.

Since Feb 18, 2025.

needs review 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 on a note
  2. Enter note input mode (N)
  3. Use a shortcut to select an articulation (Shift+V, Shift+O, for example)
  4. Enter a note with midi keyboard

Expected behaviour: Existing note is overwritten with the selected articulation applied
Actual behaviour: A new note is added to the previous one with the new articulation

Playing around with things a bit more, it would seem that pressing Shift once and then releasing is enough to make the next note be added to the existing note to form a chord (oddly enough, holding Shift and entering a note does not do this, as I would have expected). Pressing Shift+whatever will select the articulation, but also the (presumably buggy) behaviour of pressing and releasing shift also falls through.

Based on this, it looks like this is related to #26447 . You can add a note to an existing one, just you need to tap shift once, rather than pressing and holding, which does not work.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/dde158b9-9ce4-4e5f-b07e-5a2f7d81081d

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

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

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.