[Broken] Key Signature Left Margin for Initial Barlines with No Clef
Hi,
Since MuseScore 3 (great job by the way!) I've noticed a problem with key signatures appearing too close to initial barlines when clefs are removed and I can't seem to fix it via Style settings as I'd hoped to. I reported this issue yesterday [https://musescore.org/en/comment/894006] and Marc Sabatella has asked me to file this officially via the issue tracker (see the comments on link above). He also confirmed he has a fix ready.
(My first time reporting an issue -- apologies if I've made a mistake. I set the severity to 'Major' as Marc requested.)
Further details of the issue can be found on the post I made yesterday (link above). In short, to reproduce:
- create a new score (all defaults) in a key with a visible key signature (ie, not C / Am) and at least 1 system break
- uncheck 'Create clef for all systems' (Format -> Style -> Page)
- check 'Barline at start of single stave' (Format -> Style -> Barlines)
- note the very close distance between the initial barline of the 2nd system and its key signature
- vary the 'Key signature left margin' (Format -> Style -> Bar)
- note that this distance does not change (compared with the 1st system with a clef, where the distance does change).
Use case:
To streamline my lead sheets, I remove clefs (+ time signatures) on all but the initial system. I also think visible initial barlines looks better. In any key but C or Am, I have to use the Workaround (see below), which isn't ideal.
Regression:
I confirm I could not reproduce this issue on MuseScore 2.
Workaround:
You can manually set all key sigs adjacent to initial barlines to have a leading space equal to the Key signature left margin value:
- select every key sig adjacent to initial barlines
- via Inspector: Segment -> Leading space: X.XXsp
(or Element -> Offset: X: X.XXsp)
(where X.XX = the Key signature left margin value)
Hope that makes sense. Please let me know if I can be more helpful. Thanks to Marc for his quick reply and speedy provisional fix!
Kind regards,
Graham
Comments
https://github.com/musescore/MuseScore/pull/4661
BTW, I suspect you would find the workaround won't work, I don't think the leading space adjustment won't survive a save & reload :-( That is a known bug that will be harder to fix than this one. Thanks for the detailed report!
In reply to https://github.com/musescore… by Marc Sabatella
Ah, you're right -- thanks for the spot! Although, the alternative of changing the X Offset seems to work (even through a save & reload). Could you confirm?
Correct, good catch! This might adversely affect spacing, requiring a leading space adjustment to the first note as well, and in any case, it's not a very nice workaround. Luckily, the fix for this was very simple, I don't anticipate any issues seeing it merged and included in an update very soon.
In reply to Correct, good catch! This… by Marc Sabatella
Thanks for the heads' up -- and thank you for being so responsive!
All the best,
Graham
Fixed in branch master, commit e65fcde888
fix #283832: distance from barline to keysig
Fixed in branch master, commit 88110b5a15
_Merge pull request #4661 from MarcSabatella/barline-key
fix #283832: distance from barline to keysig_
Fixed in branch 3.0.x, commit 4b3c7b3e04
_Merge pull request #4661 from MarcSabatella/barline-key
fix #283832: distance from barline to keysig_
Automatically closed -- issue fixed for 2 weeks with no activity.