Unexpected plus signs and rests
Hi everyone,
I run MS 3.3.4.9066.
A minute ago I all of a sudden noticed (or at least I was made aware of it) that in some scores, at the end of some bars, a plus sign appeared mear the end of the bar, with an extra quaver rest being added to the end of the bar.
They do look quite faint, like hidden elements.
It was in scores I hadn't made, but the person who had made them alerted me to that bug (Or is it?)
Has anyone come across this yet, is it a bug or does anyone know a solution?
Thank you in advance.
Comments
See: https://musescore.org/en/handbook/3/note-input-modes#timewise
In reply to See: https://musescore.org… by Shoichi
Thank you for this quick reply, Schoichi,
now the question that remains is: how can you get rid of these excess rests, the conventional methods (selecting them and use the delete button or right-clicking and selecting delete) do not seem to work.
Thanks.
In reply to Thank you for this quick… by mrfdes
right-click into the measure(s), measure properties, change actual duration to match nominal duration.
This will lose excess notes too, so better copy them all first and paste back after.
If it is just excess rests you want to loose anyway, no need to bother
In reply to Thank you for this quick… by mrfdes
Sorry, ignore this.
I just found to use CTrL + Del.
Thanks again.
In reply to Sorry, ignore this. I just… by mrfdes
Hmm, OK, that's the easy way out ;-)
In reply to Hmm, OK, that's the easy way… by Jojo-Schmitz
OK, what's the other suggestion then?
Thank you.
In reply to OK, what's the other… by mrfdes
see above
In reply to see above by Jojo-Schmitz
Right.
Thanks everyone.
Much obliged.
In reply to Hmm, OK, that's the easy way… by Jojo-Schmitz
I found out it isn't.
When I have done it 2 or 3 times, Musescore just crashes every single time.
In reply to I found out it isn't. When I… by mrfdes
Crashing is very bad.
![Muse_oh.png]( "Muse_oh.png")
Please attach a score where this happens whenever you change measure durations. Explain the steps required.
In reply to Crashing is very bad. … by Jm6stringer
OK,
here is one score where it happened.
The steps are quite simple: delete the excess rests with CTRL+Del 2 or 3 times and BINGO.
Regards.
In reply to OK, here is one score where… by mrfdes
I see 4 instances of the extra quaver rest at the end of a bar: measures 14, 21, 22, and 25.
I can Ctrl+Del them one at a time without crashing.
I can also change measure durations (as per Jojo's reply above) without crashing.
What version of MuseScore? What OS (operating system)? What is your exact sequence of mouse selection and keystrokes to reproduce the crash?
(Windows10, MuseScore 3.34)
In reply to I see 4 instances of the… by Jm6stringer
MS 3.3.4.9066 Windows 10 v 1909 64-bit.
I place the cursor on the rest, then hold CTRL and press Del.
There is no problem with the method of right-clicking the bar and using the "measure properties".
Regards.
In reply to MS 3.3.4.9066 Windows 10 v… by mrfdes
My setup is:
MS 3.3.4.9066, Windows10 Pro version 1903 64-bit.
Windows Update showed I was up to date but, when I did a new check, I found an 'optional update' to version 1909.
Anyhow, before I update, I will post a new entry below detailing some score corruption I've found. (I still can't get MuseScore to crash.)
Check this out...
I open mrfdes' file (posted above): "highland-cathedral-bewerkt-naar-5 (2).mscz".
I see 4 instances of an extra quaver rest at the end of a bar: measures 14, 21, 22, and 25.
I select the extra quaver rest in measures 14 then Ctrl Del it out of existence.
Repeat for measure 21. Repeat for measure 25. Measure 22 is left untouched.
Save, then close the score, then re-open. No loading errors.
N.B. There is an invisible quaver rest at the end of measure 24, but it's ok - should be made visible though.
Here's the almost fixed score:
highland-cathedral-bewerkt-almost-fixed.mscz
Now let's fix measure 22:
Select the extra quaver and press Ctrl+Del while watching measure 23. You will see movement.
Save, close the score, then re-open.
A loading error occurs with details:
Measure 23, staff 1 incomplete. Expected: 4/4; Found: 26/16
Measure 23, staff 2 incomplete. Expected: 4/4; Found: 6/4
Measure 23, staff 3 incomplete. Expected: 4/4; Found: 6/4
Measure 23, staff 5 incomplete. Expected: 4/4; Found: 6/4
Ignore and open the broken score and you'll see measure 23 with extra beats added!
Here's the broken score:
highland-cathedral-bewerkt-broken.mscz
However, if one uses measure properties in the almost fixed version to repair measure 22 (not Ctrl+Del), the score maintains its integrity and everything is ok:
highland-cathedral-bewerkt fixed.mscz