musescore / musescore/MuseScore

Synchronisation issues between full score and parts (when open one MS3 score in MS4)

Open
#25,002 5 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

P3 regression MS3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

in the attached file (which was originally created with MS3) the score and the parts are not synchronized correctly: In bar 17 there are two notes in the full score, but three in the part “1. Tenorhorn in B”. In the “Bariton in B” there are texts that are not present in the full score. In addition, the exercise markings have been removed from the full score in the meantime, but are still included in the parts.

to recreate:

  • open MS3.6.2 file in MS4.4.2
  • select measure 73-74
  • Tools > Explode
  • open parts
  • in the first part (1. Tenorhorn in B) is still the whole chord
Supporting files, videos and screenshots

MS4.4.2 file: test_fehler.zip
MS3.6.2 file: test_MS3.6.2.zip

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

4.4.2-242570931, revision: github-musescore-musescore-3130f97

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10 Version 2009 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.