- Sep 01, 2016
-
-
Sebastian Dröge authored
-
- Aug 16, 2016
-
-
Interlaced video is as yet unsupported in the vc1 element. Print an error to make that more obvious. https://bugzilla.gnome.org/show_bug.cgi?id=769250
-
- Aug 10, 2016
-
-
Víctor Manuel Jáquez Leal authored
Commit 4259d1ae introduced this compilation error. This patch fixes it.
-
Víctor Manuel Jáquez Leal authored
Use gst_util_uint64_scale() to calculate bitrate instead of normal arithmetic to avoid overflows, underflows and loss of precision. https://bugzilla.gnome.org/show_bug.cgi?id=768458
-
Víctor Manuel Jáquez Leal authored
Validate that fps numerator is non-zero so it can be used to calculate the duration of the B frame. Also it gst_util_uint64_scale() is used instead of normal arithmetic in order to aviod overflows, underflows and loss of precision. https://bugzilla.gnome.org/show_bug.cgi?id=768458
-
- Aug 06, 2016
-
-
Tim-Philipp Müller authored
Encoders claim to support a whole bunch of input formats but then just error out if the format is not actually supported, even if there's a converter in front. This means they're not fit for autoplugging in encodebin or camerabin yet and therefore should not have a rank. People can still use them in custom pipelines. https://bugzilla.gnome.org/show_bug.cgi?id=769266
-
- Jul 29, 2016
-
-
Víctor Manuel Jáquez Leal authored
Check earlier if upstream video source has activated the dmabuf-import io-mode (hack to disappear soon), thus we can avoid the re-assignation of a new allocator.
-
Víctor Manuel Jáquez Leal authored
If the frame size or format, change, the allocators are reset, so a new ones can be created with the new video info.
-
Víctor Manuel Jáquez Leal authored
If the negotiated sinkpad caps change, destroy the assignated allocator, because it is not valid anymore.
-
Víctor Manuel Jáquez Leal authored
Since they are not modified, we should mark them as const.
-
Víctor Manuel Jáquez Leal authored
Add the method gst_allocator_get_vaapi_image_size() for the GstVaapiVideoAllocator, which gets the size of the allocated images with the current video info. This method replaces the direct call to the allocator's image info when the pool is configured.
-
Hyunjun Ko authored
Depends on media, video size is sometimes updated with new allocator. It leads to dismatch between bufferpool's set size and real allocated buffer size. In this case, it causes every buffer is freed during release in bufferpool, which should be reused. This affects performance. https://bugzilla.gnome.org/show_bug.cgi?id=769248
-
- Jul 27, 2016
-
-
Víctor Manuel Jáquez Leal authored
Since commit 27429ce6, EGL support doesn't depend on dynamic loading libraries, thus the dependency to gmodule-2.0 is not mandatory anymore.
-
Scott D Phillips authored
Some invocations of PKG_CHECK_MODULES were intended to be non-fatal if the package is missing, but action-if-not-found was given as an empty string which still causes the default action to run, which halts execution. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=769237
-
- Jul 22, 2016
-
-
Víctor Manuel Jáquez Leal authored
Since the upstream of gstreamer-vaapi, the library is not a public shared object anymore. But the EGL support depended on this dynamic library, so the EGL support was broken. This patch removes the dynamic library loading code and instantiates the EGL display using either X11 or Wayland if available. https://bugzilla.gnome.org/show_bug.cgi?id=767203
-
Víctor Manuel Jáquez Leal authored
In order to register only the available decoders, this patch queries the created test VA display, which uses the currently used back-end (X11, Wayland, DRM, …) on the used display device. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
In order to register only the available encoders, this patch queries the created test VA display, which uses the currently used back-end (X11, Wayland, DRM, …) on the used display device. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
Split the vaapidecode to all the supported codecs with the format vaapi{codec}dec. vaapidecode is stil registered as a GObject type, but not as a GStreamer feature, so it can be used internally by vaapidecodebin without changing its code too much. https://bugzilla.gnome.org/show_bug.cgi?id=734093
-
Víctor Manuel Jáquez Leal authored
Since the elements dependant of the VA video processor are now only registered if it is available, vaapidecodebin code can be simplified a lot, removing all the code required to check if the VA video processor was available. https://bugzilla.gnome.org/show_bug.cgi?id=768899
-
Víctor Manuel Jáquez Leal authored
Delay the GstVaapiDisplay instantiating until when changing the state from READY to PAUSE. In this way the element has more chances to find an already created GstVaapiDisplay, or a GL context, in the pipeline. https://bugzilla.gnome.org/show_bug.cgi?id=766206
-
Víctor Manuel Jáquez Leal authored
The function gst_vaapi_create_display_from_gl_context() cretes a GstVaapiDisplay given a GstGLContext. But it didn't created a GLX VA display when the GL platform was GLX, but a plain X11 VA display. This patch fixes that, by querying the GL platform earlier. https://bugzilla.gnome.org/show_bug.cgi?id=766206
-
Víctor Manuel Jáquez Leal authored
Using the GstContext mechanism, it is possible to find if the pipeline shares a GstGLContext, even if we are not to negotiating GLTextureUpload meta. This is interesting because we could negotiate system memory caps feature, but enable DMABuf if the GstGLContext is EGL with some extensions. https://bugzilla.gnome.org/show_bug.cgi?id=766206
-
Víctor Manuel Jáquez Leal authored
Since nobody is calling gst_vaapi_plugin_base_driver_is_whitelisted(), it is deleted.
-
Víctor Manuel Jáquez Leal authored
Remove the common change_state() vmethod for all the plugins, since no one is using it.
-
Víctor Manuel Jáquez Leal authored
Since the driver checkup is done at registering, there is no need to do it when changing the element state from NULL to READY. This patch remove this vmethod from vaapidecode.
-
Víctor Manuel Jáquez Leal authored
Query the GstVaapiDisplay to know if the driver supports video postprocessing. If does, then register vaapipostproc and vaapidecodebin elements. This patch will simplify the design of vaapidecodebin. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
Using the test VA display, the driver name is queried, and if it is not white-listed, the plugin rejects to register any element. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
Move some of the logic in gst_vaapi_plugin_base_driver_is_whitelisted() to a new function gst_vaapi_driver_is_whitelisted(), in this way, it can be used when registering the plugin's feature set with the test VA display. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
This patch tries to instantiate a GstVaapiDisplay when registering the plugin features, if it fails, no gstreamer-vaapi element is registering. The purpose of this patch is to avoid a situation where the user has gstreamer-vaapi installed but their VA-API setup is not functional, which may lead to unexpected behavior. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
There are two main external dependencies that define the feature set of this plugin: a) the kernel and b) the VA driver This patch tracks both dependencies, if any of them change, GStreamer will re-inspect the plugin. The kernel is tracked through the device files /dev/dri/card* The VA driver is tracked through the files VA_DRIVERS_PATH/*_drv_video.so, where VA_DRIVERS_PATH is the one defined in libva package configuration. Also, the environment variables LIBVA_DRIVERS_PATH and LIBVA_DRIVER_NAME are tracked since they modify the driver lookup. Additionally, the environment variable GST_VAAPI_ALL_DRIVERS is tracked too. https://bugzilla.gnome.org/show_bug.cgi?id=724352
-
Víctor Manuel Jáquez Leal authored
GObject's memory is set to zero, so there is no need to initialize to zero or NULL it's class variables.
-
Víctor Manuel Jáquez Leal authored
-
Víctor Manuel Jáquez Leal authored
This reverts commit 1dbcc8a0 and commit 372a03a9. While the dmabuf handle is exported, the derive image must exist, otherwise the image's VA buffer is invalid, thus the dmabuf handle is never released, leading into a file descriptors leak.
-
Víctor Manuel Jáquez Leal authored
-
Víctor Manuel Jáquez Leal authored
This is a fix for a regression of previous commit, which updates the filters only when the property is set, because it is also required to update the filter when the color balance interface change its values.
-
Hyunjun Ko authored
In case that sink caps and src caps are same, and no filtering parameter set, pass-through mode is enabled. If new filtering parameter is set during playback, it makes it reconfiguring, so that pass-through mode is changed In addition, updating filter is performed during reconfiguration, if needed. https://bugzilla.gnome.org/show_bug.cgi?id=751876
-
Hyunjun Ko authored
This patch is to avoid checking filter value at every frame. https://bugzilla.gnome.org/show_bug.cgi?id=751876
-
- Jul 21, 2016
-
-
The prefix/suffix SEI nal units can appear in codec_data too which weren't handled before. Parse these SEI headers to fix the segfault. https://bugzilla.gnome.org/show_bug.cgi?id=768544
-
- Jul 15, 2016
-
-
Víctor Manuel Jáquez Leal authored
MAINTAINERCLEANFILES is defined in gtk-doc-plugins.mak, thus instead of overload it, the files should be added.
-
Sreerenj Balachandran authored
Pack the transform_8x8_mode_flag and other necessary rbsp data in packed_pps header for MVC encode. https://bugzilla.gnome.org/show_bug.cgi?id=768647
-