Well, the problem is not exactly if there is currently a workaround or not. The question is to know if you can reproduce this issue and where and when?
And so, to help you and other users, in order to investigate, it is necessary that you attach the current score (or by providing very precise steps from scratch, ie a new score)
The score I'm working on was an "xml" file exported from Sibelius 7 and imported at first in MuseScore 2.3.2. Then upgraded to MuseScore 3.0.
Also I'm using midi outpus through virtual MIDI cable "loopMIDI" into a DAW called "Reaper" loaded with virtual instruments.
I didn't experienced this issue working on new files.
Comments
For checking what happens, we need that you attach the actual score demonstrating what you observe.
Changing to "Page view" instead of "Continuous View" before saving seems to be fixing this issue.
In reply to Changing to "Page view"… by Alejandro Brukman
Well, the problem is not exactly if there is currently a workaround or not. The question is to know if you can reproduce this issue and where and when?
And so, to help you and other users, in order to investigate, it is necessary that you attach the current score (or by providing very precise steps from scratch, ie a new score)
In reply to Well, the problem is not… by cadiz1
And, just to be sure : what version do you use: 3.0 (as indicated in your issue report), or 2.3.2, or previous.
In reply to And, just to be sure : what… by cadiz1
Yes, version is 3.0 with the latest update.
So, please attach this score. We need it, really. Thanks.
The score I'm working on was an "xml" file exported from Sibelius 7 and imported at first in MuseScore 2.3.2. Then upgraded to MuseScore 3.0.
Also I'm using midi outpus through virtual MIDI cable "loopMIDI" into a DAW called "Reaper" loaded with virtual instruments.
I didn't experienced this issue working on new files.
Ok, that could explain a few things indeed. But feel free to attach this xml file, for further investigation.
Here is a score that crashes when you
Save
Henry_V.mscz