- Feb 23, 2017
-
-
Sebastian Dröge authored
-
- Feb 07, 2017
-
-
Reduce frame num gaps so that we don't have to create unnecessary dummy pictures, just throw them away. Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=777506
-
- Feb 01, 2017
-
-
Hyunjun Ko authored
A value of width/height property should be set to out caps, if negotiation had been going properly. So we can use srcpad_info when making decision of scaling. https://bugzilla.gnome.org/show_bug.cgi?id=778010
-
- Jan 30, 2017
-
-
Sebastian Dröge authored
-
- Jan 23, 2017
-
-
Use the sink caps pixel-aspect-ratio to fixate the src caps, if it is not already set. https://bugzilla.gnome.org/show_bug.cgi?id=777395
-
if the vaapipostproc is configured to not do deinterlacing, the interlace-mode in the src caps should be the same as the input caps. https://bugzilla.gnome.org/show_bug.cgi?id=777395
-
- Jan 20, 2017
-
-
warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
-
Thus a race condition segfault is avoided. Original-patch-by: Matt Staples <staples255@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=777146
-
- Jan 10, 2017
-
-
If the frame is a cloned picture, its PTS comes from its parent picture. In addition, the base decoder doesn't set a valid PTS to the frame corresponding to the cloned picture. https://bugzilla.gnome.org/show_bug.cgi?id=774254
-
- Jan 06, 2017
-
-
If src pad caps have changed, it needs to notify it downstream. In addition, do not set passthrough if they have changed. Otherwise, transform sometimes starts processing before caps change. The passthrough value will be set in fixate later in this case. https://bugzilla.gnome.org/show_bug.cgi?id=775204
-
- Nov 29, 2016
-
-
Sebastian Dröge authored
-
- Nov 25, 2016
-
-
Removes GstVideoGLTextureUploadMeta caps feature if the driver doesn't support opengl. Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=772838
-
When the allowed source pad caps are generated, the GLTextureUpload caps are only inserted if the driver support OpenGL. https://bugzilla.gnome.org/show_bug.cgi?id=772838
-
In commit 6d11a009 were introduced a regression when gstreamer-vaapi is compiled with out EGL/GLX support: it shall not support GST_VAAPI_MAKE_GLTEXUPLOAD_CAPS. This patch guards the inclusion of GST_VAAPI_MAKE_GLTEXUPLOAD_CAPS in the allowed src caps for vaapedecode if EGL/GLX.
-
Just as vaapipostproc, VA decoder's context can be queried to get the possible raw formats, so, the src caps can negotiate the exact caps that the context supports.
-
In case libva-wayland has its headers not installed in default locations (like /usr/include), the build fails to include "wayland-client.h": CC libgstvaapi_egl_la-gstvaapiutils_egl.lo In file included from gstvaapidisplay_wayland.h:27:0, from gstvaapidisplay_egl.c:35: /usr/include/va/va_wayland.h:31:28: fatal error: wayland-client.h: No such file or directory #include <wayland-client.h> As we already passed VA_CLAGS, /usr/include/va/va_wayland.h could be found, but it is our fault not to instruct the system that we ALSO care for va_wayland. We correctly query for libva-wayland.pc in configure and use this in other places as well. It is thus only correct and consequent, to do it also at this spot. https://bugzilla.gnome.org/show_bug.cgi?id=773946
-
- Nov 17, 2016
-
-
Sebastian Dröge authored
-
- Nov 11, 2016
-
-
Hyunjun Ko authored
The thread that handles window's events should be finished during pipeline's shutdown, otherwise it will remain alive during pipeline re-activation, leading to unexpected problems. This patch fixes failures of intensive_state_change scenario of gst-validate https://bugzilla.gnome.org/show_bug.cgi?id=774241
-
- Nov 08, 2016
-
-
Víctor Manuel Jáquez Leal authored
"gst_pad_push" is not a good description of the event.
-
Hyunjun Ko authored
Returning GST_FLOW_ERROR always when gst_pad_push fails might lead to deadlock during seek. This patch returns the same error of gst_pad_push() and log out the return value. https://bugzilla.gnome.org/show_bug.cgi?id=774030
-
Víctor Manuel Jáquez Leal authored
Previously the frame map counter increased independently if the map succeeded or not. This leaded to critical messages and crashes if the frame was unable to be mapped, but the counter increased. This patch increases the map counter only if the map operation occurred. https://bugzilla.gnome.org/show_bug.cgi?id=773939
-
Víctor Manuel Jáquez Leal authored
When running gst-discoverer-1.0, in certain media, vaapipostroc is stopped meanwhile it is transforming caps. The problem is that stop() calls gst_vaapi_plugin_base_close(), which nullifies the element's va display, but the va display is used in tranform_caps() when it is extracting the possible format conversions. This display disappearing generates warning messages. This patch holds a local reference of va display at ensure_allowed_raw_caps() hence it doesn't go away meanwhile it is used, even if the gst_vaapi_plugin_base_close() is called in other thread. https://bugzilla.gnome.org/show_bug.cgi?id=773593
-
- Nov 01, 2016
-
-
Sebastian Dröge authored
-
- Oct 27, 2016
-
-
-
-
Víctor Manuel Jáquez Leal authored
Since vaapipostproc is only registered if the driver supports it, all the support for dynamic loading were removed. Though some leftovers remained. https://bugzilla.gnome.org/show_bug.cgi?id=773589
-
-
Víctor Manuel Jáquez Leal authored
In the spirit of the codec split, this patch removes the documentation of vaapidecode and adds a page per each possible decoder. Nonetheless, only those available in the compilation system are going to be instrospected, because the rest are not registered.
-
Víctor Manuel Jáquez Leal authored
-
- Oct 25, 2016
-
-
Víctor Manuel Jáquez Leal authored
Since we can have several vaapipostproc operating in a pipeline, it is useful to know which one is generating the logging message. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
vaapidecode has a member named allowed_caps, but this name is not enough explicit. This patch renames allowed_caps to allowed_sinkpad_caps. No functional changes were included. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
-
-
Víctor Manuel Jáquez Leal authored
In order to clarify the use of flag as input parameter, it is renamed to surface_alloc_flag, since it is used when creating a VA surface with certain properties. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
So encoders and decoders have similar descriptions. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
So encoder and decoders have the same codec name. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
Merge two lines of variable declarations. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Hyunjun Ko authored
GstVaapiDecode is a descendant of GstVaapiMiniObject, so, thought we should use its methods, even though it doesn't change functionality. GstVaapiPixmap, GstVaapiTexture and GstVaapiWindow are descendant of GstVaapiObject, hence its methods shall be used. https://bugzilla.gnome.org/show_bug.cgi?id=772554
-
- Oct 19, 2016
-
-
Julien Isorce authored
In short GstFdMemory is configured to call close when using GstDmabufMemory. https://bugzilla.gnome.org/show_bug.cgi?id=755072
-
Víctor Manuel Jáquez Leal authored
-