Permanent courtesy time sig and key sig before system/page break when toggling in Continuous View and/or Parts

Does this happen on scores imported from 2.x or (also) on scores created in that 3.0 from scratch? I'd the former, upgrade to a later development build and reimport

Right-now, I can't reproduce by removing the page break (but I can with another scenario)
A simple image does not help. Please attach the score, it is necessary to check what is happening. Or/and thanks for being precise on the sequence of steps that lead to this behavior.

For example, I see right now another related behaviour, when toggle in Continuous View.

Tested with: OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4457, revision: e5d17fc

About the related behaviour (adapted title change for the moment), see:

As more or less predictable : same behaviour with system break.

1) SATB template
2) Add new time signature let's say mesure 6
3) Add a system break in the previous measure
4) Toggle in continuous view

Result: display both of time signature and courtesy

I would imagine one could get cases like this in page view for the same reasons as #279609: Inserting measure before measure previously at start of system displays spurious key signature. The extra time signature displayed in continuous view is bad but not as bad as an extra one in page view, since only the latter print. If we can reproduce this in page view, then I would mark this critical priority.

For the record, this issue has not been fixed with the mentioned commit above.
See:

Came up again in: #280556: Double Time Signature

Another one in: #280774: Time signatures that show on two lines in page view duplicate in continuous view

The attached in-progress score repros the duplicate signature in page view of the parts. See measure 81.

Also, if you try (in the main score) to change the time signature to 4/4 (for instance), 3.0 crashes.

The score has been completely developed in MS 3.0. I could not repro with a simpler score, so I don't know what triggered it as I've only recently generated parts.

Frequency should be updated based on number of reported issues, I think.

OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.0.0.20137, revision: c1a5e4c

Issue is also demonstrated at measure 97 of the score (in parts only).

Should I create a separate issue since this is page view in parts vs. continuous view? FTR, it also repros in continuous view in this score, so I think it's the same issue, only higher severity since it affects engraving.

Well, I'm bumping the priority of this so it gets a better look, then maybe someone can see if the issues are the same or not.

Well, I don't think the crash in the file "La folia" is directly related with this issue of displaying twice time/key signatures. I can reproduce without it. Seems rather a problem with 4/4, C and Cut time if there is another or other time signatures later in a score (with parts), which is the case in your file. Report soon (EDIT: done: #281504: Swap 4/4, C or Cut time if there is another time signature further in the score crashes the program. Also happens when changing from 4/4 to 2/4)

Thanks, cadiz1

Seems like Frequency should be updated here, as well as the title to include the Parts case. I've done the latter but don't have rights to change the former.

I've been asked to post this sample score here from another thread. Among the issues it exhibits is the stuck courtesy time signature, though I do not use Continuous View. This is happening for me when only using Page View.

Trying to open that score gets MuseScore 3.0.1 into a loop/freeze. Is that just me? It opens in a selfbuild from lastest master

"Among the issues it exhibits is the stuck courtesy time signature, though I do not use Continuous View."
The question is now: can you reproduce this issue only in Page View - ie never toggle in Continuous View - from scratch (a new score)?
And if so, please provide steps.

So, after checking, this issue, in this scenario (https://musescore.org/en/node/279925#comment-880026), appears on August, 16

• This nightly (last one of August 15) works: cb982cd

• Not this one, and so I guess (since the two previous commits seem not related) it's a side effect of this commit/nightly: 411b463

Thank you. I understand now.

An initial investigation shows the extra signature is indeed a courtesy signature and is not in fact being laid out at all while in continuous view, it's just being displayed based on the layout from page view. So in fact, it goes away if you save/reload while in continuous view, but re-appears if you switch to page view and back again.

https://github.com/musescore/MuseScore/pull/4656

Fixes the basic issue with the double sigs appearing when switching from page to continuous view, if a courtesy sig existed while in page view. There may be other cases of double sigs not addressed by this PR. For instance, we know scores imported from 2.x using the first beta get permanent extra elements that simply need to be deleted; this is unrelated. But anyhow, I believe my fix addresses the most common reports here.

Fixed in branch master, commit 65ef5321fb

fix #279925: double sigs on switch from page to continuous view

Fixed in branch master, commit 9077881f98

_Merge pull request #4656 from MarcSabatella/279925-double-sigs

fix #279925: double sigs on switch from page to continuous view_

Fixed in branch 3.0.x, commit a60a23f27c

_Merge pull request #4656 from MarcSabatella/279925-double-sigs

fix #279925: double sigs on switch from page to continuous view_

Thank you all for your help. The problem has been solved.

Automatically closed -- issue fixed for 2 weeks with no activity.