[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 13:00:08 +0100
User-agent: KMail/1.9.6 (enterprise 20070904.708012)

On Tuesday, November 17, 2009, Rui Nuno Capela wrote:
> On Tue, 17 Nov 2009 00:30:56 +0100, Pedro Lopez-Cabanillas
> > On Monday, November 16, 2009, Rui Nuno Capela wrote:
> >> 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
> no, the goal is not quite channel muting, although i believe the expedite
> result to user's pov might be equivalent.
> 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.

From the user's POV, CC#7 or patch change MIDI messages sent later by a MIDI 
sequencer/player on the same channel are going to void the channel muting. 
The key is your own word: "permanently". I think that the request for a 
channel mute function is sound, but should be implemented without depending 
on MIDI control change or patch change messages. And there is not any other  
MIDI standard message defined for this purpose.


reply via email to

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