summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAustin Yuan <shengquan.yuan@intel.com>2013-06-05 09:58:02 +0800
committerGwenole Beauchesne <gwenole.beauchesne@intel.com>2013-08-27 11:16:44 +0200
commit61a384af1e8763903aa0c519b43a1f09dfb5178a (patch)
treeceda9a53a8960851e0a853457bb0bbbf4b198209
parent0af50e13eaaa3b386bb3e70d94bc329d3be5737b (diff)
downloadlibva-61a384af1e8763903aa0c519b43a1f09dfb5178a.tar.gz
va.h:Add new VAConfigAttribEncAutoReference
Encoder usually has better knowledge about which reference frame are the best one than application. This attribute is used to signal application that driver has this capability, and application doesn't need to worry about reference frame settings Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
-rw-r--r--va/va.h14
1 files changed, 14 insertions, 0 deletions
diff --git a/va/va.h b/va/va.h
index dddb54d..23fafec 100644
--- a/va/va.h
+++ b/va/va.h
@@ -403,6 +403,20 @@ typedef enum
*/
VAConfigAttribEncMacroblockInfo = 16,
/**
+ * \brief Auto reference frame management. Read-only
+ *
+ * This attribute determines whether the driver supports auto reference management
+ *
+ * If driver supports, application only needs to set scratch reference surfaces
+ * via VAPictureParameterBufferH264:ReferenceFrames. The scratch surfaces number is
+ * determined by the maximum number of RefPicList0 and RefPicList0 which can be queried from
+ * VAConfigAttribEncMaxRefFrames. Application doesn't need to set VAPictureParameterBufferH264:CurrPic
+ * and VAEncSliceParameterBufferH264:RefPicList. Driver will manage the reference frames internally
+ * and choose the best reference frames. Which scratch surface is used for reconstructed frame and which
+ * surfaces are used for reference frames will be fedback via VACodedBufferSegment
+ */
+ VAConfigAttribEncAutoReference = 17,
+ /**
* \brief Maximum picture width. Read-only.
*
* This attribute determines the maximum picture width the driver supports