From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP Profile Certification
Date: Tue, 30 May 2006 17:50:44 +0200 [thread overview]
Message-ID: <447C69D4.9020504@palmsource.com> (raw)
In-Reply-To: <447C6598.6050107@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!
As you said, I'm not sure it makes sense, and I can't figure how to test =
it. But I believe a typical scenario would be the following :
- you listen a2dp music from your pc (source) on the headphone (sink).
- someone call your mobile.
- you answer the call so the headphone tell the source to stop a2dp.
- while you talk, the source send audio data to /dev/null.
- when you hangup, the headphone will tell your computer to send the =
music again.
Fr=E9d=E9ric
Brad Midgley a =E9crit :
>Fr=E9d=E9ric
>
> =
>
>>- Accept Connection Establishment,
>>- Accept Start Streaming,
>>- Accept Connection Release.
>> =
>>
>
>see a2recv for these. it implements the a2dp sink. there is not any sort
>of special connection with alsa for this, but i'm not sure it makes
>sense since this runs more like a daemon and just sends any audio that
>comes in to the speakers.
>
> =
>
>>- An entry must also appear in SDP records.
>> =
>>
>
>sdptool add A2SNK
>
>brad
>
>
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
> =
>
_______________________________________________
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 15:50 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 [this message]
2006-05-30 16:30 ` Brad Midgley
2006-05-30 16:33 ` Marcel Holtmann
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=447C69D4.9020504@palmsource.com \
--to=frederic.dalleau@palmsource.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;
as well as URLs for NNTP newsgroup(s).