- 23 Nov, 2018 1 commit
-
-
Víctor Manuel Jáquez Leal authored
This will fix the compiler warning "G_HAVE_ISO_VARARGS" is not defined, evaluates to 0 [-Wundef]
-
- 15 Nov, 2018 1 commit
-
-
Xavier Claessens authored
-
- 13 Nov, 2018 1 commit
-
-
Nirbheek Chauhan authored
-
- 12 Nov, 2018 1 commit
-
-
Currently in Python it would become a signed 64 bit value but should actually be an unsigned 32 bit value with all bits set. This is the same problem as with GST_MESSAGE_TYPE_ANY. See https://bugzilla.gnome.org/show_bug.cgi?id=732633
-
- 11 Nov, 2018 2 commits
-
-
Rather then letting gst_gl_memory_setup_buffer guess the GL format used for an eglimage after importing a dmabuf be explicit about it. This fixes issues where dmabuf import may have used another format then gst_gl_format_from_video_info would guess on the basis of the available GL extensions. In particular on etnaviv the gst_gl_format_from_video_info would assuming a luminance + alpha GL format is used for YUY2, but the dmabuf import will always use RG88. Which causes images to end up somewhat pink when displayed on the screen.
-
When importing an egl image from dmabuf gst_gl_format_from_video_info was used to work what the result GL format will be. Unfortunately that will only work if the conventional format and the choosen DRM fourcc for the format match up. On etnaviv platforms there is no support for GL_EXT_texture_rg, so the GL format chosen for YUY2 ends up being GST_GL_LUMINANCE_ALPHA. However DRM does not do luminance + alpha as it's a legacy GL thing, so the dmabuf import ends up using DRM_FORMAT_GR88. To fix this, tie the DRM_FORMAT and the GL format together so they always match up.
-
- 01 Nov, 2018 2 commits
-
-
Nicolas Dufresne authored
There is new code that ensures that we renegotiate after an uploader transition if the negotiated caps have changed. The problem is that the raw uploader will not really try and fixate the input caps, but instead of return a subset with the only the supported target texture. This had two effect, raw uploads was always done renegotiated once and the raw upload unit test was now failing as it didn't expect a renegotiation. As it's a valid check, simply relax the gst_caps_is_equal() check and use a gst_caps_is_subset() instead. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Nicolas Dufresne authored
The direct dmabuf upload does color conversion, so when it transforms the caps, it replaces the format with all formats found through the format query. When this uploader can't be used, it makes the upstream source pick a unsupported format. To fix this, we only append the caps with a list of format. So the source will only pick one of these formats if the downstream preferred format is not supported. A negotiation failure after this would be normal. This fixes pipelines without a glcolorconvert element. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
- 30 Oct, 2018 10 commits
-
-
Report in the DEBUG log if the driver does not support importing a given format with linear modifiers non-externally. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
The EXT_image_dma_buf_import_modifiers extension [1] states regarding eglQueryDmaBufModifiersEXT: The format must be one of those returned by the eglQueryDmaBufFormatsEXT command. To comply with this requirement eglQueryDmaBufFormatsEXT must be called before eglQueryDmaBufModifiersEXT. [1] https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import_modifiers.txt https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Calculate DRM fourcc and report to the DEBUG log about it only once instead of three times in gst_egl_image_from_dmabuf_direct(). https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Michael Olbrich authored
The idea is that some GPUs (like the Vivante series) can actually perform the YUV->RGB conversion internally, so no custom conversion shaders are needed. To make use of this feature, we need an additional uploader that can import DMABUF FDs and also directly pass the pixel format, relying on the GPU to do the conversion. Based on patches from Nicolas Dufresne <nicolas.dufresne@collabora.com> and Carlos Rafael Giani <dv@pseudoterminal.org>. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Michael Olbrich authored
If a upload method is selected then use it exclusively in transform_caps(). Also, reconfigure if the current caps don't match the current upload method. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Michael Olbrich authored
This should not be necessary, but currently not all plugins that provide dmabuf memory announce this with caps features, e.g. v4l2. The static caps already contain the system memory. It didn't break before because other upload methods provide the necessary transformation. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Michael Olbrich authored
Reconfigure will trigger a set_caps which clears the upload method. Remember the method in this case and start with it. Wrap around once to try all methods if necessary. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
Michael Olbrich authored
The colorspace conversion happens during the upload so the necessary hints must be provided to ensure that the conversion works correctly. At least the Mesa Intel driver will create a texture without error but produces an incorrect result. Use eglQueryDmaBufModifiersEXT() to check if non-external upload is supported for the given format. Based on a patch from Carlos Rafael Giani <dv@pseudoterminal.org>. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
gst_gl_memory_setup_buffer() was not properly using the number of pointers to wrapped. This also fixes the validation, as we only support 1 wrapper per view, or num_planes * views wrapper. https://bugzilla.gnome.org/show_bug.cgi?id=783521
-
- 04 Oct, 2018 8 commits
-
-
Matthew Waters authored
Remove testing code from 23159365
-
Matthew Waters authored
Using the correct blend modes for each case or converting to premultipled in the very unlikely case that separate blend modes are unavailable on ancient opengl hardware.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
It's proper new name is gst_gl_stereo_downmix_get_type().
-
Sebastian Dröge authored
-
Matthew Waters authored
This is required to use gloverlaycompositor outside of glimagesink where the output is not automatically flipped
-
Matthew Waters authored
-
Matthew Waters authored
We can get away with ensuring that the memory:GLMemory caps feature is present in the output caps
-
- 03 Oct, 2018 3 commits
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Older glib-mkenums completely fails to parse it otherwise.
-
- 02 Oct, 2018 2 commits
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- 26 Sep, 2018 1 commit
-
-
Matthew Waters authored
This may be a cause of out-of-place frames when transforming multiview buffers.
-
- 25 Sep, 2018 2 commits
-
-
Sebastian Dröge authored
Without this, glviewconvert (and thus glimagesink) will drop all overlay composition metas.
-
Sebastian Dröge authored
-
- 24 Sep, 2018 1 commit
-
-
Tim-Philipp Müller authored
For each lib we build export its own API in headers when we're building it, otherwise import the API from the headers. This fixes linker warnings on Windows when building with MSVC. The problem was that we had defined all GST_*_API decorators unconditionally to GST_EXPORT. This was intentional and only supposed to be temporary, but caused linker warnings because we tell the linker that we want to export all symbols even those from externall DLLs, and when the linker notices that they were in external DLLS and not present locally it warns. What we need to do when building each library is: export the library's own symbols and import all other symbols. To this end we define e.g. BUILDING_GST_FOO and then we define the GST_FOO_API decorator either to export or to import symbols depending on whether BUILDING_GST_FOO is set or not. That way external users of each library API automatically get the import. While we're at it, add new GST_API_EXPORT...
-
- 21 Sep, 2018 1 commit
-
-
Sebastian Dröge authored
Removes some unneeded code duplication between here and GLib. https://bugzilla.gnome.org/show_bug.cgi?id=797184
-
- 18 Sep, 2018 4 commits
-
-
-
Víctor Manuel Jáquez Leal authored
There are a lot of symbols in GstGL-1.0.gir generated by automake that are not when it is generated by meson, because a lot of headers were not included in meson's gir generation. https://bugzilla.gnome.org/show_bug.cgi?id=797158
-
Matthew Waters authored
g-ir-scanner does not have a good enough C parser to parse the GL system headers
-
Matthew Waters authored
-