musescore / musescore/MuseScore

Beams spanning barlines cause incorrect rendering in Continuous View (Horz)

Open
#25,926 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Steps to recreate 100%

  1. Open sample score (beam_bug.mscz)
  2. Ensure you are in Continuous View (Horizontal).
  3. Note that some some beams that span measures were created (e.g. between measures 2 and 3)
  4. Select the third eighth note d in measure 4.
  5. Move the note up one half step (other edits will cause this as well...)
  6. Observe incorrect rendering (beam extends backwards and stem of final note is incorrect)
  7. It's purely a rendering issue. If you select the instruments panel and click and re-click the eye to show / hide the instrument, the line will be correctly rendered again.

Found in MSS 4.4.4 - still present on Nightly Build 12/26/2024. Do not recall seeing this in earlier versions of 4.x, but not sure exactly when this started occurring.

Supporting files, videos and screenshots

image
image
beam bug.zip

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-243610304, revision: github-musescore-musescore-4c05925

Regression

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

Operating system

Edition Windows 10 Home Version 22H2 Installed on ‎12/‎5/‎2020 OS build 19045.5247 Experience Windows Feature Experience Pack 1000.19060.1000.0

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.