# Beam over 16th rests connected to eighth note appear as 8th note beam

• Aug 9, 2021 - 18:18
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
1. Create a 16th rest next to an 8th note.
2. Put a beam over the 16th rest using Beam properties in Palette

See beat 4 of the bar in the attached score.

Attachment Size
smf-test_beam_bug.mscz 2.67 KB

 Type Graphical (UI) ⇒ Functional

Looks like this:

 Title Beam over 16th rests appear as 8th note beam ⇒ Beam over 16th rests connected to eighth note appear as 8th note beam Severity S3 - Major ⇒ S4 - Minor Workaround No ⇒ Yes

FWIW, I don't see where Gould makes a clear statement about this, but it's not obvious to me it would be better with the extra beam. Certainly, it cannot connect to the eighth or the eighth would read as a sixteenth. So the extra beam would be "floating" - something I can't recall ever seeing in a published score. The only case I see where Gould shows this sort of case is a case that also involves "stemlets", and that little stem over the rest provides the "glue" to hold the beam in place.

So to me, this is probably not worth changing until such a time as we support stemlets directly.

Meanwhile, workaround - whether you want stemlets or not - is to add an invisible/silent note there.

 Workaround Yes ⇒ No

Thank you, guys!

The addition of a stemlet would be optimal. However, I maintain that an 8th note type beam under a 16th note makes for a confusing read. The expected behavior is an extra beam similar to the very last 16th note.

The workaround is possible but only when dealing with a small number of instances. Unfortunately, we have a very large amount.

 Workaround No ⇒ Yes

It is a workaround though

Can you show examples of this in published music? Would be good to understand how this is handled "for real".