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

Rests missing in parts for second voice #19182

Closed
Mansent opened this issue Aug 26, 2023 · 1 comment · Fixed by #23554
Closed

Rests missing in parts for second voice #19182

Mansent opened this issue Aug 26, 2023 · 1 comment · Fixed by #23554
Assignees
Labels
engraving P1 Priority: High

Comments

@Mansent
Copy link

Mansent commented Aug 26, 2023

Issue type

Choose option...

Bug description

No response

Steps to reproduce

  1. Create this score:
    Bildschirmfoto vom 2023-08-26 19-57-12
  2. Delete the rest in second voice
  3. Open the part for this instrument
  4. Only display 2nd voice in the part
    You get this:
    Bildschirmfoto vom 2023-08-26 20-00-17
    I would expect that since the first voice is missing, the rests are properly displayed

Screenshots/Screen recordings

Here the practical example how i stumbled on this to show why it makes sense to fix this. I have an orchestral score with this flute line:
Bildschirmfoto vom 2023-08-26 19-46-20

In orchestral scores, it is common practise to leave out the rests for the second voice. However if I generate part for the second flute, it looks like this:
Bildschirmfoto vom 2023-08-26 19-52-10

This is not useful to the flute player. In this example I also get this ugly whole note rest which doesn't belong there.

MuseScore Version

MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

Regression

Choose option...

Operating system

Linux Mint 21.1, Arch.: x86_64

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engraving P1 Priority: High
Projects
Development

Successfully merging a pull request may close this issue.

5 participants