• R/O
  • HTTP
  • SSH
  • HTTPS

Commit

Tags
No Tags

Frequently used words (click to add to your profile)

javac++androidlinuxc#windowsobjective-ccocoa誰得qtpythonphprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer

hardware/intel/libva


Commit MetaInfo

Revision6c2765a53496384cd7f27af3935d7a2fee7e8bba (tree)
Time2012-04-08 14:14:50
AuthorGwenole Beauchesne <gwenole.beauchesne@inte...>
CommiterGwenole Beauchesne

Log Message

API: h264 decode: fix the definition of slice_data_bit_offset.

Align with the existing practice in various media stacks available
in Linux today. i.e. codec layer submits slice data that represents
the original bitstream, thus including any emulation prevent bytes.
However, the slice_data_bit_offset represents an offset relative
to the buffer that contains the NAL unit byte and the rest of the
slice with any emulation prevention bytes removed.

Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>

Change Summary

Incremental Difference

--- a/va/va.h
+++ b/va/va.h
@@ -1227,12 +1227,12 @@ typedef struct _VASliceParameterBufferH264
12271227 /**
12281228 * \brief Bit offset from NAL Header Unit to the begining of slice_data().
12291229 *
1230- * This bit offset is relative from the NAL unit byte to the first
1231- * bit of slice_data(), thus including any emulation prevention
1232- * bytes in slice_header().
1233- *
1234- * Basically, this field represents the number of bits parsed in
1235- * the slice_header() + 8 for the initial NAL unit byte.
1230+ * This bit offset is relative to and includes the NAL unit byte
1231+ * and represents the number of bits parsed in the slice_header()
1232+ * after the removal of any emulation prevention bytes in
1233+ * there. However, the slice data buffer passed to the hardware is
1234+ * the original bitstream, thus including any emulation prevention
1235+ * bytes.
12361236 */
12371237 unsigned short slice_data_bit_offset;
12381238 unsigned short first_mb_in_slice;