Melisma may take negative space

• Dec 31, 2014 - 19:48
Type
Functional
Severity
S4 - Minor
Status
closed
Project

When the note spacing is very tight already, a melisma on a slur allows the following syllable to overlap with the current one, so the syllable with the melisma actually uses less space than without it. The melisma starts from the end of the syllable and continues to the left instead of right. This way, it takes up negative space.

The two pictures are basically the same. For better visibility, I moved the second syllable down a little bit. This way, the melisma line with negative width is clearly visible.

Expected behavior:
If the syllable is already wider than the slur, there should be no melisma, and the slurred notes should be distributed over the width of the syllable.

Attachment Size
Melisma original.png 18.55 KB
Melisma second syllable moved.png 20.54 KB

Comments

I don't quite follow. First, what version of MuseScore, and what OS? Can you post the actual score so we can see exactly what you have done?

When I try to recreate your example in the current build of MuseScore 2.0, it looks nothing like your picture. I get this:

sing.png

If the first syllable is long enough to cover the second note, it looks like this:

sing2.png

Notice the syllable does not currently overlap the second note; that's an open feature request - see #5261: Lyrics for melismas should not respace notes if there is room before next syllable. I had a fix for that, but it suffers a worse problem: if the syllable is long enough to overlap the next note after that, it will overlap the lyric on that note just as in your picture.

I am guessing maybe you are using Beta 1, or some other build from roughly that time frame (summer of 2014)?

Attachment Size
sing2.png 8.17 KB
sing.png 7.56 KB
Status (old) needs info active

Yes, sir, it's beta 1. I'm waiting impatiently for a deb for beta 2 - or even better, 2.0 final ;o)

Good to know this will be fixed in the next version. Have a great 2015!

Status (old) active closed

OK, in that case, we can close this. Feel free to re-open (with sample score / steps to reproduce) if you still have trouble with a current build.