MuseScore keeps on reverting to default soundfont
I changed the soundfont but if I restart MuseScore (or even just close and reopen the demo file) it reverts to the sound of the old (default) soundfont. When I select Display->Synthesizer it shows the new soundfont as selected, but it plays using the old one until I "open" the new one again.
After that it will play using the new soundfont but if I export the file to .ogg, I can hear that the file was created using the old (default) soundfont too.
I'm using the prerelease of 0.9.6.2 (revision 3361).
Comments
0.9.6.2 is released. Please upgrade and don't use a prerelease for serious work.
I can't reproduce with MuseScore 0.9.6.2 on Vista.
In reply to 0.9.6.2 is released. Please by [DELETED] 5
I've upgraded but the problem persists. Since reinstalling:
Open MuseScore, play: uses default soundfont.
Change soundfont, play: uses new soundfont.
File->Reload, play: uses default soundfont again.
Is the soundfont a property of the score (so that it needs to be saved) or of MuseScore? Saving the demo after changing the soundfont seems to make no difference.
This is also on Vista.
In reply to I've upgraded but the problem by Minix
The soundfont is a property of MuseScore. It's stored as a preference in
C:\Users\<USERNAME>\AppData\Roaming\MusE\MuseScore.ini
In reply to The soundfont is a property by [DELETED] 5
Thanks. I found that uninstalling MuseScore does not delete the .ini file (is that a bug?) and deleting it manually is necessary to restore default settings when reinstalling. That reverts the soundfont back to "C:/Program Files/MuseScore//sound/TimGM6mb.sf2" (is there any significance to the double /?) So this default soundfont path must be stored in the program data somewhere...
If I change the soundfont it remembers it in the ini, but seems to play using the default one after restarting or loading a new score unless the new one is explicitly reloaded. Conversely, changing the reverb and chorus seemed to have no effect until the score was reloaded. (And the default position of the sliders did not seem to match up with the values displayed next to them).
Is MuseScore using FluidSynth internally?
In reply to Thanks. I found that by Minix
-
In reply to The soundfont is a property by [DELETED] 5
I think I have solved it - the soundfont I was using is known to have had problems with FluidSynth and there is a newer version which fixes it.
It also says there are problems with FluidSynth 1.0.8 and earlier - which version does MuseScore use?
If I turn both chorus and reverb down to 0 and restart MuseScore they seem to reset to higher levels.
In reply to I think I have solved it - by Minix
MuseScore uses a modified version of Fluidsynth, not sure which one has been forked.