From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] audio & dbus
Date: Sun, 19 Nov 2006 18:20:30 +0100 [thread overview]
Message-ID: <4560925E.3030901@free.fr> (raw)
In-Reply-To: <455CCBD8.3080001@xmission.com>
Hi Brad,
>
>>>> int32 GetIdleDisconnect(string identifier, string profile)
>> Brad : How are we supposed to handle the case when an application
>> crashes while sending audio data ? Will he have to keep the audio
>> channel opened forever ?
>
> if the disconnect timout is set then after the timeout passes the sco
> connection will be closed.
>
> I didn't want the timeout to default to be on since it's only useful in
> the case when audio goes over hci.
Looks like you lost me there :-(, i didn't understand your last sentence
>
>> Marcel, could you provide details on all this PCM routing stuff ?
>> ALSA already has support for routing aufio through the use of audio plugins.
>> Maybe it's a bit redundant ?
>
> I was the one who brought up routing. I want the daemon to store enough
> state so the alsa plugin can figure out where audio goes.
Brad, could you provide some details on that ?
If i read your schematic correctly, there is a GUI that allows user to
choose between PCM and headset routing.
If this is what it is supposed to do, then it is possible to do it at
ALSA level without having to write any code :
Users would have to add that in their ~/.asoundrc for instance
pcm.!default {
type dmix
slave.pcm "a2dpd"
}
And this would switch their default output to be the headset.
Of course it is possible to write a program that automates that so that
people don't have to dig in their configuration files.
Cheers,
Fabien
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-11-19 17:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 6:14 [Bluez-devel] audio & dbus Brad Midgley
2006-11-16 10:22 ` Marcel Holtmann
2006-11-16 15:48 ` Brad Midgley
2006-11-16 16:03 ` Marcel Holtmann
2006-11-16 16:17 ` Johan Hedberg
2006-11-16 16:45 ` Brad Midgley
2006-11-16 17:18 ` Marcel Holtmann
2006-11-17 19:35 ` Brad Midgley
2006-11-17 19:53 ` Brad Midgley
2006-11-16 19:19 ` Brad Midgley
2006-11-16 19:38 ` Fabien Chevalier
2006-11-16 20:45 ` Brad Midgley
2006-11-16 19:27 ` Fabien Chevalier
2006-11-16 20:36 ` Brad Midgley
2006-11-19 17:20 ` Fabien Chevalier [this message]
2006-11-20 1:27 ` Brad Midgley
2006-11-21 19:23 ` Fabien Chevalier
2006-11-21 21:02 ` Brad Midgley
2006-11-22 11:09 ` 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=4560925E.3030901@free.fr \
--to=fabchevalier@free.fr \
--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.