[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fluid-dev] New Reverb and Chorus API versus actual API
From: |
Tom M. |
Subject: |
Re: [fluid-dev] New Reverb and Chorus API versus actual API |
Date: |
Sun, 18 Oct 2020 17:41:13 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
> The reason is that those actual shell fx commands are redundant with
> respective settings (synth.reverb.xxxx, synth.chorus.xxxx).> Instead, the
> user can use the commands: set synth.reverb.xxxx, set
> synth.chorus.xxxx which set the respective setting for all fx unit. Those
JJC is correct.
> fluid_synth_set_reverb_fx_xxxxx(synth, fxunit_idx,xxxxx),
> fluid_synth_set_chorus_fx_xxxxx(synth, fxunit_idx,xxxxx).
I kept thinking about this. If we decide against the "2"-suffix my
current favorite is:
fluid_synth_set_reverb_group_xxxxx()
fluid_synth_set_chrous_group_xxxxx()
This would be consistent with the synth.effects-groups setting.
And, like JJC, I would still vote for deprecating the old API functions.
Tom
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Marcus Weseloh, 2020/10/11
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Ceresa Jean-Jacques, 2020/10/14
- Re: [fluid-dev] New Reverb and Chorus API versus actual API,
Tom M. <=
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Ceresa Jean-Jacques, 2020/10/18
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Marcus Weseloh, 2020/10/20
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Ceresa Jean-Jacques, 2020/10/20
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Tom M., 2020/10/20
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Marcus Weseloh, 2020/10/20
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Ceresa Jean-Jacques, 2020/10/23
- Re: [fluid-dev] New Reverb and Chorus API versus actual API, Tom M., 2020/10/23