Hi all,
When we implemented the dynamic sample loading, we also discussed if
it would be good to provide a way to preload samples. Back then it was
mainly meant as a way to preload all presets from a MIDI file, so that
loading the samples dynamically wouldn't stall the playback. We
decided that it
Am Di., 20. Okt. 2020 um 17:49 Uhr schrieb Tom M. via fluid-dev
:
> 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
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
Hi,
>So for the shell we introduce the proposed new commands to set specific fx
>group settings.
>We keep the old fx shell commands deprecated and document that "set
>synth.reverb.xxx" should be used instead (if not already done).
>And for the API we use the function names suggested above a
Hi,
Am So., 18. Okt. 2020 um 17:41 Uhr schrieb Tom M. via fluid-dev
:
> I kept thinking about this. If we decide against the "2"-suffix my
> current favorite is:
>
> fluid_synth_set_reverb_group_x()
> fluid_synth_set_chrous_group_x()
>
> This would be consistent with the synth.effects-grou
