[Top][All Lists]

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

Re: [fluid-dev] chorus module

From: David Henningsson
Subject: Re: [fluid-dev] chorus module
Date: Mon, 25 Feb 2013 09:54:25 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2

On 02/25/2013 09:38 AM, BCA wrote:
Hello David,

"The parameters are set independently of CC93"

is it possible to make them accessable via controllers?

Not currently, i e, not without writing code. I don't know how things look in jOrgan (which I assume that you use), but it might be easier to persuade Sven to map CC93 and other controllers to FluidSynth's chorus API in jOrgan, than trying to make something in FluidSynth directly.

Yes, I can set CC93 (as you say, effects as a whole), but apparently I cannot 
operate the parametres via a controller.
The effects are very good!

Many thanks
Bernd Casper.

----- Folgende Nachricht wurde empfangen -----

Absender:  David Henningsson
Empfänger:  FluidSynth mailing list
Zeit: 2013-02-25, 06:49:59
Betreff: Re: [fluid-dev] chorus module

On 02/22/2013 12:56 PM, BCA wrote:
Hello ,

the documentation about the chorus effects module says:

String. ['yes', 'no']. When set to "yes" the chorus effects module is activated.
Otherwise, no chorus will be added to the output signal.
Note that when the reverb module is active, the amount of signal send to the chorus 
module depends on the "chorus send" generator defined in the SoundFont.
Default value: 'yes'.

Does "synth.chorus.active" represent CC93?
Which controllers can operate the different FluidSynth chorus elements 

The parameters are set independently of CC93 - they both affect chorus
level. See the final chorus level as a sum of CC93, the FluidSynth
parameters, and what's set per voice in the sf2 file. (An sf2 file can
also override the default behaviour of CC93.)

// David

fluid-dev mailing list

reply via email to

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