Missing space between key signature and first note if time signature is hidden
Reported version
3.3
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
1) Create simple score (one instrument is sufficient) and "large" key signature (e.g. G-flat major).
2) Add single note. (Spacing is ok.)
3) Hide time signature (e.g. using inspector). => There is no space anymore between key signature and first note.
Attachment | Size |
---|---|
TestFirstNotePlacement.mscz | 5.46 KB |
MissingSpace.png | 16.12 KB |
Fix version
3.6.0
Comments
In reply to (No subject) by Jojo-Schmitz
Workaround is to disable display of the time signature via the stave properties dialogue.
In reply to Workaround it to disable… by SteveBlower
There is a circumstance where this workaround doesn't work. If the composer shows a dual time signature at the start of the piece, but then mixes the time signatures between parts and indeed between voices of the same stave - without any explicit changes of time signature printed after the first dual indication.
See attached PDF of such a score, of which this is the opening system:
Obviously this score is a candidate for turning off the display of time signatures. But this makes it impossible to show an opening time signature (as in the original edition) without resorting to an image:
I find it quite hard to produce a screenshot which matches into the stave lines properly. It would be much easier if I could set the opening time signature as 12/8 from the Time Signatures palette, and then add the C (common time) symbol from the Master palette.
In reply to There is a circumstance… by DanielR
+1
In reply to There is a circumstance… by DanielR
Well, it can be done with a different (rather clumsy) workaround.
Adjust the leading space of the first elements in the bars following the now invisible time signatures to - compensate for MuseScore's miscalculations.
Dual time signature using images (2).mscz
I agree, it would be much better if MuseScore could sort this out itself. And I guess that if the issue gets fixed, you would then have to revisit all the scores where you used the workaround to reset the leading spaces.
The new workaround is fine, because these cases don't occur often.
But the principle is that MuseScore should not be using an invisible time signature element to calculate note offsets: in this situation (first bar of a system) it must check the key signature width to calculate the note offset.
See https://github.com/musescore/MuseScore/pull/6811
Fixed in branch 3.x, commit 27978791d6
_Fix #299196 - Missing space between key signature and first note if time signature is hidden
When calculating the minimum measure width in Measure::computeMinWidth(), skip segments when all elements in that are invisible too._
Fixed in branch 3.x, commit fc5093290b
_Merge pull request #6811 from njvdberg/issue-299196-invisible-timesig-spacing
Fix #299196 Fix #312393 - Missing space between key signature and first note if time signature is hidden_
Fixed in branch 3.6alpha, commit 27978791d6
_Fix #299196 - Missing space between key signature and first note if time signature is hidden
When calculating the minimum measure width in Measure::computeMinWidth(), skip segments when all elements in that are invisible too._
Fixed in branch 3.6alpha, commit fc5093290b
_Merge pull request #6811 from njvdberg/issue-299196-invisible-timesig-spacing
Fix #299196 Fix #312393 - Missing space between key signature and first note if time signature is hidden_
Automatically closed -- issue fixed for 2 weeks with no activity.