Pepper: Define PPB_VideoEncoder API.

ppapi/api/pp_codecs.idl

Index: ppapi/api/pp_codecs.idl
diff --git a/ppapi/api/pp_codecs.idl b/ppapi/api/pp_codecs.idl
index 5a93ff1063f054a130ee0a797280c491138f1d5a..5a336f7e541fa9062e7959c2741c4cadd7236214 100644
--- a/ppapi/api/pp_codecs.idl
+++ b/ppapi/api/pp_codecs.idl
@@ -115,3 +115,48 @@ struct PP_VideoPicture_0_1 {
    */
   PP_Size texture_size;
 };
+
+/**
+ * Supported video profile information. See the PPB_VideoEncoder function
+ * GetSupportedProfiles() for more details.
+ */
+struct PP_SupportedVideoProfile {

[llandwerlin-old, 2015/01/26 19:25:47]

While implementing this, I figured that maybe we should indicate which profiles
are either hardware or software accelerated.

Should we add a boolean in this struct?

[bbudge, 2015/01/26 20:34:32]

That seems reasonable. VEA implements GetSupportedProfiles, but we need to
figure out how the software encoder stuff in Chromium can implement the same
thing.

[bbudge, 2015/01/27 00:17:22]

Instead of a PP_Bool, I added a PP_HardwareAcceleration value, to convey
whether the profile is available in HW, SW, or both.

+  // The codec profile.
+  PP_VideoProfile profile;
+
+  /**
+   * Dimensions of the maximum resolution of video frames, in pixels.
+   */
+  PP_Size max_resolution;
+
+  /**
+   * The numerator of the maximum frame rate.
+   */
+  uint32_t max_framerate_numerator;
+
+  /**
+   * The denominator of the maximum frame rate.
+   */
+  uint32_t max_framerate_denominator;
+};
+
+/**
+ * Struct describing a bitstream buffer.
+ */
+struct PP_BitstreamBuffer {
+  /**
+   * The size, in bytes, of the bitstream data.
+   */
+  uint32_t size;
+
+  /**
+   * The base address of the bitstream data.
+   */
+  mem_t buffer;
+
+  /**
+   * Whether the buffer represents a key frame.
+   */
+  PP_Bool key_frame;
+};
+