3.1 Beta: changing soundfont order in Synthesiser causes a crash
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6437, revision: 06f0ddd
- Install MS 3.1 Beta with default settings, but to a different Windows folder than 3.0.5.
- Open MS 3.1, use Resource Manager to install the High Quality (HQ) soundfont.
- The new MuseScore_General_HQ.sf3 soundfont installs itself to:
D:\Users\Dan Rootham\Documents\MuseScore3\Extensions\MUSFE\1.0\soundfonts - The old MuseScore_General.sf3 soundfont is still installed at:
C:\Program Files\MuseScore 3\sound -
Background info: the C: drive is a SSD for program files and Windows OS, the D: drive is a normal hard disk for user data.
-
Now open a score, then open the Synthesiser.
- Any attempt to change the order of the soundfonts results in a crash.
Comments
Does this crash happen with the 3.1 Beta only?
In reply to Does this crash happen with… by RobFog
On my setup, this now also crashes MS 3.0.5. I haven't played with soundfonts much until now, so I don't know if the problem existed before. But it might be something to do with my separate C: and D: disks?
Update:
1. As an experiment I copied MuseScore_General_HQ.sf3 from its default install folder:
D:\Users\Dan Rootham\Documents\MuseScore3\Extensions\MUSFE\1.0\soundfonts
to:
D:\Users\Dan Rootham\Documents\MuseScore3\SoundFonts.
2. Opened MS 3.1 Beta, opened the Synthesiser, tried to move the MuseScore_General.sf3 font to the top.
3. Result: apparent success on first try, but consistent crashes after that.
So.... is the Resource Manager placing MuseScore_General_HQ.sf3 in the wrong folder?