- 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
-
Víctor Manuel Jáquez Leal authored
When importing buffers to a VA-base buffer, it is required to copy the metas in the original buffer, otherwise information will be lost, such as GstVideoRegionOfInterestMeta. https://bugzilla.gnome.org/show_bug.cgi?id=768248
-
Víctor Manuel Jáquez Leal authored
According to Debian package auto-building, uintptr_t is not an unsigned long in i386 arch, raising an "incompatible pointer type" error. This patch adds a casting for compiler's satisfaction in i386.
-
- Feb 26, 2018
-
-
Enabled zero as valid value for keyframe-period property. https://bugzilla.gnome.org/show_bug.cgi?id=793829
-
- Feb 22, 2018
-
-
Víctor Manuel Jáquez Leal authored
-
- Feb 20, 2018
-
-
Víctor Manuel Jáquez Leal authored
Generate system allocated output buffers when downstream doesn't support GstVideoMeta. The VA buffer content is copied to the new output buffer, and it replaces the VA buffer. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
When downstream can't handle GstVideoMeta it is required to send system allocated buffers. The system allocated buffers are produced in prepare_output_buffer() vmethod if downstream can't handl GstVideoMeta. At transform() vmethod if the buffer is a system allocated buffer, a VA buffer is instanciated and replaces the out buffer. Later the VA buffer is copied to the system allocate buffer and it replaces the output buffer. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
This helper function aims to copy buffers with VA memory to dumb buffers, when GstVideoMeta is not available dowstream. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
This patch add the member copy_output_frame and set it TRUE when when downstream didn't request GstVideoMeta API, the caps are raw and the internal allocator is the VA-API one. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
The allocator will be required if we need to allocate a buffer to store the frame with the expected strides. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
This function will inform the element if it shall copy the generated buffer by the pool to a system allocated buffer before pushing it to downstream. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
VA-API based buffer might need a video meta because of different strides. But when donwstream doesn't support video meta we need to force the usage of video meta. Before we changed the buffer pool configuration, but actually this is a hack and we cannot rely on that for downstream. This patch add a check fo raw video caps and allocator is VA-API, then the option is enabled without changing the pool configuration. In this case the element is responsible to copy the frame to a simple buffer with the expected strides. https://bugzilla.gnome.org/show_bug.cgi?id=785054
-
Víctor Manuel Jáquez Leal authored
When deinterlacing with VPP the discont flag was not forwarded to the new created buffer. This patch sets the discont flag if input buffer has it.
-
Víctor Manuel Jáquez Leal authored
-
- Feb 19, 2018
-
-
Increased max values of periodic key frame for h26x codecs. This allow more fine tunning of encoder that in certian scenario want higher periodic key frame. For example: it doesn't want a key frame each 10 seconds but each 120 seconds. https://bugzilla.gnome.org/show_bug.cgi?id=786320
-
- Feb 15, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Feb 13, 2018
-
-
Víctor Manuel Jáquez Leal authored
vaapsink, when used with the Intel VA-API driver, tries to display surfaces with format NV12, which are handled correctly by Weston. Nonetheless, COGL cannot display YUV surfaces, making fail pipelines on mutter. This shall be solved either by COGL or by making the driver to paint RGB surfaces. In the meanwhile, let's just demote vaapisink as marginal when the Wayland environment is detected, no matter if it is Weston. https://bugzilla.gnome.org/show_bug.cgi?id=775698
-
Víctor Manuel Jáquez Leal authored
Mesa has updated its VA-API Gallium driver vendor string: https://cgit.freedesktop.org/mesa/mesa/commit/?id=5db29d62ce1fefa3f2ee6e4a4688576fde4bde4a This patch tries to cover both, the old and the new one. https://bugzilla.gnome.org/show_bug.cgi?id=793386
-