System Header with time signature distance does not work for some time signatures (imported 2.x file)

• Jul 11, 2019 - 10:37
Reported version
3.2
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
MuseScore

Win 7 /10. 3.2.3 (official)

(Note: #292003: Extra treble clefs have appeared in imported 2.3.2 file has already been reported).

  1. Open the attached file and reset. Then save and reload (to fix a layout problem—see #292028: System header distance too to small if extra clef present in file but hidden due to staff property).
  2. Now open Format > Style > Measure and decrease the System header distance.
    Expected result: The clef to note distance should decrease at clef system headers but there should be no effect at time signature system headers.
    Actual result: This is the case for measure 1, but not for subsequent time signatures: e.g. measure 33.

Similarly, "System Header with time signature distance" works for measure 1 but not for measure 33 and so on. Workaround is to delete the offending time signatures and reapply.

Attachment Size
aguado_lessons_ms2.mscz 44.74 KB

Comments

• Jul 11, 2019 - 18:24
Status active ⇒ by design

When I follow your instructions, reducing "system header distance" to 0.5 after first saving & reloading, I find the distance decreases exactly as expected: it decreases everywhere but the systems where the last header element is a time signature. The extra clef in measure 33 is why it doesn't take effect here. The idea isn't that the mere presence of the time signature isn't what determines which setting kicks in, it's whether the time signature is last in the header (as it normally would be if present).

Reply

• Jul 12, 2019 - 10:35
Status by design ⇒ active

I should have added the instruction, "delete any extraneous clefs first." Once this is done, measure 33 (and others) responds to "System header distance (which it shouldn't) and fails to respond to "System header with time signature distance (which it should).

It appears that some of the time signatures do respond correctly, others don't. Not sure why. Deleting and reapplying the time sig is the workaround.

Reply

• Jul 12, 2019 - 17:11
Severity S3 - Major ⇒ S4 - Minor
Priority ⇒ P2 - Medium

The score in question seems to have some corruption in the systems headers, which is why replacing the time signature fixes it.

If you can reproduce this problem in a non-corrupt score, feel free to followup with that score and steps.

Reply