diff options
| author | 2016-06-28 15:47:55 -0700 | |
|---|---|---|
| committer | 2016-06-28 15:50:21 -0700 | |
| commit | 024005e5e405a781d2e9d2c5d58e6400526ef202 (patch) | |
| tree | baacff6a6bf6374bfcd278613e5a056b188f1700 | |
| parent | a1df385e7438f163ed582a484d74a0a75e6d6847 (diff) | |
media: clarify notes in MediaCodec doc
Bug: 23709311
Change-Id: I4af683a8f43db29fa5a777832a659a6c43a7a8d1
| -rw-r--r-- | media/java/android/media/MediaCodec.java | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/media/java/android/media/MediaCodec.java b/media/java/android/media/MediaCodec.java index 542dcedb007c..264944f43bae 100644 --- a/media/java/android/media/MediaCodec.java +++ b/media/java/android/media/MediaCodec.java @@ -133,9 +133,10 @@ import java.util.Map; <p class=note> Note that on some devices the slice-height is advertised as 0. This could mean either that the slice-height is the same as the frame height, or that the slice-height is the frame height - aligned to some value (usually a power of 2). Unfortunately, there is no way to tell the actual - slice height in this case. Furthermore, the vertical stride of the {@code U} plane in planar - formats is also not specified or defined, though usually it is half of the slice height. + aligned to some value (usually a power of 2). Unfortunately, there is no standard and simple way + to tell the actual slice height in this case. Furthermore, the vertical stride of the {@code U} + plane in planar formats is also not specified or defined, though usually it is half of the slice + height. <p> The {@link MediaFormat#KEY_WIDTH} and {@link MediaFormat#KEY_HEIGHT} keys specify the size of the video frames; however, for most encondings the video (picture) only occupies a portion of the @@ -620,8 +621,9 @@ import java.util.Map; mode} will be automatically applied with one exception: <p class=note> Prior to the {@link android.os.Build.VERSION_CODES#M} release, software decoders may not - have applied the rotation when being rendered onto a Surface. Unfortunately, there is no way to - identify software decoders, or if they apply the rotation other than by trying it out. + have applied the rotation when being rendered onto a Surface. Unfortunately, there is no standard + and simple way to identify software decoders, or if they apply the rotation other than by trying + it out. <p> There are also some caveats. <p class=note> |