[Top][All Lists]

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

[fluid-dev] New Reverb and Chorus API versus actual API

From: Ceresa Jean-Jacques
Subject: [fluid-dev] New Reverb and Chorus API versus actual API
Date: Thu, 17 Sep 2020 11:52:19 +0200 (CEST)

Hi All,


For those amoung you using actual Reverb and Chorus API (or associated shell commands).

You have noticed that theses API (or commands) allow to change one parameter for all fx unit.

For example if fluidsynth has been started with synth.effects-groups set to 2, the synthesizer has 2 fx units.

That leads with MIDI channel 0 using fx unit 0, and MIDI channel 1 using fx unit 1.

The lack of actual API that it doesn't allow to change parameters of only one fx unit (all fx unit (0,1) are affected by this change).


To overcome this issue a new set of Revert and Chorus API will be proposed with one added parameter which is the fx unit index (0 or 1)

to which the change is applied. This new API set can also behave like actual API set if fx unit index is -1.

That means that the actual API set will become redundant as soon the new API set will be proposed.

So it seems that it should be preferable to deprecate the actual API set (that should be replaced by the new API set).


Now the question is: does the deprecation of actual Reverb and Chorus API could cause issues ?


Thanks for your feedback.




reply via email to

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