RE: A2DP with AAC codec: non-existent document reference in the "Bluetooth Accessory Design Guidelines for Apple Products"
RE: A2DP with AAC codec: non-existent document reference in the "Bluetooth Accessory Design Guidelines for Apple Products"
- Subject: RE: A2DP with AAC codec: non-existent document reference in the "Bluetooth Accessory Design Guidelines for Apple Products"
- From: John Westing <email@hidden>
- Date: Thu, 04 Apr 2013 16:40:18 -0400
Shawn,
Did you ever find the answer to your question? I am stuck in a similar situation, but it sounds like you have gotten further than me. I don't understand the explanation of the packet header given in
https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf, and like you I can't find a document titled ISO/IEC 13818-3:2005, the latest version I could find was from 1998.
If the AVDTP header is the header found in Figure 4 of RFC 3016 then the RTP Market Bit (audioMuxElement for LATM) should always be 1 according to the Bluetooth Design Guidelines PDF. I'm not seeing that, I decoded the data with Wireshark (v1.9.2) and the bit is always 0.
Do I have something configured wrong? How did you figure out how to bypass the RTP header and get to the AAC audio? I took a look at the document you mentioned, ISO/IEC 14496-3:2005, but it looks like this document gives an algorithm for decoding the packet and does not give the actual breakdown of fields in the packet.
I'm trying to use built-in GStreamer elements to decode the RTP but I'm not having any luck. I'm wondering if I need to write own GStreamer plugin. I tried the rtpmp4adepay element to decode the data but the element gets hung waiting for the Market Bit/audioMuxElement bit.
Any help is appreciated.
Thanks,
Sam
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden