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

[Ceresa Jean-Jacques]

> > 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 collection.

Yes organization soundfont is only the application need. As pointed by Sqweek E " ...there’s no standard way to do this..".

I don't think that fluidsynth package is the right place to define good conventions like standard search paths and/or configuration files.

Instead (as suggered by Sqweek E), the community of application end users should probably helps to do that. This should need time to collect those informations.

this should lead to a dedicaced llibrary with its API.

 

>Frankly, if the "potentially non-technical user" is too lazy to specify a proper path to the soundfont(s) he wants to use, I expect him to take the time and set up proper search paths *once*, because those are only suitable in his unique environment.

This is the minimum simple task that a end user should be able to do when this task is not frequent. Also using symbolic link should be useful.

jjc.

> > Message du 03/11/18 06:16
> > De : "Tom M." <address@hidden>
> > A : address@hidden
> > 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 @address@hidden 
> > 
> > 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 a shell environment variable.
> > 
> > > to allow the maintainer to set a reasonable default
> > 
> > That's the point: A package maintainer doesn't have the knowledge to evaluate a "reasonable default". That's why it is not done, see DEFAULT_SOUNDFONT.
> > 
> > > 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 collection. Frankly, if the "potentially non-technical user" is too lazy to specify a proper path to the soundfont(s) he wants to use, I expect him to take the time and set up proper search paths *once*, because those are only suitable in his unique environment.
> > 
> > 
> > Tom
> > 
> > 
> > 
> > 
> > _______________________________________________
> > fluid-dev mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/fluid-dev
> >