From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: "Henryk Plötz" <henryk@ploetzli.ch>
Subject: Re: [Bluez-devel] a2play and Toshiba SR-1 Bluetooth Headset
Date: Fri, 26 Nov 2004 05:29:16 +0100 [thread overview]
Message-ID: <1101443356.6465.81.camel@pegasus> (raw)
In-Reply-To: <20041126041158.GF27879@snoopy.src.ricoh.co.jp>
Hi Alain,
> > You can try to hack the a2play.c to use SEID 3 instead of 1 and see what
> > the audio sink on SEID 3 offers you. Run the hcidump 1.15.
>
> The SEID 1 is pretty weird in fact ... at least doesn't offer things that
> can be decoded by hcidump (sorry guys .. just no time now to read AV specs
> in details).
you meant SEID 3, right? Please do the same for SEID 4. We can't do
anything useful with audio source, but it is nice to know what it is.
> > ACL data: handle 0x0028 flags 0x02 dlen 12
> L2CAP(d): cid 0x0041 len 8 [psm 25]
> AVDTP(s): Discover rsp: transaction 0
> ACP SEID 1 - Audio Sink
> ACP SEID 3 - Audio Sink
> ACP SEID 4 - Audio Source
> < ACL data: handle 0x0028 flags 0x02 dlen 7
> L2CAP(d): cid 0x0040 len 3 [psm 25]
> AVDTP(s): Capabilities cmd: transaction 1
> ACP SEID 3
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 0x0028 flags 0x02 dlen 19
> L2CAP(d): cid 0x0041 len 15 [psm 25]
> AVDTP(s): Capabilities rsp: transaction 1
> Media Transport
> Media Codec - non-A2DP
> 04 00 01 00 01 00 FC
So they use their own codec here. It is fine, but doesn't help us and
even the specification wouldn't tell us anymore. Actually I expect to
see a MP3 codec.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-26 4:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 9:11 [Bluez-devel] a2play and Toshiba SR-1 Bluetooth Headset Alain Volmat
2004-11-25 10:25 ` Henryk Plötz
2004-11-25 10:56 ` Alain Volmat
2004-11-25 12:17 ` Marcel Holtmann
2004-11-26 3:40 ` Marcel Holtmann
2004-11-26 3:56 ` Henryk Plötz
2004-11-26 4:12 ` Marcel Holtmann
2004-11-26 9:00 ` Sebastien HENRIO
2004-11-26 17:29 ` Marcel Holtmann
2004-11-27 1:04 ` Henryk Plötz
2004-11-27 3:09 ` Marcel Holtmann
2004-11-26 4:11 ` Alain Volmat
2004-11-26 4:27 ` Alain Volmat
2004-11-26 4:41 ` Marcel Holtmann
2004-11-26 4:57 ` Alain Volmat
2004-11-26 4:29 ` Marcel Holtmann [this message]
2004-11-26 4:54 ` Alain Volmat
2004-11-26 8:32 ` Brad Midgley
2004-11-26 8:07 ` 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=1101443356.6465.81.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=henryk@ploetzli.ch \
/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