[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 12:42:23 +0100
User-agent: KMail/1.9.6 (enterprise 20070904.708012)

On Tuesday, November 17, 2009, address@hidden wrote:
> Quoting Pedro Lopez-Cabanillas <address@hidden>:
> >> 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.
> >
> > Regards,
> > Pedro
> Good point.  Couldn't mute be accomplished by simply setting the
> volume MIDI controller to 0 though?

It may be not enough, depending on the scenario. Think about using a MIDI 
player without a "channel mute" button, like aplaymidi, and files that aren't 
under your control, with FluidSynth as the MIDI synth. Even if you set a 
channel volume to 0, the song/player may send another value at any time. 

I think the users would like to have channel mute buttons in QSynth, that 
would not be affected by volume controller messages sent by player 


reply via email to

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