Time Signature disappears

• Feb 2, 2019 - 15:46
Reported version
3.0
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore
  1. Open a score with a time signature.
  2. Select the time signature. And, with the Inspector alter the scale of the signature to anything other than the 1.00/1.00, i.e. 0.9/0.9.
  3. Set the new scale as the DEFAULT. (At this point, the signature is visible and reduced in size.)
  4. Save the score.
  5. Reopen the score and observe that the reduced size time signature has disappeared. Note: If the new scale is NOT set as the DEFAULT, the time signature will continue to be displayed after reopening the score.
  6. Once the signature has disappeared, there is no recovery. Unless, there is an additional time signature in the score with a scale altered independent of the Default. This signature can be selected with its scale set to 1.00/1.00 and set as default. At this point the disappearing signature will reappear.

Comments

• Sep 16, 2019 - 16:25

Here's a different way to change your time signatures: You can right click the time sig, then Select -> All Similar Elements, then change the size. It works for me.
Unfortunately, I haven't found a solution to the disappearing time signatures you get from changing the style default.

Reply

• Sep 20, 2019 - 06:32
Status active ⇒ PR created

Another way to make the time signature reappear without completely resetting the style is to do the following:

  1. Save the score as an "Uncompressed MuseScore 3 File (*.mscx)".
  2. Close the score.
  3. Open the MSCX file in a text editor, and delete the line that looks like
      <timesigScale w="0.9" h="0.9"/>

It was line 13 for me.
4. Save the file.
5. Reopen the MSCX file in MuseScore. You will see that the time signature has reappeared.

Anyway, see https://github.com/musescore/MuseScore/pull/5334 for a patch that resolves this issue. It was just a simple mistake in the code for reading style properties of type QSizeF.

Reply

Fix version
3.3.0