AndroidVDA by using Android's MediaCodec API.

content/common/gpu/media/gles2_external_texture_copier.h

Index: content/common/gpu/media/gles2_external_texture_copier.h
diff --git a/content/common/gpu/media/gles2_external_texture_copier.h b/content/common/gpu/media/gles2_external_texture_copier.h
new file mode 100644
index 0000000000000000000000000000000000000000..4050db9271585b09a91d76db0ba3a75608feda78
--- /dev/null
+++ b/content/common/gpu/media/gles2_external_texture_copier.h
@@ -0,0 +1,48 @@
+// Copyright (c) 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CONTENT_COMMON_GPU_MEDIA_GLES2_EXTERNAL_TEXTURE_COPIER_H_
+#define CONTENT_COMMON_GPU_MEDIA_GLES2_EXTERNAL_TEXTURE_COPIER_H_
+
+#include "base/basictypes.h"
+#include "ui/gl/gl_bindings.h"
+
+namespace content {
+
+// A utility class which copies the given external texture
+// (GL_TEXTURE_EXTERNAL_OES) to the target texture (GL_TEXTURE_2D) by using
+// framebuffer.
+class Gles2ExternalTextureCopier {

[Ami GONE FROM CHROMIUM, 2013/02/13 18:07:11]

What's the status of using glCopyTextureChromium?

[dwkang1, 2013/02/14 01:38:51]

I've asked it also to Gregg(gman@), and cced you, but he said
glCopyTextureChromium does not support gpu process.

Here is part of his response.
"glCopyTextureChromium is not implemented for gpu process code. Only renderer
process code. Maybe it can be refactored but it won't be called labeled as a GL
function like glCopyTextureCHROMIUM it will just be something like
GPUCopyTextureToTexture or something."
To see the whole mail, you can search for "Regarding OpenGL ES headers" in your
mail box.

Would it be okay to keep this for a while and use it once we have
GPUCopyTextureToTexture? btw, our case is somewhat different from
glCopyTextureCHROMIUM because we need to apply transfrom_matrix. What do you
think?

[Ami GONE FROM CHROMIUM, 2013/02/14 16:43:25]

I remember that thread but thought it ended w/ gman@ offering to expose the copy
helper to the GPU-process; I realize on re-reading that it was more tenuous than
that so asked a clarifying question on that thread.

If gman@ is too busy to do this then I guess we're fine landing the copier
helper here, I'd just like to avoid it if possible.

Do you know what transform_matrix comes out looking like in practice?  My
suspicion is that it is either the identity or a pure Y-flip for the decode case
(and that in fact it is only used for camera capture rotation/flip purposes,
which are inapplicable here).

[dwkang1, 2013/02/16 11:30:31]

Unfortunately, CopyTextureCHROMIUMResourceManager does not support
GL_TEXTURE_EXTERNAL_OES. I've asked this on the thread. :(

Regarding transform_matrix, it was vflip matrix when I checked with N10 and
Xoom.
https://cs.corp.google.com/#googletv/frameworks/native/libs/gui/SurfaceTextur...

I've checked rotation transform used in MediaPlayer path, but not in MediaCodec
path.
https://cs.corp.google.com/#googletv/frameworks/av/media/libstagefright/OMXCo...

+ public:
+  Gles2ExternalTextureCopier();
+  virtual ~Gles2ExternalTextureCopier();
+
+  bool Init(int32 width, int32 height);
+
+  bool Copy(GLuint source_texture_id, GLuint destination_texture_id,
+            const float transfrom_matrix[16]);
+
+ private:
+  bool SetupGraphics();
+  void RenderFrame(int32 width, int32 height, GLuint texture_id,
+                   const float transfrom_matrix[16]);
+  bool SetupFrameBuffer();
+
+  bool initialized_;
+  int32 width_;
+  int32 height_;
+  GLuint framebuffer_id_;
+  GLuint renderbuffer_id_;
+  GLuint program_;
+  GLuint position_handle_;
+  GLuint st_matrix_handle_;
+  GLuint mvp_matrix_handle_;
+  GLuint texture_handle_;
+
+  DISALLOW_COPY_AND_ASSIGN(Gles2ExternalTextureCopier);
+};
+
+}  // namespace content
+
+#endif  // CONTENT_COMMON_GPU_MEDIA_GLES2_EXTERNAL_TEXTURE_COPIER_H_