GitLab

check that app->seek_format exists before seeking.

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

Ensure errors are cleaned up properly at the right level.
Abort connection attempts if we're cancelled.

Part-of: <!1115>

'ext' object unlocked if gst_rtp_header_extension_read() fails was never
locked in the first place.

Part-of: <!1118>

Use TREMOR define to avoid duplicate symbols
of ivodebis and vorbis plugins when
static linking GStreamer.

Rearrange debug category init.

Part-of: <!1116>

uridecodebin assumes that refcount of decodebins stored in pending_decodebins
are floating but it might not be true in case that refcount of the decodebin
was touched in other places. To avoid the floating refcount issue,
hold strong reference.

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

It's more debugging friendly (tracer for example)

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

Similar to ae8d0cf3

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

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

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

Part-of: <!1105>

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

Lookup will now maintain the full list of possible IP address(es).
We can now iterate over all available addresses in case certain
address families (IPv6) are disabled or try connecting to additional
addresses for the clients.

Part-of: <!1105>

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

consolidate gsttcp.h & gsttcpelements.h
rename gsttcpelement.c to match header

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

The buffer should be set according to DTS if exists
when we are guessin the PTS instead of segment start.
The decoder can receive buffers which are before the segment
in case of seek for example.

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

`@` references are used to reference function parameters, struct members
or enum variants _within_ the current type/function.  It cannot and
should not be used to reference to types outside that.

Since C has no notion of member functions it makes little sense to
prefix these with `@`; most of the documentation here was referencing
functions on _different_ types anyway.

Part-of: <!1090>

This is a direct translation of
<gstreamer/gstreamer!429>,
as playbin{2,3} insulates its sub groups state changes from the pipeline
base class, it needs to track whether the subgroup is live itself,
and handle RESET_TIME the same way GstPipeline does.

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

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

Follow-up to !999 which wasn't backported into 1.18 in the end
after all.

Fixes gstreamer/gst-plugins-base#857

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

As the comment asked, yes, incomplete writes can happen.
I have encountered this with an sshfs mount, for example.

It seems like g_output_stream_write_all() is designed to handle this case,
by not returning until the requested buffer has been completely written,
or an error occurs, which seems to match up with the desired behaviour.

Fixes #885

Part-of: <!1100>

Like other foobarA variant APIs on Windows, formatted string
by strftime() is ANSI string, not unicode encoded one.
It would be problematic for non-english locale systems.
We should use unicode version API (wcsftime in this case)
whenever it's possible on Windows.

Part-of: <!1093>

If the alsasink thread starts the write loop but another thread pauses
the underlying alsa device, the sink thread will endlessly loop.

snd_pcm_writei() will return 0 if the state is SND_PCM_STATE_PAUSED
and the loop will never make any progress.

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

This fix a warning because we were generating 2 pc files for gstgl
library. Also fix missing glesv2 in Requires.

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

Table 1.10 – "Levels for the AAC Profile" only goes to 5 max channels
/ 7 max channel post amendmend, so I assume the number of channels
should not include LFE, otherwise there's no valid level for 5.1 resp.
7.1 (post amendmend)

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

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

Based upon valgrind finding:

Conditional jump or move depends on uninitialised value(s)
   at 0x4AFF589: read_rtp_header_extensions (gstrtpbasedepayload.c:1197)
   by 0x4AFF9E5: gst_rtp_base_depayload_set_headers
(gstrtpbasedepayload.c:1298)
   by 0x4AFFEE0: gst_rtp_base_depayload_do_push
(gstrtpbasedepayload.c:1413)
   by 0x4AFFF53: gst_rtp_base_depayload_push
(gstrtpbasedepayload.c:1448)
   by 0x4AFDEBA: gst_rtp_base_depayload_handle_buffer
(gstrtpbasedepayload.c:801)
   by 0x4AFE41E: gst_rtp_base_depayload_chain_list
(gstrtpbasedepayload.c:899)
   by 0x48F262C: gst_pad_chain_data_unchecked (gstpad.c:4414)
   by 0x48F3333: gst_pad_push_data (gstpad.c:4655)
   by 0x48F3DF8: gst_pad_push_list (gstpad.c:4814)
   by 0x4AFAD87: gst_rtp_base_payload_push_list
(gstrtpbasepayload.c:1978)
   by 0x72B3154: gst_rtp_vp8_pay_handle_buffer (gstrtpvp8pay.c:672)
   by 0x4AF7031: gst_rtp_base_payload_chain (gstrtpbasepayload.c:868)
 Uninitialised value was created by a heap allocation
   at 0x483C77F: malloc (in
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
   by 0x4B8BA78: g_malloc (gmem.c:106)
   by 0x4BA3A9D: g_slice_alloc (gslice.c:1069)
   by 0x488D777: _sysmem_new_block (gstallocator.c:413)
   by 0x488DB28: default_alloc (gstallocator.c:512)
   by 0x488D3E8: gst_allocator_alloc (gstallocator.c:310)
   by 0x4AE97E3: gst_rtp_buffer_set_extension_data (gstrtpbuffer.c:856)
   by 0x4AF9EC6: set_headers (gstrtpbasepayload.c:1757)
   by 0x489FE4D: gst_buffer_list_foreach (gstbufferlist.c:287)
   by 0x4AFA87A: gst_rtp_base_payload_prepare_push
(gstrtpbasepayload.c:1915)
   by 0x4AFAD06: gst_rtp_base_payload_push_list
(gstrtpbasepayload.c:1970)
   by 0x72B3154: gst_rtp_vp8_pay_handle_buffer (gstrtpvp8pay.c:672)

Part-of: <!1075>

gst_type_find_suggest_simple() now requires a NULL terminator.
Use the new, simpler API for no-parameter calls.

gstreamer!774 (comment 861492)

Part-of: <!1092>

e.g. if we have:

video-x/raw,format=I420 ! compositor ! video/x-raw,format=BGRA

This will currently produce a warning as the alpha-ness of the chosen
'best' format (I420) will be different from the value restricted by the
downstream caps filter.

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

Split plugin into features including
dynamic types which can be indiviually
registered during a static build.

More details here:

gstreamer/gst-build!199
gstreamer/gstreamer!661

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

Split plugin into features including
dynamic types which can be indiviually
registered during a static build.

More details here:

gstreamer/gst-build!199
gstreamer/gstreamer!661

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

Split plugin into features including
dynamic types which can be indiviually
registered during a static build.

More details here:

gst-build!199
gstreamer!661

Part-of: <!1089>

Split plugin into features including
dynamic types which can be indiviually
registered during a static build.

More details here:

gst-build!199
gstreamer!661

Part-of: <!1089>

Split plugin into features including
dynamic types which can be indiviually
registered during a static build.

More details here:

gst-build!199
gstreamer!661

Part-of: <!1089>

All these signals don't run the class handler in the CLEANUP stage.

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

The --include-hidden argument was --show-hidden in a previous iteration of
commit ddf3e666, and I forgot to change the
example.

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

Filter out the ones which are already present. Can happen with several input
stream which have identical collections

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

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

When adding inputs dynamically, we need to make sure the new parsebin are
added *and* activated by the same thread (by taking the state change lock).

The rationale for this is that the calling thread might be an upstream streaming
thread and when activating parsebin it might call back upstream. If we don't use
the same thread (ex: when the application does a state change on decodebin3
between the moment we add parsebin to decodebin3 and we synchronize the state of
parsebin) then we would end up in different threads trying to take upstream
recursive locks.

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

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

Even if we don't care about any global objects being removed, wayland
will still error if globals are removed without a corresponding listener
set up for them.  e.g. wl_output hotplugging

Discovered by: Matthias Clasen

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