Double time signature after deleting system break
There is a part in my music where I no longer want a system break for the time being. When I delete it, the time signature reads double.
I've tried deleting the time signature and adding it in again, but it shows the same thing.
The solution I came up with is to make one of them invisible, however it leaves this awkward gap that is undesirable.
| Attachment | Size |
|---|---|
| Screenshot (28).png | 269.8 KB |
Comments
See #279925: Permanent courtesy time sig and key sig before system/page break when toggling in Continuous View and/or Parts
I have this same problem did you file a bug report and did they give you a fix? I have been doing the same thing with this issue. Making one invisible.
In reply to I have this same problem did… by rio3333
Can you come up with steps to reproduce this problem? We'd love to fix it but so far no one has been able to tell us how it happened.
In reply to Can you come up with steps… by Marc Sabatella
None of the files that was showing this issue are not showing it now. When I reopen them after updating the last time they do not show a double time signature. If it happens again I will write down the steps that I used that caused the event to happen.
In reply to Can you come up with steps… by Marc Sabatella
Just happened again. I am sending you the file that it happened with.
1 added a line break at a time change in the file.
2 removed the line break, time signature show twice
3 saved file and closed
4 reopened file, double time signature still there.
5 reapplied line break time signature returned to end of line, beginning of next line.
this file was originally created using a version of Musescore 2. Have save numerous time with 3.0 and now opened and created issue with the newest 3.0.5.5992
Hope this helps.
In reply to Just happened again. I am… by rio3333
The problem is to reproduce from scratch (ie, from a new created file). Can you?
In reply to The problem is to reproduce… by cadiz1
tried making new score then a new part. Unable to duplicate the problem with a 3.0.5 new file.
Apparently an issue with updating previous version files. Thank you for the assistance you provided. I will just continue to use the work around on old files of making 2nd time invisible instead of remaking the files from scratch. This would be the easier option. Thanks
In reply to tried making new score then… by rio3333
"Unable to duplicate the problem with a 3.0.5 new file."
Right now, that's exactly the question. If we look at it in an optimistic way, perhaps it means that this issue is really fixed. But it may be better to remain vigilant for some time.
In reply to Can you come up with steps… by Marc Sabatella
This problem happens all the time. Perfectly reproducible. (As someone else also reported the steps).
First, have a score with system breaks. Change a time signature after a system break. Then, the courtesy time signature appears at the end of the staves of the previous page. Delete the system break, now the measure where the time signature changes to somewhere in the middle stave. The problem is that it appears as two time signature together. There should be only one time signature. Trying to delete either of them does not work. Delete the time signature and try to reapply a time signature. This brings back two signatures again. Trying to switch off curtesy signature option does not seem to work. If the measure is in the middle of the stave (not at the last measure of the page), the double time signature should automatically reduce to one.
In reply to This problem happens all the… by yoichi123
Yes, there have been other reports, but as far as we know, all the cases where there were reproducible steps have already been fixed as of 3.1 beta (and indeed most were fixed before 3.0.5).
If you are finding you can still reproduce with your particular score using 3.1 beta, please attach it and given us precise steps (eg, tell us which specific measure to add time signature too, which line break to delete, etc).
In reply to Yes, there have been other… by Marc Sabatella
Thanks for the reply. I am still using 3.0.5 Mac version. I will test it when I can get 3.1b. Cheers!