Pepper VideoDecoder API definition.

ppapi/api/pp_media_codec.idl

+/* Copyright (c) 2014 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.
+ */
+
+/**
+ * Video decoder profiles.
+ */
+enum PP_MediaCodec_Profile {

[Ami GONE FROM CHROMIUM, 2014/04/09 22:12:41]

"MediaCodec" implies to me these values would match Android's MediaCodec, not
chromium's profile num.

[bbudge, 2014/04/11 17:15:16]

I'm open to naming suggestions :)
I'm using MediaCodec as a prefix in this API with the idea that it will help
group things better if we add an encoding API, or Audio APIs later.

+  PP_MEDIACODEC_H264PROFILE_BASELINE = 0,
+  PP_MEDIACODEC_H264PROFILE_MAIN = 1,
+  PP_MEDIACODEC_H264PROFILE_EXTENDED = 2,
+  PP_MEDIACODEC_H264PROFILE_HIGH = 3,
+  PP_MEDIACODEC_H264PROFILE_HIGH10PROFILE = 4,
+  PP_MEDIACODEC_H264PROFILE_HIGH422PROFILE = 5,
+  PP_MEDIACODEC_H264PROFILE_HIGH444PREDICTIVEPROFILE = 6,
+  PP_MEDIACODEC_H264PROFILE_SCALABLEBASELINE = 7,
+  PP_MEDIACODEC_H264PROFILE_SCALABLEHIGH = 8,
+  PP_MEDIACODEC_H264PROFILE_STEREOHIGH = 9,
+  PP_MEDIACODEC_H264PROFILE_MULTIVIEWHIGH = 10,
+  PP_MEDIACODEC_VP8PROFILE_MAIN = 11,
+  PP_MEDIACODEC_VP9PROFILE_MAIN = 12,
+  PP_MEDIACODEC_PROFILE_MAX = PP_MEDIACODEC_VP9PROFILE_MAIN
+};
+
+/**
+ * Struct describing a video bitstream buffer. This struct is read-only and
+ * should not be modified by the plugin.

[dmichael (off chromium), 2014/04/09 21:54:07]

So this comment only refers to the struct, but the plugin can write to the data
addr references?

Not sure if there's a better way to word that.

[bbudge, 2014/04/11 17:15:16]

Eliminated this struct.

+ */
+struct PP_MediaCodec_BitstreamBuffer {
+  /**
+   * Buffer id. This can be used by the plugin to match bitstream buffers sent
+   * to the decoder with picture buffers received from the decoder.
+   */
+  int32_t buffer_id;
+
+  /**
+   * Size of buffer in bytes.
+   */
+  uint32_t size;
+
+  /**
+   * Pointer to buffer data. The plugin can safely write to the address range
+   * [addr, addr + size - 1].
+   */
+  mem_t addr;
+};
+
+/**
+ * Struct describing a decoded video picture. The decoded picture data from the
+ * bitstream buffer corresponding to |buffer_id| is stored in the GL texture
+ * corresponding to |texture_id|. This struct is read-only and should not be
+ * modified by the plugin.
+ */
+struct PP_MediaCodec_PictureBuffer {
+  /**
+   * Identifier of the last bitstream buffer which decoded into this picture.
+   */
+  int32_t buffer_id;
+
+  /**
+   * Texture ID in the plugin's GL context. The plugin can use this to render
+   * the decoded picture.
+   */
+  uint32_t texture_id;
+
+  /**
+   * The type of GL texture used to hold the decoded picture. The possible
+   * values are:
+   *   GL_TEXTURE_2D
+   *   GL_TEXTURE_RECTANGLE_ARB
+   */
+  uint32_t texture_target;
+
+  /**
+   * Dimensions of the texture holding the decoded picture.

[Ami GONE FROM CHROMIUM, 2014/04/09 22:12:41]

Elsewhere (cf. media::VideoFrame) it's been important to keep other data such as
visible rect (for cropping), coded rect (for padding/alignment), and natural
size (for aspect ratio).  I don't know if you want to track any of that here.

[bbudge, 2014/04/11 17:15:16]

I'm not sure where that information would come from. The decoder only gives us a
media::Picture.

+   */
+  PP_Size texture_size;
+};