From 8aa735f71e8921b93f2bb6fa5506d8ff414698a0 Mon Sep 17 00:00:00 2001 From: Andreas Huber Date: Tue, 8 May 2012 11:33:12 -0700 Subject: [PATCH] Clarification of MediaCodec behaviour when codec specific data is included in the format passed to configure(). Change-Id: I150f52e8092c0f7d897891f02ba6b1d89b6230f4 related-to-bug: 6364139 --- media/java/android/media/MediaCodec.java | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/media/java/android/media/MediaCodec.java b/media/java/android/media/MediaCodec.java index 1dbd48ef109d4..2debd57df82dc 100644 --- a/media/java/android/media/MediaCodec.java +++ b/media/java/android/media/MediaCodec.java @@ -94,6 +94,11 @@ import java.util.Map; * be codec specific data marked as such using the flag {@link #BUFFER_FLAG_CODEC_CONFIG} * in a call to {@link #queueInputBuffer}. * + * Codec specific data included in the format passed to {@link #configure} + * (in ByteBuffer entries with keys "csd-0", "csd-1", ...) is automatically + * submitted to the codec, this data MUST NOT be submitted explicitly by the + * client. + * * Once the client reaches the end of the input data it signals the end of * the input stream by specifying a flag of {@link #BUFFER_FLAG_END_OF_STREAM} in the call to * {@link #queueInputBuffer}. The codec will continue to return output buffers