Hello community,
here is the log from the commit of package gstreamer-plugins-vaapi for
openSUSE:Factory checked in at 2018-03-24 16:15:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/gstreamer-plugins-vaapi (Old)
and /work/SRC/openSUSE:Factory/.gstreamer-plugins-vaapi.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "gstreamer-plugins-vaapi"
Sat Mar 24 16:15:41 2018 rev:25 rq:590335 version:1.12.4
Changes:
--------
---
/work/SRC/openSUSE:Factory/gstreamer-plugins-vaapi/gstreamer-plugins-vaapi.changes
2018-03-22 12:10:03.175058536 +0100
+++
/work/SRC/openSUSE:Factory/.gstreamer-plugins-vaapi.new/gstreamer-plugins-vaapi.changes
2018-03-24 16:15:57.614242799 +0100
@@ -1,0 +2,10 @@
+Wed Mar 21 19:23:10 UTC 2018 - [email protected]
+
+- Add gst-vaapi-h264-ensure-num_ref_frames-greater-0.patch: libs:
+ decoder: h264: ensure num_ref_frames is greater than 0. Even if
+ it is the h264parse fault or bad video file, vaapih264dec should
+ set a proper value for
+ VAPictureParameterBufferH264.num_ref_frames as the driver might
+ use it (bgo#793836).
+
+-------------------------------------------------------------------
New:
----
gst-vaapi-h264-ensure-num_ref_frames-greater-0.patch
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ gstreamer-plugins-vaapi.spec ++++++
--- /var/tmp/diff_new_pack.psxE1l/_old 2018-03-24 16:15:58.690204014 +0100
+++ /var/tmp/diff_new_pack.psxE1l/_new 2018-03-24 16:15:58.694203869 +0100
@@ -39,6 +39,8 @@
Patch4: gst-vaapi-vaapipostproc-set-discont-flag.patch
# PATCH-FIX-UPSTREAM gst-vaapi-vaapivideobufferpool-fix-regression.patch
[email protected]
Patch5: gst-vaapi-vaapivideobufferpool-fix-regression.patch
+# PATCH-FIX-UPSTREAM gst-vaapi-h264-ensure-num_ref_frames-greater-0.patch
[email protected]
+Patch6: gst-vaapi-h264-ensure-num_ref_frames-greater-0.patch
BuildRequires: Mesa-devel
BuildRequires: Mesa-libGLESv3-devel
++++++ gst-vaapi-h264-ensure-num_ref_frames-greater-0.patch ++++++
>From 9a130035e52a49e6804ff33eb399ea5f6be5c773 Mon Sep 17 00:00:00 2001
From: Julien Isorce <[email protected]>
Date: Mon, 12 Mar 2018 16:59:01 +0000
Subject: libs: decoder: h264: ensure num_ref_frames is greater than 0
Even if it is the h264parse fault or bad video file, vaapih264dec
should set a proper value for VAPictureParameterBufferH264.num_ref_frames
as the driver might use it.
Also see "info.ref_frames = dpb_size;" in
gstvaapidecoder_h264.c::ensure_context
https://bugzilla.gnome.org/show_bug.cgi?id=793836
---
gst-libs/gst/vaapi/gstvaapidecoder_h264.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gst-libs/gst/vaapi/gstvaapidecoder_h264.c
b/gst-libs/gst/vaapi/gstvaapidecoder_h264.c
index ae644c6..165f0ee 100644
--- a/gst-libs/gst/vaapi/gstvaapidecoder_h264.c
+++ b/gst-libs/gst/vaapi/gstvaapidecoder_h264.c
@@ -3781,6 +3781,9 @@ fill_picture (GstVaapiDecoderH264 * decoder,
GstVaapiPictureH264 * picture)
COPY_FIELD (sps, bit_depth_luma_minus8);
COPY_FIELD (sps, bit_depth_chroma_minus8);
COPY_FIELD (sps, num_ref_frames);
+ if (pic_param->num_ref_frames == 0)
+ pic_param->num_ref_frames = priv->dpb_size;
+
#if !VA_CHECK_VERSION(1,0,0)
/* Deprecate H.264 baseline profile and FMO support */
COPY_FIELD (pps, num_slice_groups_minus1);
--
cgit v1.1
