Sebastian Dröge ba294415d7 basesink: Post a latency message whenever we're ready to answer the query ... Usually the latency message is only posted whenever latency of an element changes but that might be too early as the sinks might not be able to query the latency at that point yet. Similarly adding a new sink should cause latency reconfiguration once that new sink is able to report its latency. This fixes latency configuration in pipelines where webrtcbin is the only "sink", i.e. it is used in a sendonly session. Before, the latency would always be configured to 0. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/843>		2021-06-28 19:59:47 +03:00
..
cleanup.c	basesink: Post a latency message whenever we're ready to answer the query	2021-06-28 19:59:47 +03:00
parse-disabled.c	Fix FSF address	2012-11-03 20:44:48 +00:00
parse-launch.c	Use gst_object_unref() / gst_object_clear() instead of the GObject ones	2020-04-20 16:28:52 +00:00
queue-error.c	Fix double semicolons	2015-03-10 09:24:28 +00:00
seek.c	tests: seek: Don't use too strict timeout for validation	2020-09-15 00:54:58 +09:00
simple-launch-lines.c	basesink: Post a latency message whenever we're ready to answer the query	2021-06-28 19:59:47 +03:00
stress.c	tests: use g_timeout_add_seconds in pipeline stress test	2013-01-27 14:52:39 +00:00