| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Without this, a buffer is dropped if glupload indicates that it is
necessary to reconfigure.
Avoid this by explicitly reconfiguring immediately and uploading the buffer
again.
https://bugzilla.gnome.org/show_bug.cgi?id=783521
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=797353
|
| |
|
| |
|
|
|
|
|
|
| |
GstVideoOverlayComposition on a stream
https://bugzilla.gnome.org/show_bug.cgi?id=797234
|
|
|
|
|
|
|
| |
Before freeing pending pads it is required to hold the mutex, that's
what is protecting the list of pending pads in other places.
https://bugzilla.gnome.org/show_bug.cgi?id=796935
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous failure was a timeout which was due to the sending pipeline
pushing test buffer *before* the remote client was accepted. We would
therefore never get the buffer on the other side.
While the client socket would indeed appear as "connected", this doesn't
mean that the remote server side did "accept" it (which is where we then
add it to the list of remote parties to which data will be sent).
The problem isn't with the element implementation, but to the nature of
TCP 3-way handshake.
In order to make the test reliable, wait for the sink to have accepted
the remote client (by checking the number of handles) before sending out
test buffers.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=796860
|
| |
|
|
|
|
|
|
|
|
| |
Use 'copy' keyword to avoid meson warning message.
Note that 'copy' keyword in configure_file() is available
since meson 0.47.0
https://bugzilla.gnome.org/show_bug.cgi?id=797298
|
|
|
|
| |
Otherwise it's very easy to miss them when gst_video_frame_map() fails
|
|
|
|
|
|
|
|
|
| |
rtsp_connection_send takes care of adding those already,
and some reverse proxies such as nginx will reject the request
altogether if the Authorization header is present twice,
even with the same value.
https://bugzilla.gnome.org/show_bug.cgi?id=797272
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a source-info property that will read/write meta to the buffers
about RTP source information. The GstRTPSourceMeta can be used to
transport information about the origin of a buffer, e.g. the sources
that is included in a mixed audio buffer.
A new function gst_rtp_base_payload_allocate_output_buffer() is added
for payloaders to use to allocate the output RTP buffer with the correct
number of CSRCs according to the meta and fill it.
RTPSourceMeta does not make sense on RTP buffers since the information
is in the RTP header. So the payloader will strip the meta from the
output buffer.
https://bugzilla.gnome.org/show_bug.cgi?id=761947
|
|
|
|
| |
https://github.com/mesonbuild/meson/pull/4169
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=797173
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=797225
|
|
|
|
|
|
| |
otherwise caps intersection always fails when converting non-interleaved to interleaved audio
https://bugzilla.gnome.org/show_bug.cgi?id=797225
|
|
|
|
|
|
| |
This reverts commit 452d90a88c6e68a3daa38e02213782836788236a.
This was actually correct. sorry for the noise!
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the internal viewconvert to not scale buffers for output with the
following pipeline:
gltestsrc ! glimagesink
It also fixes overlay composition with a resized output with an OpenGL
upstream:
gltestsrc ! timeoverlay ! glimagesink
|
|
|
|
| |
This reverts commit 779d028f27b7bc6eb7abe841fe2cda97de3be983.
|
|
|
|
|
| |
Fallback to the closest but incorrect values we had before if we can't
do this correctly.
|
|
|
|
| |
Remove testing code from 23159365618409011745b554b4ad371700961121
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
It's proper new name is gst_gl_stereo_downmix_get_type().
|
| |
|
|
|
|
| |
And register a GType for it.
|
| |
|
|
|
|
|
|
|
|
|
| |
Attempting to use the MAX(1, display_rect) would result in the overlay
composition attempting to draw into 1x1 buffer and calculate some
grossly incorrect sizes.
previously failing case:
gltestsrc ! textoverlay text=GStreamer ! glimagesinkelement
|
|
|
|
|
|
|
| |
Flattens all the overlays from the GstVideoOverlayCompositionMeta into
the video stream.
https://bugzilla.gnome.org/show_bug.cgi?id=759867
|
|
|
|
|
| |
This is required to use gloverlaycompositor outside of glimagesink where
the output is not automatically flipped
|
| |
|
|
|
|
|
| |
We can get away with ensuring that the memory:GLMemory caps feature is
present in the output caps
|
| |
|
|
|
|
| |
Older glib-mkenums completely fails to parse it otherwise.
|
|
|
|
| |
The old one still exists but behind GST_DISABLE_DEPRECATED
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=797240
https://bugzilla.gnome.org/show_bug.cgi?id=797144
|
| |
|
| |
|
|
|
|
|
|
| |
It was checking for GST_IS_CAPS only and that would fail if the new
restriction caps was NULL and its documentation says it accepts NULL as
valid input.
|