I get a message in the console while launching mscore :
Unable to open file "/home/ws/sfont/FluidR3.SF2"
My user name is not ws, thus the question is why does it try to open this file at this place?
That soundfont is used by "test/crossbeams.mscx" and "test/slur1.mscx" (and I guess it is not needed there at all) but also by "share/templates/Guitar Tab.mscx" and "share/templates/carol.mscx", and probably all scores that have been created using these templates. It may be used in some of the .mscz files too (can't easily grep on those to check).
Each ver. 2.0 score file contains the path of the sound font(s) loaded the last time the score was saved. I think this is related with the fact that multiple sound fonts can be loaded for each score.
If some of the stored sound font file cannot be found, the program uses the default sound font; at installation the supplied (small) sound font is the default but, via preferences, any sound font can be set as default.
So, I do not see what is "bad" with this setup; the quoted message is just a diagnostic message and it only appears if the program is launched from a command line (or has the debug window activated, as the debug version does).
I am closing the issue; feel free to re-open if you disagree!
Comments
That soundfont is used by "test/crossbeams.mscx" and "test/slur1.mscx" (and I guess it is not needed there at all) but also by "share/templates/Guitar Tab.mscx" and "share/templates/carol.mscx", and probably all scores that have been created using these templates. It may be used in some of the .mscz files too (can't easily grep on those to check).
Each ver. 2.0 score file contains the path of the sound font(s) loaded the last time the score was saved. I think this is related with the fact that multiple sound fonts can be loaded for each score.
If some of the stored sound font file cannot be found, the program uses the default sound font; at installation the supplied (small) sound font is the default but, via preferences, any sound font can be set as default.
So, I do not see what is "bad" with this setup; the quoted message is just a diagnostic message and it only appears if the program is launched from a command line (or has the debug window activated, as the debug version does).
I am closing the issue; feel free to re-open if you disagree!
M.