musescore / musescore/MuseScore

Synchronization/DeSynchronization Issues with stems and beams between main score/parts

Open
#25,942 1 comment 1 reaction 3 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)

Description with steps to reproduce

1: Paste your cue into main score layer 1 of the spot you want.
2. hide all of it
3. go to part and desynchronize all of it
4. make it visible
5. go back to main score and look at the notes of the cue

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/f3fa5b58-ae12-4a0a-aad7-2508bd175cfb

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

4.4.4

Regression

No.

Operating system

macOS 15.2

Additional context

The main issue regarding this bug is the stems and beaming within the synchronization between the main score and parts. The synchronization settings flick on (specifically the stems and beams) when the user tries to implement something different from the main score. This can also be seen across different layers and gets super confusing when having a rest in the main score and just the cue notes in the part.

Screenshot 2024-12-29 at 10 00 47 AM

At the end of the day though, this issue is arduous to deal with in regard to cueing. You would have to manually highlight certain elements to hide them on the main score.

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.