[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Pedro Lopez-Cabanillas
Subject: Re: [fluid-dev] More commits on the way to 1.1.1
Date: Tue, 17 Nov 2009 00:30:56 +0100
User-agent: KMail/1.9.6 (enterprise 20070904.708012)

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]