commit | e28ca0c3d70c67cda2a09dc2d663a3395b13c779 | [log] [tgz] |
---|---|---|
author | Lajos Molnar <lajos@google.com> | Wed Feb 26 18:16:50 2025 -0800 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Apr 09 15:16:32 2025 -0700 |
tree | 449178781049ecafa1eaea7383ade4d9a5a42001 | |
parent | bf2838cf3578bc25859e9939fc7b5c5609eea2d6 [diff] |
mediandk: clean up AMediaCodec_getInput/OutputBuffer semantics AMediaCodec_getInputBuffer erroneously considered the offset, which could result in a smaller input buffer being returned and client confusion. In practice, input buffer offset is rarely used. Similarly, the buffer size returned from AMediaCodec_getOutputBuffer included padding after the output buffer leading to potential confusion. Now the size returned from both AMediaCodec_getOutputBuffer and AMediaCodec_dequeueOutputBuffer is correct. Also removed mentions of non-existing NDK methods AMediaCodec_getOutputBuffers and AMediaCodec_getInputBuffers. Bug: 301470262 Flag: EXEMPT bugfix (cherry picked from commit d69fe7b73a0ed14c2b5bc237f1a42314140c9458) Merged-in: I6bbd9b85023aef56a608362afde0662d3df7284a (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0e8d99cb7893e23a6a941379bca31455ea068fc8) Merged-In: I6bbd9b85023aef56a608362afde0662d3df7284a Change-Id: I6bbd9b85023aef56a608362afde0662d3df7284a