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

[Rui Nuno Capela]

On Tue, 17 Nov 2009 00:30:56 +0100, Pedro Lopez-Cabanillas
<address@hidden> wrote:
> On Monday, November 16, 2009, Rui Nuno Capela wrote:
>> On Mon, 16 Nov 2009 00:46:43 -0800, address@hidden wrote:
>> >> 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.
> 
> If the goal is channel muting, IMO the solution should be a channel mute

> function, with a precise name and strict semantics, without collateral 
> effects. It is not necessary to link the mute status of a channel to
it's 
> assigned program, and separating both states would be more useful.
> 

no, the goal is not quite channel muting, although i believe the expedite
result to user's pov might be equivalent.

imho, goal is simply api completeness. channel preset assignment is an
accessible state. you should have two-way control through the api, that is.

a great deal for this regards to qsynth's channels widget where you can
assign whatever preset (bank, program) to whatever synth channel, at will.
you can even save the whole preset configuration for later recall. just a
little bit that is missing in the picture and that is some _official_ way
to set or keep a channel explicitly unassigned. it's no big deal, it's just
that the time seems right ;)

fwiw, you can still mute a channel at user's discretion, via midi channel
volume cc#7, as ever was. but that maybe (still) part of user's performance
and not of engine's structural configuration, which i'm trying to address.

just my .02

cheers
-- 
rncbc aka Rui Nuno Capela
address@hidden