Thanks Tom, some very enlightening comments -- especially about the lack of 
errors.I had already noted that fluidsynth was not good at reporting errors.
I have now implemented fluid_synth_set_reverb() and of course it now works 
beautifully and Iget the currently set values from   value = 
fluid_synth_get_reverb_roomsize(synth); etc.
It was amazingly easy once I located the proper documentation (which I had 
already lookedfor but failed to find).
David

      From: Tom M. <tom.m...@googlemail.com>
 To: David Back <csw...@yahoo.co.uk> 
Cc: FluidSynth mailing list <fluid-dev@nongnu.org>
 Sent: Sunday, 7 January 2018, 18:17
 Subject: Re: [fluid-dev] fluidsynth, programming reverb
   
> I can only guess where to begin as the documented reverb API is limited to 
> turning reverb on or off (which I have done and it is working)

Reverb is a feature of the synth, you should therefore have a look at the 
numerous functions the synth provides:

http://www.fluidsynth.org/api/synth_8h.html

One of those functions is fluid_synth_set_reverb(), which perfectly fits your 
needs.


> I have assumed that the doubles: roomsize, damp, width and level are settings

This assumption is wrong. Those settings are not documented because they dont 
exist.

The fact that you can recall the value via fluid_settings_getnum() is due to 
the error-hiding behaviour of fluidsynths 1.1.x settings API. Whenever you set 
a setting that is unknown, it is silently registered. This behaviour was 
recently fixed upstream and will be part of fluidsynth's next major release. 
Furthermore another inconsistency regarding the settings API was addressed: all 
public fluid_settings_* functions that return an integer, which is not meant to 
be interpreted as bool, will return either FLUID_OK or FLUID_FAILED (rather 
than TRUE and FALSE as they currently do).


Tom

P.S.: fluidsynth.org/api/ is currently down, give it 20 hours to recover.


   
_______________________________________________
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev

Reply via email to