Bug report regarding parts
Hello,
I would like to report some bugs. I added files with minimal reproduction and annotations.
| Attachment | Size |
|---|---|
| Bug 1.mscz | 20.97 KB |
| Bug 2.mscz | 30.69 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
Another one
In reply to Another one by Mansent
Linked staves don't make any sense for Flutes.
But delete the slur and reenter it, and all is fine.
Question is how you got the linked staves into that inconsistent state.
Edit: I see, playing with voices, better mention that rather than letting us guess
In reply to Linked staves don't make any… by Jojo-Schmitz
It made sense to me to create a linked stave because I have a full orchestral score, where flute 1 and 2 share the same stave. In the flute part, I wanted seperate staves for each flute so I created one linked stave.
This is how I got it in inconsistant state:
1. Create new empty score
2. Enter a few notes in voice 1 and 2
3. Select first note in voice 1
4. ctrl click last note in voice 1
5. press S to slur
6. create a part of that instrument
7. create a linked stave
8. configure the first stave to only show 1st voice, second stave to only show 2nd voice
Now if I select a bar in the lower stave and press S to slur, the additional slurs appear.
In reply to It made sense to me to… by Mansent
That's just not what linked staves are designed for.
May still be a bug though
Check if these have been reported on GitHub, and if not, report them there.
Seems at least the rit. issue needs to get reported there
Same for the voices issue, apparently
In reply to Check if these have been… by Jojo-Schmitz
I tryed to click on "New Issue" on https://musescore.org/project/issues, but for some reason the link redirects me to my profile instead of letting me create a new issue. That's why I posted them here.
Am I doing this wrong?
In reply to I tryed to make click on … by Mansent
Apparently. Go to https://github.com/musescore/MuseScore/issues/new/choose
One issue per bug, do include a good description (and not only in the sample score) and zip the sample score in order to be able to attach it
In reply to I tryed to make click on … by Mansent
that issue tracker (https://musescore.org/project/issues) has been discontinued. Use the one mentioned above instead.
In reply to That link does work for me,… by Jojo-Schmitz
Ah thank you, then I report them there
Here is another one.
By the way, i am using
OS: Linux Mint 21.1, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: e4d1ddf
In reply to Here is another one. By the… by Mansent
See Bug 3, same questions
Ah, here you played with the voices again, missing from the description
Re bug 1. This may be only a partial bug. Whatever that is. The rit. is on the third beat of the measure in the soprano part. It could be that when MuseScore tries to render the tenor part, all it sees is a whole rest. Maybe it has no idea where beat three is. When I break the whole into two half rests, the the rit is placed properly. Not quite right, but not totally wrong, either.
Thanks for
In reply to Thanks for https://github… by Jojo-Schmitz
I've a comment to issue https://github.com/musescore/MuseScore/issues/19182 and the example included. While it looks nice just removing the rest, it's not clear for the conductor who should play, i.e. Fl .1, Fl. 2 or maybe both. As it is shown, I would interpret it as unisono or possibly Fl. 2 because the stems are pointing down.
Hence, to make it clear, the score should include a clarification, e.g. "a2" or "a due", Fl. 1 or Fl. 2.
This is not a comment on the issue as such because that should be corrected but only on the clarity of the score if two voices are "merged".