Selection filter crashes

• Jan 2, 2015 - 15:43
Reported version
2.1
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

Hi, I've just downloaded the Beta 2 of the 2.0 software, and for my first session, happily used (and enjoyed) the selection filter. I've come back to do some more editing of my score, and I can't open the selection filter at all. If I try, either by pressing F6 or using the view menu it just crashes. I've tried with a different file, also restarting the program, and restarting my computer, but nothing has helped. I'm running Windows 7.

GIT commit: a925ae0

Comments

• Jan 2, 2015 - 16:05

Hmm. That should be the case. Perhaps the workspace files have become corrupt. Could you try running "MuseScore.exe -F" from the command line? This will revert everything to factory defaults.

Reply

• Jan 2, 2015 - 16:59

I would run it from the command line, but I'm afraid I'm not very familiar with this. I can get the command prompt up, but I'm not sure what to do after that. I've tried typing in 'start MuseScore.exe-f', but get a message that Windows can't find the file. I've managed to change the directory to where the executable is - I can see MuseScore.exe in the directory listing, but don't know what to do now...

Reply

• Jan 2, 2015 - 17:45

Brilliant! Thanks both - I've managed to do the thing, and it's working again. Now I just need to go and re-do all my personalisations...
Thanks again for such a prompt and useful response :-)
Jane

Reply

• Jan 2, 2015 - 17:52

Since apparently there exists a way to generate corrupt workspace info using Beta 2, I'll leave this open, but still "needs info" in that we'd need a way to reproduce the problem to be able to fix it. It *might* have been a random fluke - power sruge causing a disk error, etc - but more likely, there is a bug waiting to be understood.

Reply

• Jan 2, 2015 - 21:20

Having re-started the program, it's now very different to how it had been behaving - I now realise that as well as the issue with the selection filter, the program was very slow to start up - it's much better now, and the playback volume was very loud indeed. Again, this is back to normal now. I'll let you know if it happens again.

Reply