[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#38941] [PATCH 0/5] Support fluidsynth and opus in sdl(2)-mixer, and
[bug#38941] [PATCH 0/5] Support fluidsynth and opus in sdl(2)-mixer, and other tweaks
Sun, 5 Jan 2020 13:23:44 +0100
thanks for the patches!
On Sun, 05 Jan 2020 11:36:34 +0100
Timotej Lazar <address@hidden> wrote:
> The MIDI backends need additional runtime configuration. Fluidsynth
> requires a soundfont to be installed and specified when running a
> program that uses sdl-mixer, e.g.:
> If this is not set, the bundled timidity backend is used, which can use
> the freepats samples. Configuration must be specified since only files
> under /etc are checked by default, e.g.:
> I’m not sure if and how default values for these vars can be specified
> for all programs using sdl-mixer, and I would prefer to leave the choice
> of backend to the user anyway.
> However, we should probably document them somewhere. Would a comment be
Let's put it in the description of the sdl-mixer package.
After all, it would document the usage of an interface that sdl-mixer provides.
> Dependent packages can then wrap
> binaries to set required paths if needed.
> Alternatively we can add freepats and/or fluid as inputs to sdl(2)-mixer
> and patch the source to look for them in the store.
How often is it that a user switches MIDI soundfonts?
Does a user expect a default soundfont?
That would tell us whether we should provide such a default (and increase
the closure size of sdl2-mixer considerably, maybe?).
There's also a procedure "sdl-union" which already does sdl magic. We could
also add some stuff for MIDI there, maybe.
In the mean time, I've applied your patchset to master since it only adds
functionality and only has few dependents.
Could you provide an update to the description or similar as a patch?
Description: OpenPGP digital signature