Message-ID: <432CE905.6050006@xmission.com>
From: Brad Midgley <bmidgley@xmission.com>
MIME-Version: 1.0
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Subject: [Bluez-devel] caching A2DP/alsa connection
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Sat, 17 Sep 2005 22:11:49 -0600

Marcel,

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.

Brad


-------------------------------------------------------
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