I had similar thoughts, re. searching the file system path not being a synth
feature. But simply deferring to the application has other downsides when it
comes to soundfont adoption in general - end users must manually configure each
application and there’s no standard way to do this. Eg. for my
Hello,
if I can say my opinion, it would be better to leave that change outside the
library.
It looks more a feature for the application that it is using FluidSynth.
This introduces also the need to distinguish between
absolute/relative/virtual/network/etc paths, that can vary on different
platf
Hi,
I like the general idea. In my opinion it only makes sense if there are
sensible default values for (nearly?) all platforms, so having a
compile-time option would be a prerequisite.
But I think requiring the user to set -O synth.soundfont-dirs=... on the
command-line if the compiled-in defaul
Per request I'm moving this discussion to the mailing list.
Motivation: https://github.com/FluidSynth/fluidsynth/issues/453
Current PR: https://github.com/FluidSynth/fluidsynth/pull/454
Essentially the feature would add an option called "synth.soundfont-dirs".
I've chosen to make this a semi-colo
