From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Headsetd "fallback" device
Date: Mon, 5 Feb 2007 14:55:04 +0200 [thread overview]
Message-ID: <e29894ca0702050455l24a8eb99pf654d277a5524015@mail.gmail.com> (raw)
In-Reply-To: <45C71E02.5010803@sawicz.net>
[-- Attachment #1.1: Type: text/plain, Size: 1236 bytes --]
On 2/5/07, Michał Sawicz <michal@sawicz.net> wrote:
>
> I just thought about something like that... There should be a
> possibility in headsetd or maybe the plugz, that would switch to a
> fallback device, if the headset can't be connected (it's switched off or
> whatever). The way it's working now - dropping the stream to /dev/null
> or wherever is not a wanted behavior, when someone calls You on a
> softphone.
This kind of stuff are upper level management. Even ALSA do not handle this
properly (if you plug/unplug a usb device). That's why all the major
distributions will ship with PulseAudio installed.
My POV is that we need to focus on the io audio stream interface and provide
a standard Linux device (with HAL and ALSA). The underlying headset/audio
device can be accessible as any simple pcm device (with ressource
constraints that already exists).
Mixing, routing, device abstraction, sample rate conversion and even
encoding... should be handled by upper level applications.
If you want to join the design discussion, we could have a FAQ in the
http://wiki.bluez.org/wiki/Audio wiki. Please feel free to add your
comments&questions there (this is still very *drafty* btw)
Regards,
--
Marc-André Lureau, GSmartMix
[-- Attachment #1.2: Type: text/html, Size: 1615 bytes --]
[-- Attachment #2: Type: text/plain, Size: 374 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-05 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 12:07 [Bluez-devel] Headsetd "fallback" device Michał Sawicz
2007-02-05 12:55 ` Marc-André Lureau [this message]
2007-02-05 13:37 ` Michał Sawicz
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=e29894ca0702050455l24a8eb99pf654d277a5524015@mail.gmail.com \
--to=marcandre.lureau@gmail.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