[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Is there some configuration file for libfluidsynth?

From: josh
Subject: Re: [fluid-dev] Is there some configuration file for libfluidsynth?
Date: Mon, 11 May 2009 16:30:15 -0400
User-agent: Internet Messaging Program (IMP) H3 (4.1.6)

Quoting David Henningsson <address@hidden>:

address@hidden skrev:
Quoting "Yair K." <address@hidden>:
Hi there,

  I want to set some fluidsynth settings globally, however most
programs only
expose the soundfont selection. Is there some global way to set default
settings like audio.periods, audio.output-channels, etc.?
You mean like a FluidSynth configuration file?  Currently no.  Seems
like that would be a nice feature though.  It would set the default
values, which an application would override.

I don't mind having a configuration file for the fluidsynth executable.
But there is one thing to look out for when we come to libfluidsynth
embedded usage; perhaps the current caller of libfluidsynth expects all
non-set values to be what they used to be. Introducing a config file in
that scenario, and the result might be that the caller does not get what
he expects.

An example could be that I write a small application that uses
fluidsynth for some rendering, expecting sample timers to be enabled
since that's the default. But in the config file, system timers are set,
and suddenly my application takes a lot longer time than expected, which
will lead to bug reports against my application.

So for libfluidsynth I would say the best solution probably is an opt-in
for the config file. For Yair, I would suggest talking to the maintainer
of "most programs" asking for more options exposed. (And there's always
the alternative of recompiling libfluidsynth of course, but if one does
so, he is probably aware that he can mess up things.)

// David

I agree, that it is a good idea not to introduce unexpected side effects of a configuration file for libfluidsynth usage. But I can also see how it is desirable to allow the user to override settings globally, regardless of the application. The configuration file could have two groups one could be [fluidsynth] and the other [libfluidsynth]. How does that sound? A side effect of this will be that potentially several paths (user and system config directories) will be searched for a config file, each time a settings object is created. I think that is OK though.

A config file won't be saved by default, but only upon request, to give the user a template for modification.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]