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..6b4e7692bc0b6c8f7c8b4865b69a7dbe3cf4aa47 100644
--- a/ppapi/api/pp_codecs.idl
+++ b/ppapi/api/pp_codecs.idl
@@ -115,3 +115,43 @@ 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 {
+  // 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;

[dmichael (off chromium), 2015/01/14 00:25:20]

What's the reason for specifying the framerate this way?

[bbudge, 2015/01/14 02:01:13]

That's how it's specified by media::VideoEncodeAccelerator. I think right now
denominator is always 1 but I'm guessing that won't always be true:
https://code.google.com/p/chromium/codesearch#chromium/src/media/video/video_...

+};
+
+/**
+ * Struct describing a bitstream buffer.
+ */
+struct PP_BitstreamBuffer {
+  /**
+   * The size, in bytes, of the bitstream buffer.
+   */
+  uint32_t size;
+
+  /**
+   * The base address of the bitstream buffer.
+   */
+  mem_t buffer;

[dmichael (off chromium), 2015/01/14 00:25:20]

So, you'll fill in this pointer, and it's probably shared memory? Recycle knows
which shared buffer it can reuse based on the value of |buffer|? I can't think
of a problem with it, just want to make sure I'm understanding.

[bbudge, 2015/01/14 02:01:13]

Yes. We could  add a |buffer_id| field but I left it out since it's purely an
implementation detail, with no real utility for the plugin. The buffer address
should work as a UID.

+};
+