musescore / musescore/MuseScore

In continuous view edits cause fermatas stacked above certain articulations to be pushed away from staff

Open
#33,061 2 comments 1 reaction 1 assignee View on GitHub

@ajuncosa is already working on this.

Since Jul 16, 2026.

engraving P3 regression MS4
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

In continuous view, edits (e.g. note input) in proximity to fermatas stacked above certain articulations cause the fermata to move ever further away from the staff.

This presents even for edits on other staves.

This does not occur for all articulations, but certainly for up/down bows, open, harmonic, etc.

Saving the project causes the fermata to return to its expected position.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/23adaa3d-4189-480f-a128-883aab2684a1

In which versions of MuseScore Studio is this issue present?

4.6.0 - latest nightlies

Regression

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

Operating system

Windows 11

Additional context

This is quite annoying, as the bug present even for edits on other staves, quickly resulting in large vertical gaps. Saving the score immediately causes the fermata to draw at the expected position, but you unavoidably experience staves jumping up and down e.g. during note input.

Possibly related to #31348, although the cause of that issue is not clear from the bug report.

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.