MuseScore keeps crashing when removing Analog Lab V virtual instrument from a track preventing me from fixing the issue

• May 6, 2024 - 00:30

I made the mistake of trying to use a sound from Analog Lab V (an Arturia VST) on one of my tracks. Wasn't the right sound so I tried to remove it and replace it with a normal Muse Sound (or any other sound). No matter what I do, changing it from the Arturia instrument causes MuseScore to crash reliably and immediately.

Everything is up to date in terms of versions, and I already tried resetting MuseScore to factory settings, to no avail.

Has anyone come across something similar, and is there a clever remedy?

Any idea as to cause? MuseScore seems to be very crashy and buggy just in general....

Thank you!

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: d757433


Tried this workaround: 1) make new fresh empty track - 2) copy all "music" to this new track, then 3) attempt to delete the offending track entirely from the score (using the "Instruments" tab in the side panel.

Even this does not work.

The current workaround is to Mute the offending track, and hide it in the instrument panel so it doesn't play and doesn't show in the score. Needless to say, this is pretty hokey (and wasteful of compute resource I'm sure).

In reply to by nroozebo

If this doesn't work, try copying and pasting the other staves to an entirely separate file. Save it. You can then try to copy the offending track into the new file as well. If that works, great! If not, you'll only have to re-write the one staff.

Oh, and delete the file with the bad soundfont.

Do you still have an unanswered question? Please log in first to post your question.