[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: |
Tue, 20 Oct 2020 17:48:56 +0200 |
Marcus, wait - remember:
>> [Tom] However, I vote against introducing new shell commands. Instead, the
>> existing commands, should become smart enough to detect whether they
>> have been called with one or two parameters.
> [Marcus] Good idea! [...]
Pls. what has changed your mind to "introduce the proposed new [shell]
commands"?
With your suggestion, we would have three different ways of setting
reverb+chorus. When changing the existing command and un-deprecate
them, we'll only have two. While still retaining backward
compatibility.
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., 2020/10/18
- 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. <=
- 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