A note spacing issue involving an accidental
Nightly acf6580 on Win 7 / 2.0.2 on Win 10.
See attached score:
In bar 7 there is an unexpectedly wide space between the second and third 1/8th notes in voice 1: this is especially noticeable if you beam all four 1/8th notes together. However, if you change D# to D in voice 2, the spacing becomes regular. It appears that the program is allowing too much space for the sharp in voice 2.
(Finale 2009, with exactly the same layout of measures, spaces these notes evenly, even with the sharp in place.)
| Attachment | Size |
|---|---|
| note_spacing_issue.mscz | 18.89 KB |
Comments
This is limitation of the current layout algorithms, which prevent the sharp from overlapping the same vertical space as the earlier note. Work is being done to improve this, but it's probably not coming until MuseScore 3.
Watch the forums for a post about this in the coming days.
In reply to This is limitation of the by Isaac Weiss
Thanks. I can work around it for now by selecting the D# and using Inspector > Segment > Leading space to adjust the position.
Are you sure the Finale example you have includes such tight spacing? MuseScore gets the spacing even *if* the measure was already spaced loosely enough that the sharp sign doesn't get in the way, and I am wondering if this isn't what you are seeing in the Finale example. I suspect it is, because in Daniel Spreabury's excvellent "Making Notes" blog, he shows a very similar case and how different notation programs handle it, and Finale clearly allocates extra space in his example very similar to what we do. See http://blog.steinberg.net/2014/12/development-diary-part-nine/, scroll down to the dection on "Rhythmic spacing". Only LilyPond ("Product C") tucks the accidental for the lower note under the upper note. It's a slightly different case in that there are not multiple voices, but actually, the case shown in Spreadbury's example is probably more common, so I'd be kind of surprised if Finale went to the trouble of handling the less common case but not this one.
If I'm wrong and Finale shows equal spacing even if this measure is spaced more tightly, then I wonder what happens it you drop that top G down an octave, so that it *does* collide with the sharp sign? Does it create unequal spacing in that case, or does it add unnecessary space throughout the measure to preserve equal spacing?