fluid-dev
[Top][All Lists]
Advanced

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

Re: [fluid-dev] LADSPA refactor branch


From: Ceresa Jean-Jacques
Subject: Re: [fluid-dev] LADSPA refactor branch
Date: Sat, 11 Nov 2017 15:21:36 +0100 (CET)

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.

 

One major difficulty for the end user is to understand the audio signal path in FluidSynth working alone (i.e without LADSPA).

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 same time all mixed to the input reverb . This is an important point later when talking about the "Reverb Send" port.

Consequently, most user will ignore for example:

1)that the internal reverb can't changed by an external plugin with its input/output connected to "Reverb Send"port.

2)that the internal reverb can't changed by an external plugin without breaking the soundfount design if this plugin isn' only a "late reverb" model.

 

Probably in the future it worth to complete both sections "FluidSynth Hosts Port" and "multi-channel output".

 

Great job!

regards.

 

> Message du 08/11/17 00:03
> De : "Marcus Weseloh" <address@hidden>
> A : "FluidSynth mailing list" <address@hidden>
> Copie à :
> Objet : [fluid-dev] LADSPA refactor branch
>
>
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 they were merged I noticed a few bits and pieces that were still not quite right. So i created another branch called "ladspa", that contains the rest of the refactor. And most importantly, also the documentation on how to use it.

>
Before creating a pull request and asking for those changes to be merged into master, I would be very grateful if some of you could look at the branch, compile it and try to use it by going through the documentation. Any feedback is highly appreciated. Especially bugs reports, missing features, missing bits in the documentation or suggestions to improve the command line interface.

>
The documentation can be found in docs/ladspa.md:
https://github.com/FluidSynth/fluidsynth/blob/ladspa/doc/ladspa.md
>

>
The branch itself on the GitHub repo:
https://github.com/FluidSynth/fluidsynth/tree/ladspa
>

>
All the best,

>
    Marcus

>

>



_______________________________________________
fluid-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fluid-dev


reply via email to

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