All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] caching A2DP/alsa connection
Date: Sat, 17 Sep 2005 22:11:49 -0600	[thread overview]
Message-ID: <432CE905.6050006@xmission.com> (raw)

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

             reply	other threads:[~2005-09-18  4:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18  4:11 Brad Midgley [this message]
2005-09-18 11:45 ` [Bluez-devel] caching A2DP/alsa connection Andreas Beck
2005-09-19  0:48   ` Brad Midgley
2005-09-19 11:39     ` Andreas Beck
2005-09-20  0:11     ` Andreas Beck
2005-09-20 15:45       ` Brad Midgley
2005-09-20 11:47 ` Marcel Holtmann
2005-09-20 15:43   ` Brad Midgley
2005-09-20 15:49     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=432CE905.6050006@xmission.com \
    --to=bmidgley@xmission.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.