Unresponsive
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
If I have Musescore open at the same time as my DAW (Studio One v5.1), Musescore will become unresponsive within a few minutes and I have to use the Task Manager to close it. I haven't tried with other scores but I have attached the one I was using when I discovered this.
| Attachment | Size |
|---|---|
| Final_Fantasy_VII_-_One_Winged_Angel.mscz | 553.89 KB |
Comments
That score stems from MuseScore 2.2.1, and as such from stoneage. Latest 2.x is 2.3.2, but we're at 3.x since more than 2 years now, latest is 3.6.2.
So unless you have this problem also with 3.6.2, we'd have to close this issue
So far I have had the same issue on v3.6.2, v3.6.0 and one more (whichever version was current in January 2020, one of the v3.3.x or v3.4.x ones)
I don't see why the age of the file would be an issue - e.g. Guitar Pro 7 still opens files made in GP3, Studio One v5 opens files I made in v3 etc.
The age of the file might not be an issue, the age and version of your MuseScore though might.
I can't reproduce the issue, but then again I'm not using any DAW.
It might be due to the sound device to be setup for exclusive use rather than shared use?
My Musescore never just closes down. Have to restart the computer each time to cloes Mscore. Fedora 33 mscore 3.6