2.0.3. Unreliable start; Saving trouble
Just started using 2.0.3. I have been using the previous version since it became available, and have enjoyed many bug-free hours of use.
On starting up 2.0.3, with the score that I had been working on, a problem immediately started. Every change I made to the score (anywhere on the score), from moving a note up or down, to adding something or cutting something resulted in the last bar on page two jumping to page three, then with the next change it jumped back. This meant that every input meant everything moved either backwards or forwards! So I couldn't build a chord easily as the bar would move around under the cursor, between my clicks.
I fixed this by putting in a page break. But it's still a problem which I had never encountered before, and didn't happen before the update on this very score.
I then carried on with my score, making several changes and additions. I click save habitually every few minutes, and did so several times yesterday.
But I have gone back to the score today and nothing has been saved - I am in the same position with the score that I was when I opened it yesterday. My evening's work is no more! Not a tragedy as it wasn't too much.
I'm now hesitant to do any more work until I can save my score reliably. Is anyone else experiencing this? Please help!
Comments
Thank you for sharing your experience. We will need a little more information in order to be able to help you out.
Could you tell us which platform you are working on? Windows, Mac OS X, ... Try to be as specific as possible.
Could you share the score file with us? So basically attach the score file to a comment on this thread?
In reply to Thank you for sharing your by Thomas
Thanks for offering your help. The strange thing is that the one thing I changed at the time of writing my post yesterday has saved! I put a page break in at the offending point of the score and it stayed there overnight! Nonetheless, I have taken the page break back out so you can see the strange 'bar switching pages' that happens as I described.
I'm using the latest version of Windows 10.
I think I've attached the score to this reply (never done this before, I ticked "list"). I haven't been able to change it - as I've read others do when posting a score for help - as that changes the position of the bars, so you're seeing my (very) amateur effort in its nearly full glory! But it's no masterpiece, so no problem!
In reply to Thanks for offering your by The Theatre
There's something strange with the dotted quarter rest in measure 42. If you change that to auto beaming (via the beams palette) the stray beam next to it disappears and measures are getting reordered.
In some other cases (measure 11, 16, 20), you could have used 'cross staff notes (badly named in the handbook, https://musescore.org/en/handbook/cross-staff-beaming), avoids having to hide rests.
In reply to There's something strange by Jojo-Schmitz
Thanks for the bit about cross staff notes, really useful.
You'll have to forgive my lack of knowledge of the various terms, so I apologize if I'm getting muddled, but what you said about the auto beaming reminded me of another problem connected (I think) to what you say:
You can see that I haven't joined the quavers together going from measures 6-7, 10-11 etc. as I would like to, and have done over previous bars. I assume this is a 'beaming' problem. If I try to join them the bar appears either way above the place it should or doesn't appear at all. Hopefully that will happen for you too if you try.
I think that this is affecting the original problem I had, and the strange problem you picked up on in your first paragraph. The solution you mentioned does work for me initially, until I then try to join the beams together, or move a note - anything in fact - and the stray beam reappears and measure 35 flips again from page 2 to 3.
I'm puzzled.
Also, I now also have a stray extra line (mirroring the ones I've used in measures 11, 16 and 20) appearing in the middle of page 2!
In reply to Thanks for the bit about by The Theatre
The stray line is the result of having manually adjusted a line in a way that made sense originally but then when the measures changed, that same manual adjustment doesn't make sense any more. This often happens if people drag a symbol so far from its original position that it ends up on a different page if the layout changes. However, it's recently been demonstrated than in these rare cases where the score layout changes of its own accord, attempting to move a line even a small amount can produce this effect is the layout changes at the same time, so my guess, these problems are related. EIther way, the solution is to reset the positions. Eg, right click one line, Select / All Simialr Elements, Ctrl+R. This will return things to their default positions - including the stray line, which I think you'll discover really belings to measure 49. You can then undo the reset operation (so you can keep the adjustments you made elsewhere), and now select measure 49 and do the reset again, to force the stray line back
In reply to Thanks for the bit about by The Theatre
Also, beams across barlines work, *unless* the measures are on different systems. In that case the beam appears in the wrong place. This is a known bug that has proven difficult to fix.
In reply to Also, beams across barlines by Marc Sabatella
Thanks for all your help. I think I've got a handle on all this now. I'll battle on to complete the piece and hope that save continues to work!
In reply to Thanks for offering your by The Theatre
In general, the prpblem you describe is a very rare one that doesn't happen often but when it does, usually strikes when there are clef, key, or time signature changes right at a place where a line potentially breaks and we have trouble figuring out how much room they will need. That's clearly what is going on your case - it's the key change at measure 36 where we are having trouble deciding about. In 2.0.2, we never even try to fit measure 35 on the same system, which is why the issue doesn't occur in this particular case. 2.0.3 is ever so slightly more space-efficient for this score, so we can just barely fit measure 35, or not - it's borderline and we can't quite decide. These borderline cases can happen with both 2.0.2 and 2.0.3, but they should be *less* common with 2.0.3, because we fixed a number of cases. I think you just got unlucky with this particular score.
The workaround when this does happen - both for 2.0.2 and for 2.0.3 - is to force the smaller number of measures onto the system using breaks, as noted.
Anyhow, thanks for posting the score, so we can try to investigate why this particular case is still failing.
In reply to In general, the prpblem you by Marc Sabatella
Thanks for that. I was sending a reply to the previous poster as you replied which brings up a problem that may be linked.
In reply to Thanks for that. I was by The Theatre
Here's the piece with the stray line on page 2 (measure 29). I can't click on it to cut or move it.