Musescore suddenly crashes when trying to add a time signature

• Nov 22, 2020 - 07:52

I'm currently trying to transcribe Stravinsky's Petrushka, which is full of time signature changes.
However, now when I try to add a new time signature change, Musescore immediately crashes. I've never had anything like this happen to me before.

Below is the transcription I have so far. Add a 3/4 time signature into first empty bar (bar 193) and it should crash.

Interestingly, if I add a 2/4 signature into bar 194 then add the 3/4 signature into bar 193, it doesn't crash...

Attachment Size
Petrushka (1st tableau).mscz 351.45 KB

Comments

For some reason, the Percussion part is corrupted (mainly Timpani - empty measures - but not only, from measure 165 and later) - image below
Remove this part, recreate it, and it's solved.
I recreated this part (check if the contents is correct, not sure for the triangle): 1 Petrushka (1st tableau).mscz

percussion.jpg

Some thoughts on workflow...

As a frequent transcriber, I find this workflow helpful:
1. Add all changes of key signature and time signature on a blank score, paginating as I go.
2. Then add all rehearsal figures and tempo marks to the blank score.

Particularly for a long work, this really helps with navigation when the pages are still empty of notes. And as a side-effect, it would probably avoid these corruption problems caused by changing or adding time signatures after notes have been entered and parts have been generated.

If you use local time signatures, it's even more important to lay down all the time signature changes before entering any notes.

In reply to by DanielR

As a frequent transcriber myself, I suggest that you not generate parts until you are done entering notes and text. You can then generate parts and change the format (add breaks) or make minor adjustments with no problem of causing corruptions since these aren't passed to the parts anyway.

The only time I pre-enter time changes in a symphonic piece is in sections with local time signatures. It allows for more freedom of the order you enter the time signatures. MuseScore sometimes complains about non-empty measures when you have notes in the flute and apply a local time signature to a lower staff. Otherwise I find it unnecessary and too tedious to try to layout a 600 measure 30 instrument symphonic piece in advance.

As for generating parts, as your piece grows, it will noticeably slowdown MuseScore rather quickly. This takes much longer if you don't have parts generated. I've transcribe about 1000 measures on 35 instruments with practically no slowdown by not generating parts. The only thing I find currently slow in a large piece is entering or flipping slurs.

Thanks for all of the help. The problem's fixed now, although I hope they fix the crashing. I'll definitely take the workflow suggestions; I didn't think the parts would cause such a hassle.

Do you still have an unanswered question? Please log in first to post your question.