From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] AVDTP socket?
Date: Sun, 14 Nov 2004 00:54:13 -0700 [thread overview]
Message-ID: <41970F25.4020902@xmission.com> (raw)
In-Reply-To: <1100351199.7349.50.camel@pegasus>
Marcel
Argh... I'm stuck again. the avdtp_set_configuration command goes out
but reading the response just blocks. I'm not sure what is wrong... I send:
00 -> header = request
03 -> AVDTP_SET_CONFIGURATION
04 -> acp_seid = 1
04 -> int_seid = 1 (how should I choose the int_seid?)
01 -> service category = media transport
00 -> length of service capabilities = 0
07 -> capability type = media codec
06 -> bytes remaining? not sure if this is right.
00 -> media type = audio media type
00 -> media codec type = SBC
22 -> 44.1khz stereo
15 -> 16-byte blocks, 8 subbands, "loudness" allocation
02 -> min bitpool
fa -> max bitpool
a2play.c in cvs contains the code I'm trying...
Brad
Marcel Holtmann wrote:
> Hi Brad,
>
>
>>>>The accept looks like this byte-for-byte:
>>>>
>>>>02 -> response accept
>>>>02 -> AVDT_GET_CAPABILITIES
>>>>01 -> category = media transport
>>>>00 -> length of service capabilities = 0
>>>>07 -> 7 'elements' follow
>>>>06 -> elements[0]
>>>>00 ->
>>>>00 ->
>>>>ff ->
>>>>ff ->
>>>>02 ->
>>>>fa -> elements[6]
>>
>>>this should be the codec specific part. Look at A2DP for more details.
>>
>>It doesn't totally seem to match up. The last 4 bytes seem to be the
>>capabilities of SBC (p.20 of a2dp)
>>
>>ff -> supports all sampling frequencies, channel modes
>>ff -> supports all block lengths, subbands, allocation methods
>>02 -> minimum bitpool val
>>fa -> max bitpool val
>>
>>I can't find where the first 06, 00, 00 fit. Also, does the seid=1 in
>>the avdtp_discover accept correspond to only supporting SBC? I wasn't
>>expecting to know the supported codecs until after the first
>>avdt_get_capabilities.
>
>
> I looked it up and the GET_CAPABILITIES response you get back contains
> two block. The first is the "media transport" with 0 bytes of additional
> information and the second is the "media codec" part with 6 bytes of
> codec specific information.
>
> 0x01 = media transport
> 0x07 = media codec
>
> The first 0x00 represents the "media type" and the second the "media
> codec type". And this means "audio" and "SBC". And the rest is SBC
> specific as you already recognized.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-14 7:54 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 5:36 [Bluez-devel] AVDTP socket? Brad Midgley
2004-11-07 12:27 ` Marcel Holtmann
2004-11-07 16:34 ` Brad Midgley
2004-11-07 16:54 ` Marcel Holtmann
2004-11-07 18:55 ` Brad Midgley
2004-11-07 21:33 ` Marcel Holtmann
2004-11-10 5:46 ` Brad Midgley
2004-11-10 8:47 ` Marcel Holtmann
2004-11-10 18:01 ` Brad Midgley
2004-11-10 18:57 ` Marcel Holtmann
2004-11-12 23:13 ` Brad Midgley
2004-11-13 0:38 ` Marcel Holtmann
2004-11-13 3:13 ` Brad Midgley
2004-11-13 13:06 ` Marcel Holtmann
2004-11-14 7:54 ` Brad Midgley [this message]
2004-11-14 15:29 ` Marcel Holtmann
2004-11-17 15:47 ` Brad Midgley
2004-11-17 15:52 ` Marcel Holtmann
2004-11-17 19:52 ` Brad Midgley
2004-11-17 20:01 ` Marcel Holtmann
2004-11-18 13:27 ` Henryk Plötz
2004-11-18 15:26 ` Brad Midgley
2004-11-18 19:11 ` Marcel Holtmann
2004-11-19 18:32 ` Henryk Plötz
2004-11-19 21:40 ` Brad Midgley
2004-11-18 23:59 ` Marcel Holtmann
2004-11-19 9:03 ` Brad Midgley
2004-11-19 11:41 ` Marcel Holtmann
2004-11-19 16:35 ` Brad Midgley
2004-11-19 16:53 ` Marcel Holtmann
2004-11-19 17:39 ` Marcel Holtmann
2004-11-19 20:45 ` Marcel Holtmann
2004-11-19 21:20 ` Henryk Plötz
2004-11-19 21:33 ` Marcel Holtmann
2004-11-19 23:58 ` Henryk Plötz
2004-11-19 21:51 ` Brad Midgley
2004-11-19 22:04 ` Marcel Holtmann
2004-11-19 23:23 ` Brad Midgley
2004-11-20 0:09 ` Marcel Holtmann
2004-11-20 0:04 ` Henryk Plötz
2004-11-20 0:43 ` Marcel Holtmann
2004-11-20 0:50 ` Henryk Plötz
2004-11-20 5:04 ` Marcel Holtmann
2004-11-19 18:44 ` Henryk Plötz
2004-11-19 18:38 ` Henryk Plötz
2004-11-19 18:56 ` Marcel Holtmann
2004-11-19 21:06 ` Henryk Plötz
2004-11-19 21:23 ` Marcel Holtmann
2004-11-21 5:46 ` Henryk Plötz
2004-11-21 17:44 ` Marcel Holtmann
2004-11-22 3:18 ` Marcel Holtmann
2004-11-22 4:32 ` Henryk Plötz
2004-11-22 13:28 ` Marcel Holtmann
2004-11-23 0:53 ` Henryk Plötz
2004-11-23 6:22 ` Marcel Holtmann
2004-11-22 4:22 ` [Bluez-devel] sbc reindent Brad Midgley
2004-11-15 8:24 ` [Bluez-devel] AVDTP socket? Sebastien
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=41970F25.4020902@xmission.com \
--to=bmidgley@xmission.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