Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
4 tasks done
Silverknife27 opened this issue Dec 29, 2024 · 0 comments
Open
4 tasks done
Assignees

Comments

@Silverknife27
Copy link

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

Synch.Issues.mov

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants