Although I haven't managed to crash the application, I did manage a good reproducible 1-2 minute freeze which is maybe not desirable anyway. Later I've come up with this: it may or may not be related to what you've reported so far. I didn't have the patience then so I killed the process. I saw a bottom-rigtht corner notification about downloading (progress 0%) and I think musescore start center couldn't get the score preview so it was unresponsive. The reason was the score file had been marked as changed but probably due to my faulty wifi at that time OneDrive somehow couldn't downloaded it. At home I opened Musescore - it started but was unresponsive. Then I worked on it on a different machine and saved it, so the original OneDrive file was rewritten. I worked on a score on my home computer and saved it to my OneDrive directory. I've also experienced something similar with Musescore 2.3.2.
0 kommentar(er)
