Deleting multi-voice rest causes flag to join

• Nov 28, 2010 - 20:06
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

1. Open attached score.
2. Click on a rest for the second voice and delete it.

Using MuseScore 0.9.6.3 and Mac OS 10.4.11.

Reported by myself .

Attachment Size
Flag Error.mscz 1.54 KB

Comments

• Mar 25, 2011 - 07:44

Although this is a bug here, I found something in bar 17 of 'Andante In F ' by Beethoven.

Is this correct, or a misprint (possibly an unedited marking by Beethoven - perhaps a standard no longer used)?

Reply

• Apr 13, 2011 - 02:05

I've looked at this score several times and don't see anything in or around bar 17, the one with the pp, right? What am I missing?

Reply

• Apr 13, 2011 - 03:23

According to the score bar numbering, that's 16, if you are referring to the one with the dynamic mark "p". What's unusual about that? The "p" is in the 1.0 dynamics pallet, and the R4156 as well, unless I'm still missing what you're referring to. I don't see anything unusual on the entire 3'rd line.

Reply

• Apr 13, 2011 - 03:46

I counted it manually (the score too small to see the number) and reached bar 17 (even counted them in the physical copy I have).

The p was just a reference to the bar I was talking about :).

The point was about the flag - should it have joined (looking at the semiquaver rest inbetween each of the three F notes)?

Reply

• Apr 13, 2011 - 17:44

I've seen that type of notation in older scores, so I didn't think anything of it. I don't know if MS can do that as I've not tried but I wonder if the Goldberg scores have that notation?

Reply

• Apr 13, 2011 - 18:37

The image is what happens in MuseScore 1.0 (should have put it up originally) if you follow the steps in the original post (Werner confirmed it to be a bug). I now don't know after seeing the Andante score.

Attachment Size
Flag Error.jpg 131.53 KB

Reply

• Apr 13, 2011 - 19:02

OK, I've looked at your original posting and I see what you are talking about with the notes beaming. In this case it is a bug as they should not beam after the rest is deleted. From your Beethoven score, they are beamed with rests, but all on one voice. The two cases are not the same.

First, why are we allowed to delete rests from the second (or other) voices? Doesn't that invite all kinds of problems? I thought if you don't want rests visible in any voice, make them invisible.

Can MS beam across voices?

Is the beaming that Beethoven used in your example implemented yet in the trunk/2.0 release?

Reply

• Apr 16, 2011 - 20:07
Status (old) active ⇒ fixed

The original issue seems to be fixed (as of 4200), but still want to ask Werner or someone about the beam in the Beethoven score.

Reply

• Apr 16, 2011 - 20:21

I'm still not sure of the issue you have with this bar in the Beethoven, so you may have to explain it better. The bar has 5 notes beamed, 2 of which are rests. Nothing unusual there, you can do that type of beaming from the Beam Properties palette, its just a little tricky with some. The sixth note (the rest), cannot be included in the beam. The end of the 5'th line and the 2'nd bar of the sixth line also have this type of beaming. The Goldberg project will have many of these too, I suspect.

If you're concerned about the rest touching the beam, so what? They are not touching so that they are included in the beam. I suspect that's just an engravers mistake by making the stems a little shorter than they should be, or keeping the rests down too far. Also, the quality of the copy is not good and there may be a _small_ amount of space between the beam and the bottom of the rest, its hard to tell.

Reply

• Apr 16, 2011 - 23:57

Yes, that's the bar I am looking at.

1. Open your attached sample score
2. Drag select the eighth notes and rests (not including the last rest) in the first bar
3. Open up the Beam Properties palette (2'nd last palette, should be on the left side of the screen)
4. Double-click the 2'nd beam option
5. Move the rests up so they don't intersect with the beam

You should have a 5-note beam, with 2 rests.

Incidentally, now try to undo the beaming... CRASH.

Reply