MuseScore Studio 4.4.2 crashes when Play button is clicked in Windows for scores with VST instruments
My apology for this addition, but I forgot to mention below that these crashes might be caused just by the QML error(s) and the assistance from Mr. Joachim Schmitz would be greatly appreciated.
- I create a brand new score with a VST accordion and MuseScore plays it perfectly fine.
- I save that score, close it and quit MuseScore.
- I start MuseScore again and open the same score.
- I confirm that the reloaded score visually looks like its previous original.
- I check the VST plugin in the mixer and, sometimes when originally chosen and saved VST instrument is not properly memorized, I assign again the same VST accordion.
- When pressing the space-key or clicking the Play button MuseScore immediately crashes :-(
FYI:
a) I have already reinstalled my MuseScore 4.4.2 Studio and it didn't help.
b) Reverting MuseScore to factory settings doesn't help either.
c) Important or not, but I have no ideas about the errors: "Could not find the tokens file: C:/Users/Kw5U/AppData/Local/MuseScore/MuseScore4/musescorecom_cred.dat and audiocom_cred.dat".
d) I also tried to bypass the Log error message: "ERROR | main_thread | ExtensionsConfiguration::manifestConfigs | failed read config data, err: [406] An error occurred when reading from the file: C:/.../AppData/Local/MuseScore/MuseScore4/plugins/plugins.json".
I temporarily created a directory ...\AppData\Local\MuseScore\MuseScore4\plugins and copied file ...\AppData\Local\MuseScore\MuseScore4\known_audio_plugins.json as ...\AppData\Local\MuseScore\MuseScore4\plugins\plugins.json.
This doesn't help.
e) Originally, I forgot to mention above that there is also a lot of QML error messages in the MS Studio logs.
Note: My MuseScore Studio 4.4.2 also crashes when trying to play any of the old scores, both on Windows 10 Home and Windows 11 Enterprise :-(
Please see my Diagnostic file attached.
Any help or advice would be welcome!
Thanks,
Vlada
| Attachment | Size |
|---|---|
| Diagnostics_Win-10_MuseScore-4.4.2-Crashes.zip | 1.27 MB |
| Diagnostics_Win-11_MuseScore-4.4.2-Crashes.zip | 493.66 KB |
Comments
For better and maybe faster investigation, Attaching a .mscz file that crashes would be at least as important as attaching the Diagnostic file.
In reply to Attaching the .mscz file… by cadiz1
Thanks for the prompt action, but please note that I use Native Instruments - Kontakt 7 and Virtual Accoustic Guerrini Accordion VST, so unfortunately you can not reproduce the same issue. FYI, I have been using all this for more than a year and everything worked just fine with the MuseScore Studio 4.3.
In reply to Thanks for the prompt action… by VladaScore
So normal troubleshooting would be to make a score without your VST's. Then add and/or substitute one at a time until the problem occurs.
In reply to So normal troubleshooting… by bobjp
Well, maybe it's Native Instruments, but not necessarily. The program can crash for other reasons, too.
Attaching a score would corroborate either lead.
In reply to So normal troubleshooting… by bobjp
I tried to clearly explain that everything works fine when a brand-new score is created and being played, but MSStudio plays it fine only and only until that score file gets closed. After that I almost always needed to reassign VST instruments (they seem sometimes not to be saved in the .mscz file anymore), but furthermore after pressing Play button MSStudio crashes without playing any single note.
This is very frustrating and stressful experience.
In reply to I clearly explained that… by VladaScore
Ok, so it's needed to report this issue on Github, here: https://github.com/musescore/MuseScore/issues
In reply to Ok, so it's needed to fill … by cadiz1
I have no GitHub account, but if that is my only option please let me know.
In reply to I have no GitHub account,… by VladaScore
To open a GitHub account, all you need to do is to Sign In and enter a name (or username) and password. That's all there is to it.
Once this is done, click on "New issue", the green label in the top right-hand corner.
In reply to To open an account, all you… by cadiz1
OK, created: https://github.com/musescore/MuseScore/issues/24956
In reply to OK, created: https://github… by VladaScore
I forgot to mention above that I suspect these crashes might be caused just by the QML error(s) or by bugs in the score file saving process for those with the VST instruments used.
In reply to OK, created: https://github… by VladaScore
Thank you very much for setting the process in motion. For the past month I've run into the very same issue when using either Kontakt 6 or 7 (with various instruments including the Play Series and other native Kontakt libraries) in v4.4.2. Have you had success with v4.4.3 or perhaps downgrading back to v4.3?
Edit: Just noticed that there is no backwards compatibility from v4.4 to v4.3. This is very upsetting as it means the process on a bunch of projects is now inaccessible to me and MuseScore is essentially dead for me. Guess I gotta move to a DAW then.
In reply to Thank you very much for… by TheCluelessComposer
There is backwards compatibility if you export as xml.
In reply to There is backwards… by bobjp
Or if you enable it in the settings
See How to open scores from a newer Musescore 4 version with an older version
In reply to Or if you enable it in the… by Jojo-Schmitz
Thanks for the suggestions to both of you. Does this include MuseSounds, because those did not seem to work for me in v4.3? I also remember that MuseSounds got migrated to the new MuseHub when I upgraded to v4.4.
In reply to Thank you very much for… by TheCluelessComposer
@TheCluelessComposer, you can find the answer(s) in my last message sent and explained at the very end of page at this link:
https://github.com/musescore/MuseScore/issues/24956
I wish you good luck !