- Nov 17, 2016
-
-
Sebastian Dröge authored
-
- Nov 11, 2016
-
-
Hyunjun Ko authored
The thread that handles window's events should be finished during pipeline's shutdown, otherwise it will remain alive during pipeline re-activation, leading to unexpected problems. This patch fixes failures of intensive_state_change scenario of gst-validate https://bugzilla.gnome.org/show_bug.cgi?id=774241
-
- Nov 08, 2016
-
-
Víctor Manuel Jáquez Leal authored
"gst_pad_push" is not a good description of the event.
-
Hyunjun Ko authored
Returning GST_FLOW_ERROR always when gst_pad_push fails might lead to deadlock during seek. This patch returns the same error of gst_pad_push() and log out the return value. https://bugzilla.gnome.org/show_bug.cgi?id=774030
-
Víctor Manuel Jáquez Leal authored
Previously the frame map counter increased independently if the map succeeded or not. This leaded to critical messages and crashes if the frame was unable to be mapped, but the counter increased. This patch increases the map counter only if the map operation occurred. https://bugzilla.gnome.org/show_bug.cgi?id=773939
-
Víctor Manuel Jáquez Leal authored
When running gst-discoverer-1.0, in certain media, vaapipostroc is stopped meanwhile it is transforming caps. The problem is that stop() calls gst_vaapi_plugin_base_close(), which nullifies the element's va display, but the va display is used in tranform_caps() when it is extracting the possible format conversions. This display disappearing generates warning messages. This patch holds a local reference of va display at ensure_allowed_raw_caps() hence it doesn't go away meanwhile it is used, even if the gst_vaapi_plugin_base_close() is called in other thread. https://bugzilla.gnome.org/show_bug.cgi?id=773593
-
- Nov 01, 2016
-
-
Sebastian Dröge authored
-
- Oct 27, 2016
-
-
-
-
Víctor Manuel Jáquez Leal authored
Since vaapipostproc is only registered if the driver supports it, all the support for dynamic loading were removed. Though some leftovers remained. https://bugzilla.gnome.org/show_bug.cgi?id=773589
-
-
Víctor Manuel Jáquez Leal authored
In the spirit of the codec split, this patch removes the documentation of vaapidecode and adds a page per each possible decoder. Nonetheless, only those available in the compilation system are going to be instrospected, because the rest are not registered.
-
Víctor Manuel Jáquez Leal authored
-
- Oct 25, 2016
-
-
Víctor Manuel Jáquez Leal authored
Since we can have several vaapipostproc operating in a pipeline, it is useful to know which one is generating the logging message. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
vaapidecode has a member named allowed_caps, but this name is not enough explicit. This patch renames allowed_caps to allowed_sinkpad_caps. No functional changes were included. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
-
-
Víctor Manuel Jáquez Leal authored
In order to clarify the use of flag as input parameter, it is renamed to surface_alloc_flag, since it is used when creating a VA surface with certain properties. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
So encoders and decoders have similar descriptions. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
So encoder and decoders have the same codec name. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Víctor Manuel Jáquez Leal authored
Merge two lines of variable declarations. https://bugzilla.gnome.org/show_bug.cgi?id=773497
-
Hyunjun Ko authored
GstVaapiDecode is a descendant of GstVaapiMiniObject, so, thought we should use its methods, even though it doesn't change functionality. GstVaapiPixmap, GstVaapiTexture and GstVaapiWindow are descendant of GstVaapiObject, hence its methods shall be used. https://bugzilla.gnome.org/show_bug.cgi?id=772554
-
- Oct 19, 2016
-
-
Julien Isorce authored
In short GstFdMemory is configured to call close when using GstDmabufMemory. https://bugzilla.gnome.org/show_bug.cgi?id=755072
-
Víctor Manuel Jáquez Leal authored
-
Víctor Manuel Jáquez Leal authored
In commit dc35dafa a bug was introduced because I assumed that GST_CLOCK_TIME_NONE is zero when is -1. This patch fixes that mistake. https://bugzilla.gnome.org/show_bug.cgi?id=772259
-
- Oct 18, 2016
-
-
Víctor Manuel Jáquez Leal authored
-
- Oct 08, 2016
-
-
Víctor Manuel Jáquez Leal authored
The header gmodule.h is not used since the library dynamic loading for EGL display was removed. https://bugzilla.gnome.org/show_bug.cgi?id=772599
-
- Sep 30, 2016
-
-
Sebastian Dröge authored
-
- Sep 23, 2016
-
-
Vineeth TM authored
https://bugzilla.gnome.org/show_bug.cgi?id=763083 Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
-
- Sep 22, 2016
-
-
Hyunjun Ko authored
When caps reconfiguration is called, the new downstream frame size might be different. Thus, if the downstream caps change,the display's texture map is reset. In addition, during pipeline shutdown, textures in texture map have to be released, since each one have a reference to the GstVaapiDisplay object, which is a dangerous circular reference. https://bugzilla.gnome.org/show_bug.cgi?id=769293 Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
-
Hyunjun Ko authored
instances when created and reuse This patch improves performance when glimagesink uploads a GL texture. It caches the GStVaapiTexture instances in GstVaapiDisplay{GLX,EGL}, using an instance of GstVaapiTextureMap, so our internal texture structure can be found by matching the GL texture id for each frame upload process, avoiding the internal texture structure creation and its following destruction. https://bugzilla.gnome.org/show_bug.cgi?id=769293 Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
-
Hyunjun Ko authored
Implement GstVaapiTextureMap object, which caches VAAPI textures, so them can be reused. Internally it is a hash table. Note that it is GstObject based rather than GstVaapiObject, as part of the future converstion to GstObject of most of the code. https://bugzilla.gnome.org/show_bug.cgi?id=769293 Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
-
- Sep 21, 2016
-
-
Sreerenj Balachandran authored
We are not getting enough compression for some streams and encoded frame end up with more size than allocated. Assuming a compression ratio of 4, which should be good enough for holding the frames. https://bugzilla.gnome.org/show_bug.cgi?id=771528
-
Sreerenj Balachandran authored
While doing the mode-1 referece picture selection, the circular buffer logic was not correctly setting the refresh frame flags as per VP9 spec. Make sure refresh_flag[0] get updated correclty after each cycle of GST_VP9_REF_FRAMES. https://bugzilla.gnome.org/show_bug.cgi?id=771507
-
- Sep 15, 2016
-
-
Víctor Manuel Jáquez Leal authored
When the format of a H.264 stream is AVC3, the SPS and PPS are inside the stream, not in the codec_data, so the size of codec_data might be 7. This patch reduces the minimal size of the codec_data buffer from 8 to 7. https://bugzilla.gnome.org/show_bug.cgi?id=771441
-
Víctor Manuel Jáquez Leal authored
set_format() is called by upstream when the stream capabilites has changed. Before, if the new stream is compatible with the old one the VA decoder was not destroyed. Nonetheless, with this behavoir, the VA decoder ignores when the upstreamer parsers gets more details of the stream, such as the framerate. Hence, when the src caps are negotiates, the further sink caps updates are ignored. This patch forces the VA decoder destroying and recreation when set_format() is called. https://bugzilla.gnome.org/show_bug.cgi?id=770921
-
- Sep 14, 2016
-
-
Sebastian Dröge authored
-
- Sep 12, 2016
-
-
Víctor Manuel Jáquez Leal authored
This reverts commit c67edea4.
-
- Sep 10, 2016
-
-
Jan Schmidt authored
From b18d820 to f980fd9
-
- Sep 09, 2016
-
-
Jan Schmidt authored
From f49c55e to b18d820
-