summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2017-08-17Automatic update of common submodule1.10Tim-Philipp Müller1-0/+0
From f49c55e to 742c09d
2017-07-17libs: encoder: vp9: array terminated in zerosVíctor Manuel Jáquez Leal1-1/+2
There is a crash when setting ref-pic-mode since the #GEnumValue array is not terminated with a structured with all memvers being zero. https://bugzilla.gnome.org/show_bug.cgi?id=785032
2017-07-17vaapipostproc: set multivew-mode flags to src capsHyunjun Ko1-0/+25
vaapipostproc didn't negotiate the proper multiview caps losing downstream information. This patch enables the playing of MVC encoded stream by setting the proper multiview mode/flags and views to src caps, according to sink caps. https://bugzilla.gnome.org/show_bug.cgi?id=784320
2017-06-15Release 1.10.51.10.5Sebastian Dröge5-10/+231
2017-05-12vaapisink: keep handle_events flag except that if user want to setHyunjun Ko1-1/+1
When state of vaapisink is changed from PLAYING to NULL, the handle_events flag is set to FALSE, and never recovered, and then event thread is never going to run. So we should allow to set the flag only when users try it. https://bugzilla.gnome.org/show_bug.cgi?id=782543
2017-05-12plugins: remove par from caps negotiationVíctor Manuel Jáquez Leal1-2/+1
https://bugzilla.gnome.org/show_bug.cgi?id=781759
2017-04-27plugins: handle pixel-aspect-ratio with value 0/1Víctor Manuel Jáquez Leal2-0/+4
When downstream negotiates a pixel-aspect-ratio of 0/1, the calculations for resizing and formatting in vaapipostproc and vaapisink, respectively, failed, and thus the pipeline. This patch handles this situation by converting p-a-r of 0/1 to 1/1. This is how other sinks, such as glimagesink, work.
2017-04-27vaapivideobufferpool: fix leak of created allocatorHyunjun Ko1-0/+1
Since it's created by itself, it should be unref-counted after gst_buffer_pool_config_set_allocator call. Afterwards, this allocator will be ref-counted again when assigning to priv->allocator. https://bugzilla.gnome.org/show_bug.cgi?id=781577
2017-04-25vaapivideobufferpool: create or reconfig allocatorVíctor Manuel Jáquez Leal1-0/+21
Sometimes a video decoder could set different buffer pool configurations, because their frame size changes. In this case we did not reconfigure the allocator. This patch enables this use case, creating a new allocator inside the VAAPI buffer pool if the caps changed, if it is not dmabuf-based. If so, it is just reconfigured, since it doesn't have a surface pool. https://bugzilla.gnome.org/show_bug.cgi?id=781577
2017-04-06libs: encoder: vp9: Fix initialization of ref_listScott D Phillips1-1/+2
gcc 7.0.1 gives a memset-elt-size warning in gst_vaapi_encoder_vp9_init: 'memset' used with length equal to number of elements without multiplication by element size [-Werror=memset-elt-size] https://bugzilla.gnome.org/show_bug.cgi?id=780947
2017-03-31encoder: h264: Fix Backward ReferencePicture flag settingSreerenj Balachandran1-1/+2
This is a regression introduced by e829b62 which override the reference flags and caused issues with latest intel-vaapi-driver.
2017-03-28encoder: h264: Fix B frame encoding artifactsSreerenj Balachandran1-0/+14
The current implementation is updating the POC values only in Slice parameter Buffer.But we are not filling the picture order count and reference flags in VAPictureH264 while populating VA Picture/Slice structures.The latest intel-vaapi-driver is directly accessing the above fields from VAPicutreH264 provided as RefPicLists, which resulted some wrong maths and prediction errors in driver. https://bugzilla.gnome.org/show_bug.cgi?id=780620
2017-03-21meson.build: update versionMathieu Duponchelle1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-03-21make: remove gstvaapiversion.h generationScott D Phillips4-80/+1
https://bugzilla.gnome.org/show_bug.cgi?id=778250 https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-03-21meson: gstreamer-codecparsers is a required depTim-Philipp Müller1-1/+1
Just like in configure.ac. https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-03-21vaapi: add meson buildScott D Phillips8-0/+441
https://bugzilla.gnome.org/show_bug.cgi?id=778250 https://bugzilla.gnome.org/show_bug.cgi?id=780363
2017-03-14docs: h264/h265: put parser to the example pipelineHyunjun Ko2-2/+2
https://bugzilla.gnome.org/show_bug.cgi?id=778749
2017-03-14libs: encoder: h265: fix reserved length of bitsHyunjun Ko1-2/+2
Fix reserved length of bits for bit_depth_luma_minus8 and bit_depth_chroma_minus8 https://bugzilla.gnome.org/show_bug.cgi?id=778749
2017-03-14O_CLOEXEC needs _GNU_SOURCE definedThomas Petazzoni2-0/+2
From man open(2): The O_CLOEXEC, O_DIRECTORY, and O_NOFOLLOW flags are not specified in POSIX.1-2001, but are specified in POSIX.1-2008. Since glibc 2.12, one can obtain their definitions by defining either _POSIX_C_SOURCE with a value greater than or equal to 200809L or _XOPEN_SOURCE with a value greater than or equal to 700. In glibc 2.11 and earlier, one obtains the definitions by defining _GNU_SOURCE. And indeed, with the uClibc C library, O_CLOEXEC is not exposed if _GNU_SOURCE is not defined. Therefore, this commit fixes the build of gstreamer-vaapi with the uClibc C library. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> https://bugzilla.gnome.org/show_bug.cgi?id=779953
2017-03-14README: fix "Sources" sectionVíctor Manuel Jáquez Leal1-1/+1
Update the URL where the release source tarballs can be downloaded.
2017-03-14README: fix "Reporting bugs" sectionThomas Petazzoni1-4/+1
The "Reporting bugs" section gives https://bugzilla.gnome.org/enter_bug.cgi?product=gstreamer-vaapi as the link to report a bug, but this link says "Sorry, entering a bug into the product gstreamer-vaapi has been disabled.". This commit fixes the URL to point to the proper location, and also removes the following paragraph that is no longer correct. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> https://bugzilla.gnome.org/show_bug.cgi?id=779954
2017-03-02configure: Add missing compiler flagsSreerenj Balachandran1-14/+12
The AC_CHECK_HEADERS macro was failing to locate some headers, in particular the va_enc_* headers due to missing compiler flags. https://bugzilla.gnome.org/show_bug.cgi?id=779101 Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
2017-02-23Release 1.10.41.10.4Sebastian Dröge4-10/+75
2017-02-07libs: decoder: h264: reduce frame number of gapsHyunjun Ko1-2/+15
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
2017-02-01vaapipostproc: set GST_VAAPI_POSTPROC_FLAG_SIZE according to src capsHyunjun Ko1-3/+5
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
2017-01-30Release 1.10.31.10.3Sebastian Dröge4-14/+109
2017-01-23vaapipostproc: use sink caps par if not requestedVíctor Manuel Jáquez Leal1-3/+3
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
2017-01-23vaapipostproc: set interlace modeVíctor Manuel Jáquez Leal2-1/+31
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
2017-01-20vaapisink: fix gcc compiler warningVíctor Manuel Jáquez Leal1-2/+2
warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
2017-01-20vaapisink: don't use member variable outside lockVíctor Manuel Jáquez Leal1-6/+16
Thus a race condition segfault is avoided. Original-patch-by: Matt Staples <staples255@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=777146
2017-01-10libs: decoder: h264: don't update cloned attributesHyunjun Ko1-4/+11
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
2017-01-06vaapipostproc: notify if src pad caps changedHyunjun Ko1-6/+15
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
2016-11-29Release 1.10.21.10.2Sebastian Dröge4-9/+106
2016-11-25vaapipostproc: GLTextureUpload if driver supports OpenGLJulien Isorce1-1/+11
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
2016-11-25vaapidecode: GLTextureUpload if driver supports OpenGLVíctor Manuel Jáquez Leal1-8/+6
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
2016-11-25vaapidecode: guard GST_VAAPI_MAKE_GLTEXUPLOAD_CAPSVíctor Manuel Jáquez Leal1-2/+5
In commit 6d11a00 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.
2016-11-25vaapidecode: generate source pad capsVíctor Manuel Jáquez Leal2-4/+53
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.
2016-11-25build: add LIBVA_WAYLAND_CFLAGS to libgstvaapieglDominique Leuenberger1-0/+1
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
2016-11-17Release 1.10.11.10.1Sebastian Dröge4-11/+104
2016-11-11vaapisink: finish event thread at stop()Hyunjun Ko1-2/+1
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
2016-11-08vaapipostproc: enhance debug messageVíctor Manuel Jáquez Leal1-2/+2
"gst_pad_push" is not a good description of the event.
2016-11-08postproc: honor gst_pad_push() return valueHyunjun Ko1-6/+6
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
2016-11-08vaapivideomemory: increment map counter only if succeededVíctor Manuel Jáquez Leal1-1/+2
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
2016-11-08plugins: ensure display when getting raw capsVíctor Manuel Jáquez Leal1-4/+6
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
2016-11-01Release 1.10.01.10.0Sebastian Dröge4-10/+1309
2016-10-27vaapidecodebin: resurrect disable-vpp propertyVíctor Manuel Jáquez Leal1-17/+15
https://bugzilla.gnome.org/show_bug.cgi?id=773589
2016-10-27vaapidecodebin: name the internal queueVíctor Manuel Jáquez Leal1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=773589
2016-10-27vaapidecodebin: remove unused variablesVíctor Manuel Jáquez Leal2-9/+0
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
2016-10-27docs: document environment variablesVíctor Manuel Jáquez Leal3-1/+74
https://bugzilla.gnome.org/show_bug.cgi?id=773544
2016-10-27docs: replace vaapidecode with each codecVíctor Manuel Jáquez Leal6-60/+346
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-25 10:52:07 +0000