Hi,
2017-11-11 22:39 GMT+01:00 Tom M. :
> > But it seems like glib includes cross-platform dynamic library loading
> functions. So maybe I could switch to using those. (Tom... any objections
> to that?)
>
> Not at all. That's exactly the reason we have glib for (...and the reason
> we'll never ge
> But it seems like glib includes cross-platform dynamic library loading
> functions. So maybe I could switch to using those. (Tom... any objections to
> that?)
Not at all. That's exactly the reason we have glib for (...and the reason we'll
never get rid of it ;) )
You could think about wrapin
Hi Ahmed,
great that you want to test it on Windows! But I'm not surprised that it
doesn't work... the code uses dlopen from dlfcn.h and that isn't available
for Windows (or so I've read... don't really have any experience with
writing code for Windows).
But it seems like glib includes cross-plat
Hi All,I would like to try this for windows. I usually configure and generate by cmake for visual studio 2010. The original 1.1.8 can be successfuly built, but not for this one with LADSPA support. It gives a "cannot open include file dlfcn.h" error, but this file also depends on fearures.h and the
> So the question really is if the API should expose the ladspa_fx object at
> all, or if all LADSPA API functions take a synth object instead. My personal
> aim is to be able to manipulate the synth->ladspa_fx, so the latter option
> would be best. But it could be useful to be able to create ad
Hi again,
I've added some more documentation that hopefully explains the effect
signal paths in FluidSynth and how to replace the internal effects with
LADSPA plugins:
https://github.com/FluidSynth/fluidsynth/commit/be2db6082d10c7aedc91a85b1ed0a0568554bab7
It that understandable and explains it i
Hi JJC,
thanks a lot for looking at it and giving feedback!
2017-11-11 15:21 GMT+01:00 Ceresa Jean-Jacques <
jean-jacques.cer...@orange.fr>:
> Most user doen't know about the SF2 sound engine model and ignore that
the internal reverb is a "late reverb" doing the job for
> all instruments at the
2017-11-11 10:23 GMT+01:00 Tom M. :
> > I would like to expose some (or most) of the public functions in
> src/bindings/fluid_ladspa.h as a public API.
>
> Ok. And what would be its main purpose? Enable the user to manipulate
> synth->ladspa_fx or create custom ladspa_fx units to manually render a
Hi Marcus,
I have read the documentation (2 times) and we realize that you have done a
good job.
>From the end user view ,the documentation helps very well any beginner to
>learn about the LADSPA functionnality and
how to use it in FluidSynth.
Some suggestions in my humble opinion.
> I would like to expose some (or most) of the public functions in
src/bindings/fluid_ladspa.h as a public API.
Ok. And what would be its main purpose? Enable the user to manipulate
synth->ladspa_fx or create custom ladspa_fx units to manually render audio
by calling fluid_ladspa_run() ?
> I gue
10 matches
Mail list logo
