Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-11 Thread Reinhold Hoffmann
r...@orange.fr; FluidSynth mailing list Betreff: Re: [fluid-dev] Allow soundfonts to be searched from multiple directories On Mon, 5 Nov 2018 at 23:59, Ceresa Jean-Jacques wrote: > > The user shouldn't have to manually edit the path themselves. >Of course he has to. Neither any m

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-10 Thread Dan Eble
On Nov 10, 2018, at 01:39, sqweek wrote: > > There's no analogous way to survey paths in use on Windows/OSX that I'm aware > of. Looking on the application side, MuseScore has its own paths: For macOS, you might wish to survey Fink , Homebrew , an

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-09 Thread sqweek
On Mon, 5 Nov 2018 at 23:59, Ceresa Jean-Jacques < jean-jacques.cer...@orange.fr> wrote: > > > The user shouldn't have to manually edit the path themselves. > > >Of course he has to. Neither any maintainer nor fluidsynth are > responsible for guessing how the user organizes his soundfont collectio

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-05 Thread Ceresa Jean-Jacques
:16 > De : "Tom M." > A : fluid-dev@nongnu.org > Copie à : > Objet : Re: [fluid-dev] Allow soundfonts to be searched from multiple > directories > > > If we decide to read from an environment variable, we should read it from > > the existing @FLUID_DAEMON_ENV_FI

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-02 Thread Tom M.
> If we decide to read from an environment variable, we should read it from the > existing @FLUID_DAEMON_ENV_FILE@. FLUID_DAEMON_ENV_FILE is a cmake variable, specifically one that points to a config file for running fluidsynth as global systemd service. This isn't suitable, I was referring to

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-02 Thread Ceresa Jean-Jacques
opie à : > Objet : Re: [fluid-dev] Allow soundfonts to be searched from multiple > directories > > 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. &g

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-02 Thread Tom
Hi, I'm happy to go along with what you said, but I have a few comments. If we decide to read from an environment variable, we should read it from the existing @FLUID_DAEMON_ENV_FILE@. It doesn't make sense to use $PATH since that has a different purpose on Linux systems (namely, searching for bina

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-02 Thread Tom M.
Thanks for the feedback guys! I share the concerns brought up here and agree that this is no suitable feature for the fluidsynth library. I.e. the current proposal to make it a FluidSetting and expose a find_soundfont() function via the API is not suitable. IMO this should be implemented as e

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-02 Thread Reinhold Hoffmann
Im Auftrag von sqweek E. Gesendet: Freitag, 2. November 2018 07:08 An: FluidSynth mailing list Betreff: Re: [fluid-dev] Allow soundfonts to be searched from multiple directories I had similar thoughts, re. searching the file system path not being a synth feature. But simply deferring to the appli

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-02 Thread Marcus Weseloh
Hi, Am Do., 1. Nov. 2018 um 20:19 Uhr schrieb Carlo Bramini < carlo.bra...@libero.it>: > 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. > I agree, this feature shouldn't be in the

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-01 Thread sqweek E.
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

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-01 Thread Carlo Bramini
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

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-01 Thread Marcus Weseloh
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

[fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-01 Thread Tom
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