1 Major Bug, 1 Minor
MuseScore 3.4.2, Revision 148e43f (should be most recent).
Windows 10 Home, Version 1903
These seem to be only on my end, but I have no idea how to fix them.
1 (Major) - Ever since an update or two after MuseScore 3 was released (i.e., a year or two, iirc), my program crashes ANY time I go to save or open a score. Making a new file works, and I can work on it, but in order to save the file, I have to quickly hit "Save" or "Save as" and click save with whatever it gives me, before it crashes. I assume this has to deal with the file program or something along those lines. I can't directly rename a file from MuseScore, that I named wrong, nor can I actually properly save what I am working with. Uninstall and fresh reinstall does not appear to work. I haven't properly made any music on here in a while due to it.
2 (Minor) - MuseScore 3 score files seem to be originally saved as ".mscz,", which is the wrong filename save. It should still be ".mscz", like MuseScore 2, in order to play.
I haven't seen anyone else with my issues, so I can't say for certain what it is.
Comments
For issue 1 we'd need sample scores. Likely there's a corruption in one of the parts
In reply to For issue 1 we'd need sample… by Jojo-Schmitz
I typically don't add parts until the end, hence why I am confused with that statement. But I'll let you look at it.
In reply to I typically don't add parts… by DarkPyroNinja
That was a brand new score from yesterday/the day before.
In reply to I typically don't add parts… by DarkPyroNinja
Doesn't crash for me.
What are the exact steps to get the crash?
In reply to Doesn't crash for me by Jojo-Schmitz
Touch anything that pulls up File Explorer, really. Opening a score, saving a score (new score that requires naming, as well as save as), etc. I've never seen anything like this either from checking out various bugs in this forum, so I'm as clueless as you.
In reply to Touch anything that pulls up… by DarkPyroNinja
Not for me.
Try reverting to factor settings
In reply to Not for me by Jojo-Schmitz
Reverted to factory settings, and went through the beginner dialog boxes. Came to the Create a New Score/Open one screen, and it still happens when I click to open a score.
In reply to Reverted to factory settings… by DarkPyroNinja
In MuseScore 3.4.2 on Windows 7 or 10? (Edit: yes, 3.4.2 and Windows 10 as per the initial post)
Try using the -w command line option to start MuseScore and check again. That crash may be related to the WebView part of the Start Center dialog (but File > Open should not be affected by that).
This has been reported to cause issues on some Windows 10 systems, but we've never been able to reprocuce, suspicion is some firewall or antivirus/malware protection tool causing this
In reply to Reverted to factory settings… by DarkPyroNinja
Could be a corrupt score in the folder you are in, MuseScore does try to build thumbnails. Try moving all the files out of there. Then if you can successfully save a new file to the now empty folder, and open it again, then maybe move the original files back in one at a time, or in batches, until you identify the culprit.
In reply to Could be a corrupt score in… by Marc Sabatella
Ah, yes, that one is a possibility too. Esp. on mscx files (on mscz I think it extracts them from the file, doesn't it?)
In reply to Ah, yes, that one is a… by Jojo-Schmitz
Generally, yes, as far as I know. But if the archive file itself is corrupted somehow, I could imagine in some cases MuseScore might try to regenerate a thumbnail.
In reply to Generally, yes, as far as I… by Marc Sabatella
I apologize for the very late reply. Decided to see if it magically fixed itself, and try your advice with the score folder to no avail. Moving all the scores out, and trying to add a new one reproduced the same issue. I'm unsure of what's causing this at all.
I haven't tried the "-w" yet. Would I place that in the shortcut's info for where to open the .exe, or the command prompt?
In reply to I apologize for the very… by DarkPyroNinja
Either should work the same. -w to disable web view is one possibility, -s to disable the synthesizer is another.
Indeed, for the first, probably the score or one of the parts is corrupt. Removing all parts then regenerating them should fix it. If not, please attach it so we can investigate further.
The backup file you are seeing (the one ending in a comma - and also starting with a period) is not new with MuseScore 3, it's always been there. Normally it's hidden, but you must have only recently turned on display of hidden files in Window if you are just now noticing them. Either turn that option off again, or just ignore those and instead be sure to open the real file. Starting with MuseScore 3.5 there is an option to store these files elsewhere.
In reply to Indeed, for the first,… by Marc Sabatella
3.5 also allows to open them