Clef can overlap preceding notes on same staff

• Jan 18, 2021 - 15:19
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

Have discovered a particular incidence where the Bass Clef is not placed ideally between beamed notes when the note preceeding the Bass Clef is an F or lower.
(Treble clef not affected in the same way. Tried to see if the Treble clef was affected but could not reproduce the issue when switching the clefs in the example below.)

Using:
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.487916429, revision: 1977cb3

F_clef_placement_Issue_Screenshot_2021-01-18_14-23-15.png

Issue discovered when updating my upload Consolation III by Liszt from MuseScore 2.2 to MuseScore 3.6
https://musescore.com/score/1128841

In Bar 48 MuseScore 2.3.2 places the Bass Clef as expected - see below
Bar_48_Consolations_MS_2.3.2.png

In Bar 48 MuseScore 3.6 does not place the bass clef correctly - see below
Bar_48_Consolations_MS_3.6.png

Attachment Size
F_clef_placement_issue.mscz 16.67 KB

Comments

• Jan 18, 2021 - 16:06
Title Bass clef placement issue between beamed notes ⇒ Clef can overlap preceding notes on same staff
Severity S5 - Suggestion ⇒ S3 - Major

This has been observed before but I'm not seeing an open issue for it, so I'm leaving this open.

I think what is happening is that unoikel in older releases, we now at least do try to allow overlap of the clef change with notes on other staves or voices, which is a good thing. But it shouldn't also extend to notes on the same staff, or at least same voice.

There are a number of other relates issues having to do with interaction between elements between voices/staves and how it affects spacing, and it's definitely something we hope to improve for MuseScore 4.

Reply