Beam thickness not scaling with staff size
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
When I input quavers, semiquavers and etc. and I want them to be connected, the neccecary second, third etc. beams are missing (one beam for semiquavers instead of two). This is not the issue when I input only one single quaver. This problem occurs only when "Small Stave" option is selected.
EDIT: Made stem displacement into a separate issue, as recommended
| Attachment | Size |
|---|---|
| SmallTempTest.mscz | 20.77 KB |
Fix version
3.1.0
Comments
somewhat related to #282026: Stem Displacement, as that is also about small staves
I think what is happening is the beam thickness is not scaling correctly, and this is also causing the beam distance to not scale correctly since it is expressed as a percentage of the thickness. It seems you are attempting to work around the bug by decreasing the beam thickness, but you'll need to change the distance too to make the workaround effective and still be able to see the multiple beams
, and you have attempted to work around that bug by setting the beam to be extremely thin, which is why they are appearing to merge into one when there are multiple beams.
In fact, you should not be using small staves either - it appears your goal was to fit a lot of instruments on one page, but the correct way to do that is to go to Format / Page Settings and just decrease the staff space size. That way everything does scale correctly.
But again, it is a bug that beams don't scale correctly when you set the staff to small.
In reply to I think what is happening is… by Marc Sabatella
Thanks for the update! I really appreciate your hard work!
I've been using MuseScore for 3,5 years and didn't know how to fit a lot of instruments in the score properly. Thank you for your help again!
This is really ugly and unreadable. Small staves are very common in sonatas.
Yes, and we currently have a number of other issues with small staves. See for instance #284440: Positions above/below staff not scaling with staff size and the other issues linked there.
Relates to #285228: [EPIC] Small staves issues
This turns out to be a very simple matter, we are using StyleP rather than StyleS in getting the style value for beam thickness, and the former does not scale for staff. PR forthcoming, will check to see how many other of the related issues are so simple.
https://github.com/musescore/MuseScore/pull/4827
Fixed in branch master, commit d788c38b92
fix #282021: scale beam thickness
Automatically closed -- issue fixed for 2 weeks with no activity.