MuseScore keeps crashing when I work on individual parts
Yeah, I am currently helping someone and creating conductor scores. The issue is, she gave me separate sheet music to combine into one, so I believed that the best way to go would be to have the part tabs visible. The issue is, MuseScore will always crash and then the file will become corrupted. I am aware that parts tend to slow MuseScore down, however, I am wondering if there is something else that could exist that causes a crash. I even took one SoundFont of the Synthesizer that was massive in order to try and speed MuseScore up. What is the possible thing to do if it's a software issue?
Comments
Unfortunately I can't help you with this problem. However I have done the same job (assembling a score from the parts) a number of time and done it the other way around.
I set up the score with all the instruments (as you have to do too), then start with one part (a principal part like the first violin is a good idea in classical works) and transcribe it directly into the appropriate staff all the way through a movement (keep the scores one movement per file, otherwise they become unmanageable). Then all the other parts one after the other. As the score starts coming together you can see how the parts match and spot errors (when you e.g. erroneously jumped a bar or a line) quickly.
When all the parts are in the score I go back and carefully proofread one part at a time. If you want to make editorial changes--e.g. adding dynamics or articulation markings--now is the time for it. After that I make a copy of the score so I have two identical files. The first is formatted (correcting stretch as needed; fix odd slurs and ties, especially the jumps from one page to the other, move dynamic markings out of the way of notes where necessary etc.). The second copy of the score is now being "contaminated" by cues: I go over one part at a time and find cues for long rests and enter them right in the score (it is a good idea to copy/paste a clue to all instruments that need it right after first entering it).
Then and only then do I create the parts, extract them to .mscz files and combine the files for the various movements using the album function of Musescore. The last step then is to format the parts (page turns, readability).
This sort of work flow seems satisfactory to me.
Crashes are due to bugs, of course - there's nothing you can do that *should* cause a crash. There are indeed some known bugs that can cause crashes. In order to say if your score is hitting one of these known bugs or it is a new bug, we'd need you to attach it. Then we can identify the problem and tell you how to work around the problem, and hopefully fix the bug if it hasn't already been fixed for the next release.