MS4 Crashing Issue
MS4 Crashes at Bar 20 consistently on the 4th offbeat (1/16th note before the bass comes in). Even with Bass part removed and with entire ensemble removed. Is this a corruption issue?
I want to go through and write it in half time at 100BPM, so if it is a corruption issue it's not the biggest of deals.
Attachment | Size |
---|---|
HeartsongFINAL.mscz | 41.37 KB |
Comments
On my system just clicking on any note in measure 20 causes a crash. and some notes in 19 and 21 also. Saving as mxl and opening in MS3, then save and open in MS4 does not help. The only thing that I could get to help is to change all instruments to MS Basic. Then there were no crashes. I suspect that there is a problem with one or more parts using Muse Sounds. You might change instruments one at a time to MS Basic until you find the culprit. Good luck
In reply to On my system just clicking… by bobjp
Earlier I tried the OP's attachment and, only having MS Basic, I could not verify the crash when opened in MuseScore 4 (Windows 10). So I moved on. Seems like you are on the right track.
(With all the issues that have surfaced since the new release, I'm taking it slow and easy with Muse Sounds.)
Edit:
I have discovered that the issue was the Piccolo part in the second last bar, the sound engine really did not like the top G, so I changed it to an E. Thank you everyone for all of your help!
In reply to Edit: I have discovered that… by Belli7
The attached file now plays properly on my system. I didn't change anything,
Open your file in MS4.
Export as mxl.
Open in MS3
Export as mxl
Open in MS4, this file plays properly.
"Save as" file attached.
HeartsongFINAL.mscz
I'm finding that multiple mxl exports between MS4 and MS3 can fix some things.
In reply to The attached file now plays… by bobjp
Is the MS3 mxl import/export step absolutely necessary?
Or does this work:
Open file in MS4.
Export as mxl.
Open that mxl in MS4
In reply to Is the MS3 mxl import/export… by Jm6stringer
I think it depends. If seen some cases yes, and some no.