- Sep 23, 2019
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Sep 19, 2019
-
-
Multiple different scenarios could break the display thread creation and end up blocking waiting for thread o be created. Fix them all by correctly waiting for a new boolean to become valid.
-
It's not actually wrapped as we create a new EGLContext from the passed in EGLContext. As a result, the created EGLContext was never destroyed.
-
- Sep 06, 2019
-
-
The Mesa Gallium driver is poorly tested currently, leading to bad user experience for AMD users. The driver can be added back to the white list at runtime using the GST_VAAPI_ALL_DRIVERS environment variable.
-
- Sep 02, 2019
-
-
-
filter_ops and filter_formats should already have valid value when the function gst_vaapipostproc_ensure_filter_caps re-enter
-
- Aug 20, 2019
-
-
The main reason to demote the message's level is because it is not an error, it's a possible output of the trial and there's a code path that handles it. Secondly, it's very annoying when using gallium driver for radeon.
-
- Aug 07, 2019
-
-
When input frame's formate changes, vp{8,9} encoders don't reset their frame counter, hence the newly created frame could become a P-frame, leading to some major troubles (sigabrt in libdrm in case of vp9). This patch adds some frame prediction-related reset logic to the `flush' methods of GstVaapiEncoderVP8 and GstVaapiEncoderVP9 implementations.
-
Dislable passing down packed PPS and PPS to driver if driver does not want it. Fix: #168
-
Fix an use-after-release of the parser pointer in VP9 decoder.
-
This fixes a deadlock in gst_vaapiencode_change_state, which was due to srcpad's chain function was locked waiting for available buffers. Since the coded buffers in codedbuf_queue become available after sinkpad consume the encoded frames, Paused -> Ready state change leads to deadlock. Coded buffers are never consumed and marked free, hence gst_vaapiencode_handle_frame waits for available buffers and holds the stream_lock of the srcpad.
-
When enable low delay B, the reference list 1 will be same with reference list 0, so need reset the num_ref_idx_l1_active_minus1 to num_ref_idx_l0_active_minus1. Fixes: #160
-
g_assert will take no effect when glib's G_DISABLE_ASSERT macro is defined. The function inside the g_assert will take no effect and we will fail to set the correct slice number.
-
Coverity scan bug: If the function actually returns a null value, a null pointer dereference will occur. In gst_vaapi_encoder_ensure_param_roi_regions(): Return value of function which returns null is dereferenced without checking
-
- Aug 06, 2019
-
-
The decoder's surface chroma type should depend on the bit depth of VP9's parser. For 10bits VP9 stream, we need to use P10LE kind 10 bits surface as the decoder result. Fixes #155
-
https://bugzilla.gnome.org/show_bug.cgi?id=748184 has resurrected with commit 3e992d8a Since gst_vaapi_find_preferred_caps_feature() returns a color format from caps negotiation, different from the default one (NV12), the postproc enables the color transformation. But when GL_TEXTURE_UPLOAD feature is negotiated, no color transformation shall be done. Nonetheless, with commit 3e992d8a the requested format changes firstly, because there's no video sink yet, so ANY caps are negotiated; but later, when there's a video sink and a caps renegotiation, the GL_TEXTURE_UPLOAD is negotiated though the color format conversion still ongoing. It is required to reset that conversion. This patch force default color format when GL_TEXTURE_UPLOAD is selected as preferred, thus avoiding the color conversion. Fixes: #157
-
Happens if vaAcquireBufferHandle fails.
-
- May 02, 2019
-
-
Tim-Philipp Müller authored
-
- Apr 18, 2019
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Apr 15, 2019
-
-
Víctor Manuel Jáquez Leal authored
This patch fixes a regression from commit 5b1fe9c6. max_qp, in rate control configuration, appeared in libva release 2.1 (API 1.1), thus it is required to guard the VA API version. Fixes: #150
-
-
Víctor Manuel Jáquez Leal authored
libva-x11 is used for X11 applications, so it is required to build any GTK application. Later, when Wayland test is added, we should change this.
-
Víctor Manuel Jáquez Leal authored
-
string_of_va_chroma_format() gets a wrong string format description. For example, the YUV420_10BPP get a string of 0x00000100 as output. It's because VA_RT_FORMAT_xxx values are macro definitions. And STRINGIFY(VA_RT_FORMAT_xxx) will expand to its real value 0x00000XXX. To avoid the macro evaluation, it is changed to show only the color format without VA_RT_FORMAT_ prefix.
-
Víctor Manuel Jáquez Leal authored
Don't reinvent the wheel.
-
- Apr 11, 2019
-
-
When the downstream has any caps, then raw video feature will be used. At this situation, the preferred format should be chose from caps which contains "vide/x-raw" feature instead of from the fist allowed caps. Fixes #142
-
Now that tier is calculated in commit 58e74f94 (!68), ensure we fill in the general_tier_flag in the VAEncSequenceParameterBufferHEVC.
-
- Apr 10, 2019
-
-
Tim-Philipp Müller authored
-
The current manner can not recognize the correct level and always set the tier to main. Need to add frame rate check to recognize levels such as 4.1, 6.2, etc. We also add a logic to check main and high tier based on bitrate. Fixes: #145
-
media-driver currently fails to set a correct value of max_qp when min_qp is different to zero, in CBR and VBR mode, generating full quality frames, thus unexpected huge output. This patch sets max_qp to an arbitrary value to avoid this output temporary. Fixes: #144
- Apr 09, 2019
-
-
Víctor Manuel Jáquez Leal authored
Currently the minimal value for either min_qp and init_qp are 1, but VA documentation specifiy that zero is also valid and means to ignore the quantiser. The default value is not changed though to avoid behaivor changes to users.
-
x11_dep and libva_x11_dep are optional and meson ignores these dependencies even if they are added into the dependency list. This fixes the error below when libva-x11 is not avaiblabe: cc -Itests/elements/tests@elements@@test-vaapicontext@exe -Itests/elements -I../../gstreamer-vaapi/tests/elements -I. -I../../gstreamer-vaapi/ -Igst-libs -I../../gstreamer-vaapi/gst-libs -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/orc-0.4 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/libdrm -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O2 -g -fvisibility=hidden -fno-strict-aliasing -pthread -DHAVE_CONFIG_H -MD -MQ 'tests/elements/tests@elements@@test-vaapicontext@exe/test-vaapicontext.c.o' -MF 'tests/elements/tests@elements@@test-vaapicontext@exe/test-vaapicontext.c.o.d' -o 'tests/elements/tests@elements@@test-vaapicontext@exe/test-vaapicontext.c.o' -c ../../gstreamer-vaapi/tests/elements/test-vaapicontext.c ../../gstreamer-vaapi/tests/elements/test-vaapicontext.c:29:10: fatal error: va/va_x11.h: No such file or directory #include <va/va_x11.h>
-
- Apr 01, 2019
-
-
He Junyan authored
GValueArray is deprecated. Use GstValueArray instead.
-
- Mar 30, 2019
-
-
Danilo Spinella authored
-
- Mar 29, 2019
-
-
Víctor Manuel Jáquez Leal authored
-
GValueArray is deprecated. Use GstValueArray instead. gst_param_spec_array can be deserialized from command line using: vaapih264enc view-ids="<(uint)40,(uint)100>" num-views=2 While the g_param_spec_value_array() can not, and always get error: "gst_value_deserialize_g_value_array: unimplemented" Also fixed an out-of-range bug.
-
He Junyan authored
The order in gst_vaapi_enc_picture_encode when encoding one picture is not very correct. The misc parameters are set before the picture parameters. Some of the misc parameters such as ROI may change the current picture parameters. But the later setting of picture parameter will re-init all picture related parameters and clear the previous setting. The right order should be picture parameter first and then misc parameters. Signed-off-by: He Junyan <junyan.he@hotmail.com>
-