public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] org.bluez.Audio
Date: Tue, 12 Dec 2006 09:45:47 -0700	[thread overview]
Message-ID: <457EDCBB.8080207@xmission.com> (raw)
In-Reply-To: <457C2D10.5040801@free.fr>

Fabien

> Brad, i think the 'only on sco channel at a time argument' is not very
> pertinent, for two reasons:
>   * First, i'm not sure there is an added value to be able to mix sound
> channels to a sco headset.
>   * Second, if we think this is really needed, ALSA provides all
> required facilities to mix multiple streams to one (think to the dmix
> plugin). For your information, dmix is now on by default since alsa
> 1.0.10 if i remember. Previously most cheap computers were only able to
> play one PCM stream at a time. While annoying,  that didn't kill anybody
> tought ;-)

maybe the documentation could use some improvement, but I'm in agreement
with you. We should give the plugin its own file descriptor for the sco
link.

Brad

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-12-12 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06  5:31 [Bluez-devel] org.bluez.Audio Brad Midgley
2006-12-06 20:43 ` Jose Vasconcellos
2006-12-06 21:24   ` Brad Midgley
2006-12-10 15:51     ` Fabien Chevalier
2006-12-12 16:45       ` Brad Midgley [this message]
2006-12-12 19:53         ` Fabien Chevalier
2006-12-12 20:24           ` Brad Midgley
2006-12-10 15:51 ` Fabien Chevalier

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=457EDCBB.8080207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox