Ah I see, thanks for explaining -- I understand now. All the best, Ien

On Fri, Jul 8, 2016 at 1:15 PM, Element Green <elem...@elementsofsound.org>
wrote:

> Hello Ien,
>
> No, the APIs work fine and so do the related shell commands for setting
> these parameters.  What I was clarifying is that there are no embedded MIDI
> commands (to my knowledge) for setting the reverb/chorus parameters (depth,
> frequency, etc) in a MIDI stream.  There aren't any MIDI standards for
> these things (to my knowledge), which is probably the main reason why this
> is missing.  Implementing something like what I was describing previously
> would require creating new interfaces, which have no standard definition,
> which would be specific to FluidSynth.
>
> Best regards,
>
> Element
>
> On Fri, Jul 8, 2016 at 10:28 AM, Ien Cheng <i...@alum.mit.edu> wrote:
>
>> Hi Element -
>>
>> I'm surprised to hear there isn't support for reverb/chorus settings.
>>
>> Does that mean e.g. reverb settings api call
>> <http://fluidsynth.sourceforge.net/api/synth_8h.html#a9740cb53a1cc10887694cbca5f800dc1>
>> doesn't do anything by design at the moment? If so, is there any way (other
>> than looking at the source) to tell from the API docs which APIs are
>> actually implemented?
>>
>> Thanks, Ien
>>
>>
>> On Fri, Jul 8, 2016 at 11:45 AM, Element Green <
>> elem...@elementsofsound.org> wrote:
>>
>>> Hello,
>>>
>>> FluidSynth follows the MIDI Tuning Standard in regards to SYSEX command
>>> data.  I'm not real familiar with this myself, but a quick search on the
>>> Internet for "MIDI Tuning Sysex" should bring up some useful info.
>>>
>>> As far as setting chorus and reverb parameters parameters (beyond just
>>> the send value), there currently isn't anything in FluidSynth to support
>>> this.  I believe there has been talk in the past about adding FluidSynth
>>> specific Sysex or RPN commands for things like this.  It may be interesting
>>> to even add the ability to run arbitrary commands using Sysex and the usual
>>> FluidSynth shell syntax (just occurred to me while writing this).  Some
>>> thought about security is probably in order though.  I don't think there
>>> are any dangerous commands that could be embedded in a MIDI file at the
>>> moment (such as deleting files or what not - deserves some analysis), but
>>> if there were any bugs in this code, it may be possible for someone to
>>> craft data to exploit it.  At any rate, perhaps the option could be left
>>> disabled by default.
>>>
>>> Best regards,
>>>
>>> Element
>>>
>>>
>>> On Thu, Jul 7, 2016 at 11:49 PM, jean-jacques.ceresa <
>>> jean-jacques.cer...@enac.fr> wrote:
>>>
>>>> Hi, Ben
>>>> >How do I set the various FluidSynth parameters for reverb and chorus
>>>> via MIDI commands, as opposed to putting them in a config file or via
>>>> telnet?
>>>>
>>>> As far i remember there is no specific CC in the MIDI specifications.
>>>> Anyway, this should be done via MIDI sysex but actually I don't know if
>>>> Fluidsynth have support.
>>>> The same remark is true for settings "Basic Channel"  from MIDI in the
>>>> recent poly-mono patch. In this patch, this as not be implemented because
>>>> of the lack of specification
>>>> knowledge about Fluidsynth sysex.
>>>> I remember that MIDI sysex has been used for "MIDI tunings". I wonder
>>>> if someone know the specific sysex code relevant to Fluidsynth ?.
>>>>
>>>> jjc
>>>>
>>>>
>>>>
>>>> Le 08/07/2016 03:18, Ben Gonzales a écrit :
>>>>
>>>>> Hi all.
>>>>>
>>>>> How do I set the various FluidSynth parameters for reverb and chorus
>>>>> via MIDI commands, as opposed to putting them in a config file or via
>>>>> telnet?
>>>>>
>>>>> The parameters are things like room size, width , damping, speed, etc.
>>>>>
>>>>> Ben
>>>>>
>>>>> _______________________________________________
>>>>> fluid-dev mailing list
>>>>> fluid-dev@nongnu.org
>>>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> fluid-dev mailing list
>>>> fluid-dev@nongnu.org
>>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> fluid-dev mailing list
>>> fluid-dev@nongnu.org
>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>>>
>>>
>>
>> _______________________________________________
>> fluid-dev mailing list
>> fluid-dev@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>>
>>
>
> _______________________________________________
> fluid-dev mailing list
> fluid-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>
>
_______________________________________________
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev

Reply via email to