No sound on upgrade to 2.2 if default soundfont was saved as default
- In MuseScore 2.1, in synthesizer, add a soundfont, delete the soundfont. It should unlock the "save as default" button
- Save as default
- Upgrade to 2.2 (it will delete the default soundfont FluidR3Mono and replace it with MuseScore General)
- Launch MuseScore and play --> not sound
- Workaround: Open Synthesizer and add the default soundfont again or revert to factory settings, loosing all palettes, shortcuts etc... (or manually delete synthesizer.xml)
When MuseScore 2 is launched, it will use the "default configuration" that has been saved to disk, it will try to load the old default soundfont and fails. Instead if it fails, it should try to load the new default soundfont.
We can fix it in MasterSynthesizer::init(): load the default state and delete the synthesizer.xml file if we cannot set the state. It will however cause the default state to be loaded for any missing soundfont...
Comments
Also something we'd want fixed for 2.2.1, right?
I'm not sure. My proposed fix "will cause the default state to be loaded for any missing soundfont...", and it will erase the default configuration. Not sure it's really wanted. So, I would not put it in 2.2.1...
Here is a PR against 2.3 https://github.com/musescore/MuseScore/pull/3596
Better wipe that setting (in case of any missing soundfont) and revert to default rather than having no sound at all.
And here's a real life case: https://musescore.org/en/node/271001
Fixed in branch 2.3, commit 293ad6a523
fix #270996: No sound on upgrade to 2.2 if default soundfont was saved as default
Fixed in branch 2.3, commit 445d8d5d99
Merge pull request #3596 from lasconic/fix-270996
fix #270996: No sound on upgrade to 2.2 if default soundfont was save…
Fixed in branch master, commit 01780025f1
fix #270996: No sound on upgrade to 2.2 if default soundfont was saved as default
Why not including this fix geared to 2.3 in a special release, a bugfix release that would replace the current 2.2.1 download? is it too late, is now so unstable the branch? there are a growing number of people reporting as of today
If anything than maybe a 2.2.2 version, but not just silently replacing 2.2.1, that's out for too long already
Also the fix used for master and 2.3 may need more testing and thoughts, see for example my remark to the PR
In reply to If anything than maybe a 2.2… by Jojo-Schmitz
ok
In reply to If anything than maybe a 2.2… by Jojo-Schmitz
Never silently replace anything; that will make people who already use it unable to get the new version, and it will make you look bad.
I’m with IIRC MarcSabatella who said that a quick follow-up bugfix release counts as success, not as loss.
Thank you!
Automatically closed -- issue fixed for 2 weeks with no activity.
In reply to Also something we'd want… by Jojo-Schmitz
Sound font was empty. I reloaded the general font, and sound resumed! Thank you.
BTW I suggest that many people experience this because SF3 requires FluidSynth >= 1.1.7 (proof: http://www.fluidsynth.org/fluidsynth-1-1-7-released/)
So they generally need to upgrade FluidSynth.
The previous soundfont was also SF3. And AFAIK fluidsynth now just integrated what Werner invented a couple years back for MuseScore.
Nobody needs to upgrade fluidsynth to use SF3 soundfonts with MuseScore