- Sep 16, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Sep 03, 2018
-
-
In gst_vaapidecode_handle_frame, when there is a decode error there is a code path the returns an uninitialized value. Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=797006
-
- Aug 31, 2018
-
-
Víctor Manuel Jáquez Leal authored
When running several vaapi elements at the concurrently, at initialization, there is a race condition when extractin the avaible formats for images and subpictures. This patch add a lock when the those arrays are filled. https://bugzilla.gnome.org/show_bug.cgi?id=797039
-
- Aug 16, 2018
-
-
Nicolas Dufresne authored
-
- Jul 20, 2018
-
-
Tim-Philipp Müller authored
WARNING: Passed invalid keyword argument "rqeuired". gst-libs/gst/base/meson.build:11: WARNING: Passed invalid keyword argument "version". gst-libs/gst/base/meson.build:11: WARNING: Passed invalid keyword argument "soversion". gst-libs/gst/vaapi/meson.build:223: WARNING: Passed invalid keyword argument "version". gst-libs/gst/vaapi/meson.build:223: WARNING: Passed invalid keyword argument "soversion".
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Jun 13, 2018
-
-
Víctor Manuel Jáquez Leal authored
We have neglected to update this code since GstVaapiDisplay turned into a GstObject descendant. https://bugzilla.gnome.org/show_bug.cgi?id=796470
-
- Jun 07, 2018
-
-
Víctor Manuel Jáquez Leal authored
The previous behavior when selecting a profile was to select the best one in the intersection of allowed, in the pipelne, and available (by the hardware). This was changed in commit 1f1e9eef to choose the first one at fixate. Nonetheless, it's a bad idea change the behavior on a stable release. Thus, this patch selects the best profile in the intersected caps as before.
-
Víctor Manuel Jáquez Leal authored
-
- Jun 06, 2018
-
-
Víctor Manuel Jáquez Leal authored
This is, practically, a revert of commit dcf135e2. The parent logic is useful for the EGL display, which is a decorator of the real windowing subsystem (X11 or Wayland). Thus it is avoided calling vaInitialize() and vaTerminate() twice.
-
Víctor Manuel Jáquez Leal authored
Statically initialise the internal params structure.
-
-
gst_vaapi_display_egl_new_with_native_display has been broken since no one uses it. Currently it needs to call this api to create display with provided EGL display so that it could avoid duplicated calls for the native display (eg. eglTerminate). https://bugzilla.gnome.org/show_bug.cgi?id=795391
-
Víctor Manuel Jáquez Leal authored
-
Víctor Manuel Jáquez Leal authored
The commit 67e33d3d ("vaapiencode: h264: find best profile in those available") changed the code to pick a profile that is actually supported by the hardware. Unfortunately it dropped the downstream constraints. This can cause negotiation failures under certain circumstances. The fix is split in two cases: 1\ the available VA-API caps doesn't intersect with pipeline's allowed caps: * The best allowed profile (pipeline's caps) is set as the encoding target profile (it will be adjusted later by the available profiles and properties) 2\ the available VA-API caps does intersect with pipeline's allowed caps: * The intersected caps are fixed, and its profile is set as the encoding target profile. In this case the is not the best profile, but the minimal one (if VA-API reports the profiles in order). Setting the minimal profile of the intersected caps is better for compatibility. This patch fixes other tests related with caps negotiation, for example, it handles baseline profile, even when VA only supports constrained-baseline. Original-patch-by: Michael Olbrich <m.olbrich@pengutronix.de> https://bugzilla.gnome.org/show_bug.cgi?id=794306
-
- Jun 04, 2018
-
-
The specification says, "log2_max_pic_order_cnt_lsb_minus4 shall be in the range of 0 to 12, inclusive." This patch changes the upper limit from 6 to 12. https://bugzilla.gnome.org/show_bug.cgi?id=796179
-
- May 21, 2018
-
-
Víctor Manuel Jáquez Leal authored
-
- May 17, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Apr 27, 2018
-
-
Víctor Manuel Jáquez Leal authored
Instead of using our own context handling for looking for GstGL parameters (display, context and other context), this patch changes the logic to use the utility function offered by GstGL. https://bugzilla.gnome.org/show_bug.cgi?id=793643
-
Víctor Manuel Jáquez Leal authored
This commit basically is a revert of commits 80925377 and fc1c4155 https://bugzilla.gnome.org/show_bug.cgi?id=793643
-
The parameters of gst_gl_ensure_element_data() have to be not local variable since they are going to be used to see if they're set in gst_element_set_context() inside the API. This is basically a revert of commit 3d56306c https://bugzilla.gnome.org/show_bug.cgi?id=793643
-
- Apr 26, 2018
-
-
Víctor Manuel Jáquez Leal authored
1. The macro in the code is USE_GLES_VERSION_MASK 2. glesv3 is provided by glesv2 pkg-config, then it's required to check headers 3. fix syntax error https://bugzilla.gnome.org/show_bug.cgi?id=795391
-
The returning egl context may be null, so we should check the return value. https://bugzilla.gnome.org/show_bug.cgi?id=795391
-
- Apr 25, 2018
-
-
Víctor Manuel Jáquez Leal authored
Include gl.h for the required GstGL symbols. https://bugzilla.gnome.org/show_bug.cgi?id=795391
-
- Apr 18, 2018
-
-
Otherwise the following poll may not return for an arbitrary amount of time. This can happen if another wayland event queue has flushed and read our events. https://bugzilla.gnome.org/show_bug.cgi?id=795224
-
- Apr 05, 2018
-
-
Víctor Manuel Jáquez Leal authored
Instead to look for the best profile in the allowed profiles by downstream, the encoder should look for the base profile in the available profile in VA-API. https://bugzilla.gnome.org/show_bug.cgi?id=794306
-
- Mar 19, 2018
-
-
Tim-Philipp Müller authored
-
- Mar 16, 2018
-
-
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
-
- Mar 13, 2018
- Mar 03, 2018
- Mar 01, 2018
-
-
Víctor Manuel Jáquez Leal authored
Instead of copying the metada in prepare_output_buffer() vmethod, it is done in append_output_buffer_metadata() thus deinterlaced buffers could also have the proper metas. GstVideoCropMeta now it is copied internally and it is decided via transform_meta() vmethod. A new internal method, copy_metadata() was added to handle VPP transformation where non-GstVideoVaapiMeta metas were lost.
-
- Feb 27, 2018
-
-
Nicolas Dufresne authored
This will ensure that meta data without memory tags will be copied. This was noticed when testing ROI. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-
Rewrote the ROI test to use GstVideoRegionOfInterest meta rather than injecting GstEvents. These meta are added as a pad probe in the queue src pad. Also * Use of navigation messages to control de test * Use signal watch for processing messages * Change to H265 rather than H264 since current intel-vaapi-driver only supports ROI on kabylake. TODO: add a parameter to change the encoder/decoder to test. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-
Check input buffers for ROI metas and pass them to VA. Also added a new "default-roi-delta-qp" property in order to tell the encoder what delta QP should be applied to ROI by default. Enabled it for H264 and H265 encoders. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-
This reverts commit 7a6f6903. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-
This reverts commit c21345c4. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-
This reverts commit 8f1b88da. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-