Re: [fluid-dev] More commits on the way to 1.1.1

[Rui Nuno Capela]

On Mon, 16 Nov 2009 00:46:43 -0800, address@hidden wrote:
> Quoting Rui Nuno Capela <address@hidden>:
>>> int fluid_synth_get_channel_preset_info
>>> (fluid_synth_t *synth, int chan, fluid_preset_info_t *info);
>>>
>>
>> looks good enough.
>>
> 
> I have a patch against QSynth 0.3.4 which adds support for the new API  
> with backwards compatibility with older versions.  I'll send it your  
> way, once I know this API is here to stay.
> 
>> re. assigned field, just one question: is there any official way (api)
to
>> keep, force or (re)set one channel preset as unassigned ?
>>
> 
> No it doesn't seem there is a way to set a single channel to  
> unassigned with the public API.  There is a private function called  
> fluid_synth_set_preset, which could be used to set the preset to NULL,  
> which would have the effect of setting it to unassigned, but that  
> isn't much help in your case.  How do you see this being useful?
> 

well, it's been a _long_ time missing function. if one can assign one
channel preset, why can't the same be reset unassigned, just for closure,
functional completeness sake?

iirc, there were some requests on this regard from time to time, that is,
a way to set one channel silent, unassigned, with no preset, permanently.

fact is, once you assign a preset to a channel, which is initially
unassigned for instance, you're doomed to life with that setting. you can
choose another preset but you can't revert the move. if it was a user
mistake, then he/she has to unload the soundfont and do it all over by
loading it again first. it might be just a little hindrance but i think now
is the time to fill the gap and extend the (public) api in that regard,
while we have a chance ;)

byee
-- 
rncbc aka Rui Nuno Capela
address@hidden