Subject: Re: [Bluez-devel] caching A2DP/alsa connection
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
In-Reply-To: <432CE905.6050006@xmission.com>
References: <432CE905.6050006@xmission.com>
Content-Type: text/plain
Message-Id: <1127216847.5168.27.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Tue, 20 Sep 2005 13:47:27 +0200

Hi Brad,

> I remember you were trying to keep the headset connection open between 
> the quick audio device close and reopen that some clients like xmms do.
> 
> I started thinking we need to put esd or another audio server or alsa 
> layer between the apps and our libalsa a2dp connection. Could we extend 
> the caching to work between different apps this way? We may even be able 
> to use a soft mixer to get simultaneous clients...
> 
> This is part of the reason I've been slow to jump in. It seems like I'd 
> need to understand alsa up and down to know how to best make this work.

even I have to look at it again, but what also came up lately is a
native integration of A2DP as GStreamer plugin. Maybe you wanna start
looking at that, because I never looked at any Code of the GStreamer
project by now.

Regards

Marcel


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel