From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP Profile Certification
Date: Tue, 30 May 2006 18:33:32 +0200 [thread overview]
Message-ID: <1149006812.11251.31.camel@localhost> (raw)
In-Reply-To: <447C7330.9000303@xmission.com>
Hi Brad,
> > We must be very careful here : The ICS says the Source must accept
> > connection establishment, this is different from the sink role because
> > the source will accept the connection and then send its audio stream!
>
> ok. yes, we're missing a lot of stuff here that we need to handle.
>
> we need to use "sdptool add A2SRC" to advertise the source. we need to
> listen for new connections and keep listening on the control connection
> during playback (maybe in another thread)
>
> the alsa plugin can't just block audio writes when the stream is
> stopped. most alsa clients do not have a separate transmission thread,
> so the ui will lock up. the way to handle it is to use dbus to tell the
> audio app to pause if possible.
>
> there is a lot of overlap with avrcp here, so we should make it easy to
> work that in too.
it might be a good idea to integrate everything into a deamon and only
have a stupid ALSA plugin that sends us the PCM data.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-30 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 15:19 [Bluez-devel] A2DP Profile Certification Frédéric DALLEAU
2006-05-30 15:32 ` Brad Midgley
2006-05-30 15:50 ` Frédéric DALLEAU
2006-05-30 16:30 ` Brad Midgley
2006-05-30 16:33 ` Marcel Holtmann [this message]
2006-06-19 5:33 ` Brad Midgley
2006-06-19 7:59 ` Frédéric DALLEAU
2006-06-19 14:49 ` Brad Midgley
2006-06-19 15:20 ` Frédéric DALLEAU
2006-06-21 16:50 ` Frédéric DALLEAU
2006-06-21 17:24 ` Brad Midgley
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=1149006812.11251.31.camel@localhost \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).