musescore / musescore/MuseScore

Adding an accent causes an unrelated measure to render incorrectly, overlapping its neighbours

Open
#20,995 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P2
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)

Bug description

Sometimes unrelated changes to one measure cause other measures to mess up their renderings and overlap. The messed up rendering goes away when a re-render is forced, so presumably it's some kind of cache-invalidation issue

Workaround is to Cmd-A, add a slur, and Cmd-V to undo it and reset all rendering

I don't know all the different cases that can trigger it, but it happens to me on a daily basis. I have attached a score with repro instructions that reliably trigger this misbehavior on my machine

Steps to reproduce
  1. Download this sheet: Lonely Rolling Star MODDED.mscz.zip

  2. Open it using MuseScore 4.2.0.233521125 on Mac OS-X Sonoma 14.2.1

  3. Go to the Bb5 on Voice 1 Measure 111 Beat 1.75 Staff 1 and add an accent by clicking the > button in the top toolbar

  4. The rendering for measures 114 and 115 get screwed up, with 114 on the left overlapping with 115 on the right. This rendering issue also affects printed PDFs when it is occuring

  5. Close MuseScore and re-open the sheet music, OR Cmd-A (select all) - add a Slur (via top toolbar) Cmd-Z (to undo), and it seems to re-set the rendering so measures 114 and 115 are no longer screwed up

Screenshots/Screen recordings
Screenshot 2024-01-13 at 8 17 30 PM
MuseScore Version

4.2.0.233521125

Regression

I don't know

Operating system

Mac OS-X Sonoma 14.2.1

Additional context

No response

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.