musescore / musescore/MuseScore

Articulations should be positioned correctly while hovering in note input mode

Open
#27,985 1 comment 0 reactions 1 assignee View on GitHub

@Eism is already working on this.

Since May 9, 2025.

P3 regression MS4 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce
  1. Select an articulation or a combination of multiple in the note input toolbar
  2. Enter note input mode (N)
  3. Hover on the staff. Articulations do not preview where they will actually be placed when the note is entered. See examples below.

The preview need not be so smart to, say, avoid colliding with other non-note elements above/below the staff, but the articulations should at least show in the order and above/below staff position they will be once entered.

Supporting files, videos and screenshots

Tenuto + accent, below staff (overlapping)
Image

Staccato (aligned to left edge rather than centered, vertical position varies)
Image Image Image

Staccato + tenuto (misaligned and stacked in wrong order)

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

Nightly. Was less egregious in some previous versions (before 4.2), though was never perfect.

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

macOS 15

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.