Prevent note and accidental collisions?
I have two voices (1 and 2) on a staff. The top has F-Enat-Eb-F, bottom is Eb-Dnat-Db-Eb. They are colliding a lot:
How do I get them to not collide?
| Attachment | Size |
|---|---|
| musescore_note_collisions.png | 6.38 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
I've tried "stretching" the measure, and it eventually sort of works, but it's still pretty bad. It puts a lot of space where not needed, and very little space where needed:
In reply to I've tried "stretching" the by dfrankow
In a pinch, I believe double clicking on each element allows movement with the <- -> keys, but this obviously is a temporary measure.
In reply to In a pinch, I believe double by xavierjazz
I'd use a combination of stretch (just a little) plus addition of leading or trailing space via the Note Properties menu, plus manual positioning via Edit Mode (double click and arrows). Ideally, this wouldn't be necessary quite so often, but I kmow I had to do quite a bit of this sort of thing with Finale, too.
When I was trying to reproduce this, I encountered another problem: #16478: Forthcoming note sounds incorrect after deleting accidental
Using MuseScore 1.2, could dfrankow (or someone) notate what is in the image and then upload the MuseScore file? I seem to have difficulty (perhaps it's just me).
In reply to When I was trying to by chen lung
To be fair, I created it with MuseScore 1.1.
However, when I open it up in MuseScore 1.2, it looks the same.
In reply to When I was trying to by chen lung
And thanks for trying to reproduce it.
Thanks for posting.
Looking at the unstable nightly builds, it seems the collision will be corrected for 2.0 (coming later this year) - see PDF :). There's another collision in the final line, though.
Just while we're talking about the score, I've also attached output from (renowned) LilyPond (using xml2ly plug-in via MuseScore 1.2) - beam direction differs and is possibly incorrect in MuseScore, but it's currently being worked on, and again, will be corrected for 2.0.
Using MuseScore 2.0 Nightly Build (5640) - Mac 10.7.4.