GitLab

audioaggregator: Only check downstream caps when handling CAPS events if we didn't negotiate with downstream yet

If we already negotiated with downstream there is not point in checking
if the caps are supported. We already know that this is the case.

Part-of: <gstreamer/gst-plugins-base!768>

Otherwise it might happen that downstream prefers a different rate (i.e.
puts it into the first structure) and also supports other rates, but
audioaggregator would then fail negotiation.

Also this now correctly handles downstream returning a range of
supported rates.

Fixes gstreamer/gst-plugins-base#795

Part-of: <gstreamer/gst-plugins-base!768>

This summary displays a list of plugins which
have been enabled.

Part-of: <gstreamer/gst-plugins-base!765>

It was not working properly and the implementation of the smartencoder
element was weird. This introduce a number of changes (which are all
in one single commit because they basically all work together and lead
to basically reimplementing the element):

* Make smartencoder a bin so that the reencoding chain of elements are
  inside of it instead of not having any parent. Those elements were not
  be visible when dumping the pipeline which was very confusing.
* Make encodebin create the right encoder with a capsfilter (and parser)
  to properly enforce the format specified by the user, and so that the
  encoder properties specified in the encoding profile are respected.
* Use `decodebin` to do the decoding instead of selecting a decoder
  ourself and not plug any parser etc...
* Ensure that negotiated format in the sinkpad of smart encoder is fixed
  through time when the user requested a non dynamic output
* Add a parser at the beginning of the smart encoder
* Handle errors when reencoding

Part-of: <!751>

Otherwise the branch that get selected later won't receive it ever.

Part-of: <!751>

Otherwise we miht have frames queued in the encoder from the old branch
that do not get encoded/muxed when they should.

The implementation is a bit 'weird' but the rational and solution
is documented in the code.

Part-of: <gstreamer/gst-plugins-base!751>

Part-of: <gstreamer/gst-plugins-base!751>

Adding properties for each and every rtp header extension is not
scalable and a new interface will be implemented for the general case
(#777).

Set the environment variable "GST_RTP_ENABLE_EXPERIMENTAL_TWCC_PROPERTY"
to any value to reenable the short-lived twcc-ext-id property.

Fixes gst-plugins-good#761

Part-of: <!756>

This is better than going into an infinite loop.

Part-of: <gstreamer/gst-plugins-base!761>

Letting this through instead results in an infinite loop where
the exact same buffer gets pushed out ad infinitum.

Part-of: <gstreamer/gst-plugins-base!761>

Part-of: <gstreamer/gst-plugins-base!761>

The ALSA provider doesn't provider live monitoring, so don't
pretend otherwise.

Part-of: <!735>

This introduced a possible regression where the EGL display connection
could be leaked when a foreign native display (x11, wayland, etc) could
create a non-foreign EGL display that would never be destroyed.

The underlying problem needed to be solved in a different way.  See
#640
for more details.

This reverts commit 2e686b0d.

Part-of: <!758>

The priority of the thread that executes audioringbuffer_thread_func
is incremented on Windows by the usage of the AvSetMmThreadCharacteristics
API. This change has to be restored, as described on the documentation
of the API (https://docs.microsoft.com/en-us/windows/win32/api/avrt/nf-avrt-avsetmmthreadcharacteristicsw#remarks),
with a call to the AvRevertMmThreadCharacteristics. If this is not done,
a handle will be leaked.

Part-of: <gstreamer/gst-plugins-base!760>

All APIs in avrt.h are desktop only.

Part-of: <gstreamer/gst-plugins-base!763>

We don't install any cocoa/win32 specific headers.

Part-of: <gstreamer/gst-plugins-base!759>

Fixes -Wmissing-field-initializers in Clang.

Part-of: <gstreamer/gst-plugins-base!757>

Part-of: <!757>

Part-of: <gstreamer/gst-plugins-base!754>

This adds linear 32x32 NV12 based tiles. This format is notably used by
Allwinner VCU and exposed in V4L2 as being "SUNXI Tiled" format. In this
patch we generalize the plane info calculation so we can share this part
with the 4L4 variant.

Part-of: <!754>

Part-of: <gstreamer/gst-plugins-base!753>

When using tile format, the stride has a different meaning. It used
the MSB and LSB 16bits to encode respectively the width and height in
number of tiles.

This issue was introduce with commit e5b70d38 which was fixing
missing size recalculation when strides and offset is updated.

Part-of: <!753>

This format is produced by Verisillicon VC8000D VPU decoder, it is a simple 4x4
tiling layout in a linear way.

Part-of: <!753>

Part-of: <!707>

-Waggregate-return: used by some Qt clases extensively and not super
useful for this example. Supress it.

warning: "GL_GLEXT_VERSION" redefined: Perform the same workaround as
qmlglsink by defining the old gl/GL.h header guard if the new GL/gl.h
guard exists.

Part-of: <gstreamer/gst-plugins-base!752>

Part-of: <!476>

Fixes gstreamer/gst-plugins-base#684

Part-of: <gstreamer/gst-plugins-base!749>

All UI elements will follow Single-Threaded Apartments (STA) model.
As a result, we should access them from dedicated UI thread.
Due to the nature of the threading model, ANGLE will wait the UI
thread while closing internal window/swapchain objects.

A problem here is that when destroying GstGLWindow from the UI thread,
it will wait GstGLContext's internal thread. Meanwhile, the GstGLContext's
internal thread will be blocked because ANGLE wants to access the UI thread.
That will cause a deadlock or exceptions.

In short, application should not try to call
gst_element_set_state(pipeline, GST_STATE_NULL) from a UI thread.
That's a limitation of current implementation.

Part-of: <gstreamer/gst-plugins-base!745>

GstGLWindow implmentaion should be able to report native window size
and also it need to handle resize event for glimagesink.

Note that GstD3D11Window implementation was referenced for this change.

Part-of: <gstreamer/gst-plugins-base!745>

For native window size query, c++ API is much convenient than c API

Part-of: <gstreamer/gst-plugins-base!745>

Don't put double ':' there

Part-of: <gstreamer/gst-plugins-base!663>

Part-of: <gstreamer/gst-plugins-base!663>

Add property "handle-segment-change" for user to allow pushing
custom segment event. For now, this property can work only for
time format GstSegment.
This property can be useful in case application controls timeline
of stream such as there is timestamp discontinuity but playback is
expected to be continuous. Multi-period scenario of MPEG-DASH is an
example of this use case.

Part-of: <gstreamer/gst-plugins-base!663>

We have the notion of presence, and when the user want to be in control
it is totally legitimate for him to have several occurrences of a
similar profile

Part-of: <gstreamer/gst-plugins-base!746>

Since we are using VideoMeta, the converter (similarly to the video_frame_copy
utility) should have no issue dealing with frames that are slightly larger.
This situation occure as some element will use padded width/height for
allocation, which results in a VideoMeta width/height being larger then the
display width/height found in the negotiated caps.

Fixes #790

Part-of: <gstreamer/gst-plugins-base!747>

get_allowed_caps() will return NULL, which is not a problem in itself.
Just take the template caps for negotiation in that case instead of
erroring out.

Part-of: <gstreamer/gst-plugins-base!744>

And fix up DOAP file XML. Parser would complain about
unknown entity ! here.

Part-of: <!743>

Don't put gl into the libraries list if the gst-gl library isn't
being built, and also don't include it in the list of linker flags
then.

Fixes gstreamer/gst-plugins-base#613

Part-of: <gstreamer/gst-plugins-base!742>

Calling gst_gl_window_send_{key,mouse}_event() from GstGLContext
thread might cause a deadlock. Instead, use the dedicated event handling
thread in GstGLDisplay.

Part-of: <!721>

Add test option "--fullscreen" for testing fullscreen mode switch.
When enabled, user can switch fullscreen mode via SPACE key or
right mouse button click.

Part-of: <!721>