MuseScore4 crashing when trying to open a bigger choir project
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore4 crashing when trying to open a bigger choir project
MuseScore4 is crashing since today when trying to open a bigger choir project with 4 voices + Piano. Mixer was configured to use VST instruments and Muse-FX were also activated (compressor and master).
This is reproducable always when loading this score. Immediately MuseScore perishs. After opening it tells that last session crashed unexpectedly.
Yesterday same configuration and project still worked flawlessly. Over night, Mac run and obviously it crashed over night, as MuseScore4 did not run anymore when I came back to my Mac.
Attached, please find the score with which it crashes constantly now.
| Attachment | Size |
|---|---|
| Air.mscz | 433.66 KB |
Comments
In reply to (No subject) by Jojo-Schmitz
I did not yet understand what "Frequency" many or once means actually, dear Jojo. Can you please explain so that I use this correctly next time?
In reply to I did not yet understand… by fluegeltraum
I uncovered and dedusted this hidden little piece of secret just now *blow* see https://musescore.org/en/handbook/3/bug-reports-and-feature-requests
Frequency relates to the number of people who have reported the issue. 1 reporter = Once, 2-5 reporters = Few, 6+ reporters = Many.
I can open the score alright on Windows 10. To help troubleshooting, I've attached a few versions of this score. If the version with no VSTS loads correctly, then we can assume that the issue has something to do with those VSTs. I've also made one version for each instrument, containing only that instrument. If any of those load correctly, then we can assume that the issue relates to something in one or more of the instrument parts.
In reply to Frequency relates to the… by Trainzack
Thanks this helps partially. Following results:
Air_0 (no VSTs).mscz always crashes
Air_0 (no VSTs, Vibraphon).mscz always crashes
Air_0 (no VSTs, bass).mscz often crashes
Air_0 (no VSTs, Tenor).mscz sometime crashes
Air_0 (no VSTs, alt).mscz works best.
Air_0 (no VSTs, Flugel).mscz works best.
Additional info:
In former MuseScore3 all scores were opened in one instance of MuseScore.
But I recognized, that in the new version, several parallel instances of Musecore4 are starting.
Is this intentional? See attached Picture!
In reply to Thanks this helps partially… by fluegeltraum
Now I have reconstructed a new Musescore4 file from an import from my former Musescore3 file and added as VST the Opus Player from EastWest Soundsonline for the Grand Piano sound, as I did with the non-working Musescore4 file before and also added the Compress MuseFx for the Piano and also added the Master MuseFx for the final mixing output channel. And this one actually works. Perhaps you can see a difference between the file before and this file? See attached the now working file:
P.S.: I have recognized that the VST instrument Opus from EW Soundsonline got an update inbeetween and that it threw a message today when I wanted to add this instrument for the Piano audio. Perhaps this unexpected message led to a crash of the crashing Musescore4 file before? But there must have been also an effect on the saved Musescore4 file, because even if I have now updated the Opus player, the Musescore4 file from before which should be identical to the actual one, still crashes. And this attached one here works.
In reply to Can you please reconstruct a… by fluegeltraum
Please set to solved, as the problem could be overridden. I restored a MuseScore 3 version of the file and reloaded this to Musescore4. Then I added again the EastWest Opus instrument. Up-to-now it works flawlessly with this setup.
The problem seems to besolved by update of VST3 EastWest Opus player.