Hi, 2017-11-11 19:07 GMT+01:00 Tom M. <tom.m...@googlemail.com>:
> I would rather prefer exposing (i.e. adding a getter) for synth->ladspa_fx > than introducing even more synth API functions that in the end would only > wrap those of fluid_ladspa.h. And having LADSPA API functions taking a > synth object to manipulate the ladspa instance of the synth object doesnt > feels right either. I've just added two commits to the ladspa branch to expose all functions that are necessary to create, link and manipulate effects via the FluidSynth API. There's also a new getter function to retrieve the synth->ladspa_fx instance. fluid_ladspa.h/c are now always included, but all the LADSPA functionality is replaced with dummy functions that return NULL, FLUID_FAILED or FALSE in case LADSPA is not compiled in. Any comments would be highly appreciated. Either here or as comments on the relevant commits on GitHub. Cheers, Marcus
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
