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

Single voice parts for non-first voice 'corrupt' when deleting rest in main score #21137

Closed
randoguyname opened this issue Jan 22, 2024 · 4 comments · Fixed by #23783
Closed
Assignees
Labels
corruption Issues involving file corruption P1 Priority: High

Comments

@randoguyname
Copy link
Contributor

Issue type

File corruption

Bug description

When deleting rests of voice 2 (and presumable other voices apart from the first) on a main score, a part score that solely contains voice 2 'corrupts', saying that there is an 'empty bar'.

Steps to reproduce

  1. Create a new score
  2. Add a part score which only shows Voice 2
Screenshot 2024-01-22 at 2 51 06 pm
  1. Write some notes in voice two then delete the entire bar (on main score)
Screenshot 2024-01-22 at 2 51 35 pm Screenshot 2024-01-22 at 2 51 47 pm
  1. Observe empty bar in part score
Screenshot 2024-01-22 at 2 51 54 pm
  1. Attempt to save and see this warning
Screenshot 2024-01-22 at 2 56 31 pm

Screenshots/Screen recordings

No response

MuseScore Version

OS: macOS 14.2, Arch.: x86_64, MuseScore version (64-bit): 4.2.0-233521125, revision: github-musescore-musescore-eb8d33c

Regression

I don't know

Operating system

macOS 14.2.1

Additional context

No response

@muse-bot muse-bot added the corruption Issues involving file corruption label Jan 22, 2024
@randoguyname
Copy link
Contributor Author

I will also add this workaround: delete the bar only in the part score and hide the rest on the main score.

@oktophonie
Copy link
Contributor

See also: #19182

@bkunda bkunda added the P1 Priority: High label Jan 23, 2024
@cbjeukendrup
Copy link
Contributor

@mike-spa This issue is assigned to me, but isn't this exactly what you were working on recently?

@mike-spa
Copy link
Contributor

Yes, indeed it is possible that this may be fixed by #23783. @oktophonie could you please also check for this while testing that PR? In any case, I'll reassign this to me

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
6 participants