From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Schmidt Subject: Re: DMIX and capture stream Date: Wed, 7 Jan 2004 13:05:30 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <20040107130530.4dd7edf6.mista.tapas@gmx.net> References: <200401051741.i05HfCXl007120@dhin.linuxaudiosystems.com> <20040106223828.39d2c233.mista.tapas@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Takashi Iwai Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org On Wed, 07 Jan 2004 12:01:02 +0100 Takashi Iwai wrote: > as written in my previous mail, it was a quick hack. and there is a > better approach. > > the attached patch will add a new plugin, asym, which defines > different slave pcms for playback and capture streams. > for example, > > pcm.duplex { > type asym > playback.pcm "dmix" > capture.pcm "dsnoop" > } > Ah, ok. This solution makes even more sense, since it is more generally useful. Especially for [broken] alsa apps that don't let you specify seperate pcm's for playback/capture.. I think of this plugin as making a full duplex pcm out of two half duplex pcm. So why not call the plugin "duplexer"? Flo P.S.: One question that comes up though: What happens when you specify a full duplex device as one of the two pcm's? Will there be an error msg? Or maybe some of the "multi" functionality could be used... -- hrrrm! ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click