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

Joining measures in parts corrupts score #17115

Closed
jonarnoldmusic opened this issue Apr 3, 2023 · 6 comments · Fixed by #19271
Closed

Joining measures in parts corrupts score #17115

jonarnoldmusic opened this issue Apr 3, 2023 · 6 comments · Fixed by #19271
Assignees
Labels
corruption Issues involving file corruption P1 Priority: High
Projects

Comments

@jonarnoldmusic
Copy link

jonarnoldmusic commented Apr 3, 2023

Issue type

File corruption

Bug description

When inputting notation into a score, if you use join measures in the part, the other parts receive null content in that measure and the score is corrupted.

Steps to reproduce

  1. Open a score with multiple parts.
  2. Open a part, select measures, Tools->Measures->Join Selected Measures
  3. Go back to score. All other parts now have null content in resulting measure.
  4. Score corruption dialog reports results like:
    Incomplete measure: Full score, measure 5, staff 1. Found: 0/1. Expected: 8/2.
    Incomplete measure: Full score, measure 5, staff 2. Found: 0/1. Expected: 8/2.
    Incomplete measure: Full score, measure 5, staff 3. Found: 0/1. Expected: 8/2.
    Incomplete measure: Part score: Cantus, measure 5, staff 1. Found: 0/1. Expected: 8/2.
    Incomplete measure: Part score: Altus, measure 5, staff 1. Found: 0/1. Expected: 8/2.
    Incomplete measure: Part score: Tenor, measure 5, staff 1. Found: 0/1. Expected: 8/2.

Screenshots/Screen recordings

Screenshot 2023-04-02 202700

MuseScore Version

OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651553, revision: github-musescore-musescore-dbe7c6d

Regression

I don't know

Operating system

Windows 11

Additional context

No response

@muse-bot muse-bot added the corruption Issues involving file corruption label Apr 3, 2023
@oktophonie oktophonie added this to To do in Parts via automation Apr 3, 2023
@oktophonie oktophonie added the P1 Priority: High label Jul 10, 2023
@oMrSmith
Copy link

Maybe it would make sense to restrict the function to split or joint measures to the score
as it will apply to all parts anyway...

@cbjeukendrup
Copy link
Contributor

Or at least under the hood, this (and almost all other operations involving measures) should happen via the master score, to make sure that all parts and all staves are updated.

@TheLostHoosier
Copy link

Maybe it would make sense to restrict the function to split or joint measures to the score as it will apply to all parts anyway...

The problem is, I get the same error if I do either a join or split or partial delete from within the score. It doesn't matter if I have the parts showing or not. Once I've had a part generated, I cannot perform any of those functions.

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

@sammik
Copy link
Contributor

sammik commented Sep 4, 2023

@cbjeukendrup please check #19271

@sammik
Copy link
Contributor

sammik commented Sep 4, 2023

@cbjeukendrup please check #19271

Hm, it seems, some Skeletons in the closet appeared.
working on it

@sammik
Copy link
Contributor

sammik commented Sep 4, 2023

Should be OK now.

@cbjeukendrup cbjeukendrup moved this from To do to Review in progress in Parts Sep 14, 2023
Parts automation moved this from Review in progress to Done Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
corruption Issues involving file corruption P1 Priority: High
Projects
Status: Done
Parts
  
Done
Development

Successfully merging a pull request may close this issue.

7 participants