- Jul 06, 2016
-
-
Sebastian Dröge authored
-
- Jul 05, 2016
-
-
Víctor Manuel Jáquez Leal authored
-
-
-
- Jun 29, 2016
-
-
Víctor Manuel Jáquez Leal authored
This patch is a fix for my bad review of commit 6d73ca8d. The element should be able to return the available raw caps handled by the VA display, but that only should happen when there a VA display. If there's none, the element should use the caps template. https://bugzilla.gnome.org/show_bug.cgi?id=768161
-
Matthew Waters authored
This delays the requirement of having a GstVaapiDisplay until later https://bugzilla.gnome.org/show_bug.cgi?id=768161
-
- Jun 28, 2016
-
-
Víctor Manuel Jáquez Leal authored
Add VP9Profile0-3 name mapping.
-
Víctor Manuel Jáquez Leal authored
This is a missed changeset from commit 1c05c53b, since also header includes should be nested.
-
Víctor Manuel Jáquez Leal authored
Though USE_{JPEG,VP8,VP9,H265}_ENCODER macros definition depend on USE_ENCODER macro, it is clearer to nest them, showing explicitly the dependency relation.
-
- Jun 24, 2016
-
-
Víctor Manuel Jáquez Leal authored
Under certain conditions the element might receive a positive context query but without a context instance. This situation will lead to a segmentation fault when traversing the context list in the pipeline. https://bugzilla.gnome.org/show_bug.cgi?id=767946
-
- Jun 23, 2016
-
-
Scott D Phillips authored
glibcompat.h is no longer doing anything. Remove it. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=767886
-
Scott D Phillips authored
Change defaults for max-bframes, cabac, and dct8x8 to be enabled by default. This will cause the default profile to be high instead of baseline. In most situations this is the right decision, and the profile can still be lowered in the case of caps restrictions. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=757941
-
Víctor Manuel Jáquez Leal authored
Raise an element warning if a required element is not available, thus the pipeline will post a warning message and the application will be informed.
-
- Jun 22, 2016
-
-
Without this, all dpb pictures are not released during flush, because we used the global dpb_count variable for checking the dpb fullness which get decremented in dpb_remove_index() routine during each loop iteration. https://bugzilla.gnome.org/show_bug.cgi?id=767934
-
- Jun 21, 2016
-
-
Nicolas Dufresne authored
From ac2f647 to f363b32
-
- Jun 17, 2016
-
-
Víctor Manuel Jáquez Leal authored
gst/gst.h is already included in gstcompat.h
-
Víctor Manuel Jáquez Leal authored
-
- Jun 16, 2016
-
-
Víctor Manuel Jáquez Leal authored
If vaapisink received a caps query before getting a VA display, it returned only the surfaces related caps. This behavior broke the autovideosink negotiation. This patch returns the pad's template caps if no VA display, otherwise the caps are crafted as before. https://bugzilla.gnome.org/show_bug.cgi?id=767699
-
- Jun 15, 2016
-
-
Scott D Phillips authored
Clarify that vaapi context resets are never needed for vp9, but that ensure_context() needs called when the size increases so that new surfaces can be allocated. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=767474
-
Scott D Phillips authored
Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=767474
-
Scott D Phillips authored
In cases where we know the video meta must be present, add it to the pool configuration. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=766184
-
- Jun 14, 2016
-
-
Scott D Phillips authored
if gst_buffer_pool_set_config returns FALSE, check the modified config and retry set_config if the config is still acceptable. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=766184
-
- Jun 08, 2016
-
-
Víctor Manuel Jáquez Leal authored
Mark as internal the functions used by VA-API dmabuf allocator.
-
Víctor Manuel Jáquez Leal authored
There's no need to check for the display in the plugin object when decide_allocation() vmethod is called, because the display will created or re-created along the method execution.
-
Víctor Manuel Jáquez Leal authored
Get the pool config just before use it, to avoid a memory leak if the allocator cannot be instantiated. Similarly, return FALSE if the configuration cannot be set, avoid keep a not used allocator in the pool.
-
Víctor Manuel Jáquez Leal authored
Instead of using the VASurface proxy's notify, which is internal gstvaapi API, use the GStreamer's GstParentBufferMeta. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
This patch avoids the creation of a VASurface each time a new input buffer is processed, caching them in the input buffer itself. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
Instead of passing the data already in GstVideoInfo, let's just pass the GstVideoInfo structure. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
Instead of instantiating an allocator per vaapivideobufferpool, only one allocator is instantiated per element's pad and shared among future pools. If the pad's caps changes, the allocator is reset. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
Originally, vaapivideobufferpool has a set of boolean variables for the buffer configuration options. This pach changes these boolean variables for a single bitwise, just as it is used in pluginbase. Hence, the internal enum was moved to vaapivideobufferpool header. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
This patch refactors the code in pluginbase in order to centralize the buffer pool instantiation. As the buffer pool config may have different options, these are gathered using a bitwise flag. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
Originally vaapivideobufferpool instantiates its own allocator regardless the received configuration, and it relies in custom configuration options to choose which kind of allocator instantiate. This patch transfers the responsibility of the allocator instantiate to vaapipluginbase and pass it to the vaapivideobufferpool through its configuration. * gst/vaapi/gstvaapipluginbase.c + set_dmabuf_allocator(): inserts a dmabuf allocator in the bufferpool + ensure_sinkpad_buffer_pool(): set a normal vaapi video allocator in bufferpool configuration + gst_vaapi_plugin_base_propose_allocation(): call set_dmabuf_allocator() if needed. + gst_vaapi_plugin_base_decide_allocation(): set a normal vaapi video allocator in bufferpool configuration * gst/vaapi/gstvaapivideobufferpool.c + gst_vaapi_video_buffer_pool_set_config(): instead of instantiate the allocator, process the received one through its configuration. * gst/vaapi/gstvaapivideobufferpool.h: removed GST_BUFFER_POOL_OPTION_DMABUF_MEMORY since it is not used anymore. * gst/vaapi/gstvaapivideomemory.c + gst_vaapi_is_dmabuf_allocator(): new helper function to identify a dmabuf allocator with the vaapi qdata. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
Instead of keeping old and new GstVideoInfo video structure, we only keep one, the current one, the negotiated. The old one is not needed at all. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
This lines repeat a couple times in the code, so it would be better to put it a helper function. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
Víctor Manuel Jáquez Leal authored
This function is shared among different elements, so let factorized it. https://bugzilla.gnome.org/show_bug.cgi?id=765435
-
-
-
Scott D Phillips authored
Add a mutex to postproc to protect concurrent access to data members. Previously set_caps() could release the allowed_srcpad_caps while transform_caps was in the middle of using it. Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=766940
-
- May 30, 2016
-
-
Sreerenj Balachandran authored
Added two modes(as properties) for reference picture selection: ref-mode-0: AltRef and GoldRef pointing to the recent keyframe and LastRef is pointing to the previous frame. ref-mode-1: Previous frame (n) as LastRef , n-1 th frame as GoldRef and n-2 th frame as AltRef https://bugzilla.gnome.org/show_bug.cgi?id=766048
-