Craig, Thanks, Gordon Date: Thu, 21 Jan 2016 11:07:01 -0800 From: Craig Dooley<cdooley@apple.com> To: Feng Yu Hong<fengyuhong@vimicro.com> Cc:"bluetooth-dev@lists.apple.com" <bluetooth-dev@lists.apple.com> Subject: Re: A2DP AAC codec bandwidth Message-ID:<B6156406-1236-4065-B7AF-C5C054D7581C@apple.com> Content-Type: text/plain; charset="utf-8" The encoder takes into account the MTU negotiated when determining the maximum frame size available. For example, if the device has an MTU of 565 for the AVDTP channel, that only allows for ~192kb/s, even if the endpoint configuration says the device can handle 262 kb/s. - Craig -- J. Gordon Rankin Owner and Chief Scientist ====== Wavelength Audio, ltd ====== _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com We are releasing an A2DP AAC solution this month. I looked at our code after reading your response on the MTU subject and found we are negotiating at 672 bytes. Is there some sort of calculation with the MTU number and the bandwith? I searched older posts which indicated a maximum of 885 bytes. Any information would be appreciated.
participants (1)
-
Gordon Rankin