- 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>
-
- Mar 28, 2019
-
-
Add size_changed flag to watch out resolution. if change, reset jpeg decoder's context.
-
- Mar 26, 2019
-
-
By now, this feature only support by media-driver on Ice Lake platform, more information you can reference: https://github.com/intel/media-driver
-
- Mar 25, 2019
-
-
The vaapi internal encoder's property id are negative, thus they are different from GObject's property ids. gst_vaapi_encoder_set_property() should map to the internal encoder property id, assigned in gst_vaapiencode_default_set_property().
-
- Mar 21, 2019
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Mar 11, 2019
-
-
Thibault Saunier authored
It was wrongly changed in 3d9555a8
-
- Mar 04, 2019
-
-
Tim-Philipp Müller authored
-
- Mar 01, 2019
-
-
He Junyan authored
Fix a typo in function description of gst_vaapi_surface_pool_new_with_chroma_type. Signed-off-by: He Junyan <junyan.he@hotmail.com>
-
- Feb 27, 2019
-
-
Víctor Manuel Jáquez Leal authored
When downstream has any caps, vaapi should not shovel vaapi featured buffers, but rather plain raw video, assuming always the worst case scenario (downstream cannot handle featured video memory but raw system memory buffers). This patch query the peer caps without any filter, to know if donwstream just ask for any caps, if so jump to the color space checking, otherwise do the caps intersection and continue with the feature selection algorithm. Fixes: #139
-
- Feb 26, 2019
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Feb 21, 2019
-
-
We prefer to use the same format between image and surface for gst vaapi allocator. The old way may choose different formats between image and surface. For example, the RGBA image may have a NV12 surface. So we need to do format conversion when we put/get image to surface. Some drivers such as iHD can not support such conversion and always cause a data flow error. There may also have some performance cost for format conversion when put/get images. So we prefer to use the same format for image and surface in the allocator. If the surface can not support that format, we then fallback to find a best one as the surface format. Co-authored-by: Víctor Jáquez <vjaquez@igalia.com>
-
- Feb 17, 2019
-
-
Two ARGB formats with the same format information. Should be verbose and delete one. Signed-off-by: He Junyan <junyan.he@hotmail.com>
-
This code is just confused. It's asking for at least as many bits of (z-axis) depth as the root window has bits of (color) depth. For rgb565 or rgb888 this is harmless, but at 10 bits per channel this demands a 30-bit or deeper Z buffer. While some hardware could in principle do a 32-bit Z buffer, Mesa does not expose such fbconfigs (at least on Intel and AMD). We're not actually using the Z buffer, so just stop asking for one.
-
- Feb 16, 2019
-
-
[wl_shell] is officially [deprecated], so provide support for the XDG-shell protocol should be provided by all desktop-like compositors. (In case they don't, we can of course fall back to wl_shell). Note that the XML file is directly provided by the `wayland-protocols` dependency and generates the protocol marshalling code. [wl_shell]: https://people.freedesktop.org/~whot/wayland-doxygen/wayland/Client/group__iface__wl__shell.html [deprecated]: https://github.com/wayland-project/wayland/commit/698dde195837f3d0844b2725ba4ea8ce9ee7518c
-
It will help us to distinguish from other Wayland shell surface (such as XDG-shell) later on.
-
It will help us to distinguish from other Wayland shells (such as XDG-shell) later on.
-
- Feb 11, 2019
-
-
Thread safety patch for ensure_profile() function Fixes #133
-
- Feb 08, 2019
-
-
Víctor Manuel Jáquez Leal authored
This was missed on commit 77bb3424
-
- Jan 24, 2019
-
-
Víctor Manuel Jáquez Leal authored
Register the WM_DELETE_WINDOW message from window manager and trap it to stop the pipeline cleanly. Fixes: gstreamer/gstreamer-vaapi#130
-
- Jan 22, 2019
-
-
Víctor Manuel Jáquez Leal authored
native-id property is problematic since the variable that stores it is gsize, which is platform specific, and in some is bigger than unsigned long, and there are not way to handle gsize properties. Also, GST_VAAPI_ID_INVALID is defined in gsize terms, and we would like to keep using it for this scope. This patch removes the native-id property and set it manually in gst_vaapi_window_new_internal().
-
Víctor Manuel Jáquez Leal authored
gsize type is not equal in all platforms, then the 'l' print modifier shall not be used always. This issue was found in Debian builds.
-
The flag only set as 1 when the rate-control mode is CBR.
-
- Jan 17, 2019
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Jan 14, 2019
-
-
Víctor Manuel Jáquez Leal authored
gst_vaapi_encoder_put_frame() and gst_vaapi_encoder_flush() duplicates the same code segment where the coded buffer is created, the picture encoded on it and pushed to the async queue. The function gst_vaapi_encoder_encode_and_queue() refactor this.
-
Víctor Manuel Jáquez Leal authored
In order to flush the pending pictures, a new internal encoder vmethod is used: get_pending_reordered() This method follows an iterator pattern which will return the next picture to encode and push. The base encoder will call this function in a loop when flush() is called. For now, only H.264 and H.265 encoders implement this flushing mechanism.
-
Instead of dropping all remain frames in reorder_frame_list during flush, keep encoding. gstreamer/gstreamer-vaapi#97
-
- Jan 15, 2019
-
-
wangfei authored
Fix the deinterlace black frame when playing with glimagesink: gst-launch-1.0 filesrc location=test.264 ! h264parse ! vaapih264dec \ ! vaapipostproc deinterlace-mode=1 deinterlace-method=1 ! glimagesink
-