musescore / musescore/MuseScore

Flipped notehead, truncated stem caused by adjusted beam, layout element

Open
#33,708 2 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Apparently a reoccurrence of https://github.com/musescore/MuseScore/issues/24823 that was fixed in 4.5

I found two instances. It only happens when the beam was adjusted and in the presence of anything layout related (cf. below: 3rd system unaffected), but that's not sufficient to reliably reproduce it. System locks can cause the issue anywhere, other layout items only in the last measure. Also occurs in the very last measure of a score. Forcing the layout to update in any way remedies the issue (until the file is opened again), same as https://github.com/musescore/MuseScore/issues/24823

Supporting files, videos and screenshots
Image

flipped.zip

In which versions of MuseScore Studio is this issue present?

MuseScore Studio version (64-bit): 4.7.2-260525085, revision: github-musescore-musescore-69af3e1

Regression

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

Operating system

OS: Windows 10 Version 22H2 or later, Arch.: x86_64

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.