Hi Ahmed,
2017-11-13 1:53 GMT+01:00 Ahmed Eraiba :
> Yes I get exactly the same problem with the master branch build, ie.
> builds successfuly, giving void function warnings and throws the same
> exceptions!
>
Ok, that is good to know. But what exactly do you mean by "exceptions"? C
doesn't have
to the usual way on Linux ?.
> - c2) Does new LADSPA plugings for Windows could be build the usual way on
> Linux (even this question is a bit out the scope) ?
>
> Thanks a lot for any possible clarifications on theses questions ?.
> Regards.
>
> Message du 11/11/17 21:
Hi Ahmed,
2017-11-13 0:30 GMT+01:00 Ahmed Eraiba :
> The last committs with LADSPA support builds successfully after the last
> fix but the synth failed to initialise, as any call to function
> fluid_settings_setstr
> throws an exeption.
>
>
Could you maybe try to build the latest master branch
Hi JJC,
2017-11-12 22:44 GMT+01:00 Ceresa Jean-Jacques <
jean-jacques.cer...@orange.fr>:
> A) I was wondering if a LADSPA library exists for Windows OS ?.
>
LADSPA is not really a library. It's a single header file:
http://ladspa.org/ladspa_sdk/ladspa.h.txt. So all you have to do to enable
LADSPA
scope) ?
Thanks a lot for any possible clarifications on theses questions ?.
Regards.
> Message du 11/11/17 21:21
> De : "Ahmed Eraiba"
> A : "FluidSynth mailing list"
> Copie à :
> Objet : Re: [fluid-dev] LADSPA refactor branch
>
>
Hi All,
Hi Ahmed,
I just installed Visual Studio 2017 on my Windows 10 machine, downloaded
the latest glib, glib-dev, pkg-config, proxy-libintl and gettext, copied
the ladspa.h file into the VS include dir and ran cmake. Then I built the
project and ran fluidsynth.
I could load a LADSPA plugin compiled f
Hi again,
2017-11-12 2:05 GMT+01:00 Ahmed Eraiba :
>
>> I pulled the last commit and recreated a new make but build failed,
>> giving this error:
>>
>> fluid_ladspa.obj : error LNK2019: unresolved external symbol __strincmp
>> referenced in function _get_effect_port_idx
>>
>
Actually, this looks l
Hi Ahmed,
2017-11-12 2:05 GMT+01:00 Ahmed Eraiba :
> I pulled the last commit and recreated a new make but build failed, giving
> this error:
>
> fluid_ladspa.obj : error LNK2019: unresolved external symbol __strincmp
> referenced in function _get_effect_port_idx
>
> Also so many "void function r
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
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
t;multi-channel output".
Great job!
regards.
> Message du 08/11/17 00:03
> De : "Marcus Weseloh"
> A : "FluidSynth mailing list"
> Copie à :
> Objet : [fluid-dev] LADSPA refactor branch
>
>
Hello all,
>
As announced in an earlier mail on t
Hello all,
As announced in an earlier mail on this list, I've taken on the LADSPA
subsystem that has been part of FluidSynth for a very long time and have
tried to clean it up, document it and to improve the performance. Some of
the changes are already in the master branch on GitHub, but after the
16 matches
Mail list logo
