> David: > But I'm not completely sure about the SOUNDFONTPATH thing - how would that > be used? Is that just to make people write foo.sf2 instead of > /usr/share/soundfonts/foo.sf2? It still wouldn't give FluidSynth itself > something to load as fallback.
Oh I see. I thought you were suggesting a default *directory* which would be searched for SoundFonts (how to pick one, I hadn't thought that far ahead). So you're saying that there'd be a default *soundfont*. Then yeah, the SOUNDFONTPATH wouldn't really be part of that, because that's about prepending to the search space. There could still be a concept of a sequence of directories to search for soundfonts (so maybe if you specify a soundfont filename without any slashes in the name, it searches all the directories for such a soundfont), but that sounds like a different feature to what you're suggesting. > Orcan: > I am not sure environment variables are the right solution. Sounds a > bit old-fashioned to me. Is there a more modern way for a user to customise a set of paths to search? I don't know what's going on in Windows these days, but in the Linux space it seems like PATH (shells), CLASSPATH (Java) and so on are still the main way in which the user can customise these sorts of things. _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
