Bug report - drum notation, drums on the same space appear on same side of stem and won't adjust
mscoreNightly-r4674
Windows 7
Open MuseScore
Select Drum kit
Enter two drums that appear on the same note (e.g. both on E if it's a bass clef).
BUG - the notes both still appear on the same side of the stem.
When I click on note properties to adjust this nothing happens.
See .doc file with pictures to further explain. This scenario does come up a lot in drum notation (in my experience).
Thanks,
Stu
Comments
.doc not .docx ...
In reply to and the attachment... by Stu_
Something similar was reported recently, and I suggested a workaround: double click one note to enter edit mode, then move it to the desired side of the stem with the cursor.
In reply to Something similar was by Marc Sabatella
Hi Marc,
Just tried your suggestion. Works fine and no issues when I save and reload.
I don't know anything about programming, but if one of the people who programs MuseScore had time, I still feel this is one worth fixing. Simply because your suggestion is a lot more time consuming than with a normal stave (e.g. piano) where MuseScore does it for you automatically.
Anyway, not being a programmer I'll leave it in your hands.
Thanks again for the workaround,
Stu
In reply to thanks Marc, but.. by Stu_
Oh, of course, I agree it is definitely worth fixing, and you should porbably submit an issue to the tracker (see links at right). But I figured you might like a workaround for now.
In reply to Oh, of course, I agree it is by Marc Sabatella
Hi Marc,
Thanks for the slash plugin by the way. It is excellent.
If you have time, I don't really understand what issue tracker is.
I've created a new issue regarding the drum thing, but it says the same stuff as on the post. What's the difference? I.e. when is it appropriate to create a new issue?
Also what should it say in the 'Assigned' column (at the moment it says unassigned).
Thanks,
stu
In reply to thanks, Issue Tracker? by Stu_
As I see it, the issue tracker serves as a formal record of the problems reported. Developers can treat it as a kind of "to do" list, and they can cross items off as they are fixed. Forum postings are more likely to kind of get lost in the shuffle, I think. It isn't as practical to comb the forum looking for outstanding bug reports, because they will be mixed in with the threads on bugs that have already been fixed, or reports that turn that out not to be nugs at all but simply misunderstandings, as wel as the many "how do I..." questions.
I think of the value of the forum with respect to bugs is in discussing what the behavior *should* be and making sure a problem hasn't already been reported, before then submitting the issue to the tracker. Also in brainstorming workarounds and alerting other users. Maybe others see it differently, but I'd expect that all bugs deserve an issue in the tracker, but there may or may not be a need to post them in the forum first.
Oh, and thamks for the comments on the slash plugin! On my list of things to do is to get it to work with percussion staves. But so far, I've been using a different method there: I edited the drum set to include a slash head note directly. I just have to hide the stems manually.