6 commits

Author	SHA1	Message	Date
Tim-Philipp Müller	510e8ef8cb	docs: fix element names in section headers ... Hopefully that'll make hotdoc pick up the docs for these elements. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1428>	2020-07-10 19:22:29 +00:00
Mathieu Duponchelle	a048ce81d4	plugins: uddate gst_type_mark_as_plugin_api() calls	2020-06-06 00:40:42 +02:00
Sebastian Dröge	a5b1e1e96d	clockselect: Don't register GstClockSelectClockId multiple times	2020-06-04 13:33:16 -04:00
Sebastian Dröge	74f2f733be	plugins: Use gst_type_mark_as_plugin_api() for all non-element plugin types	2020-06-04 13:33:16 -04:00
Ederson de Souza	3ea0f694de	clockselect: Add TAI clock support ... Via new value for property clock-id, "tai", it's possible to use GST_CLOCK_TYPE_TAI as pipeline clock. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1009>	2020-04-30 19:21:37 +00:00
Ederson de Souza	fe8e2a001c	debugutils: clockselect, a pipeline that enables clock selection ... Sometimes, one wants to force a clock on some pipelines - for instance, when testing TSN related pipelines, one usually uses GstPtpClock or CLOCK_REALTIME (assuming system realtime clock is in sync with network one). Until now, one needs to write an application for that - not difficult, but quite boring if one just wants to test something. This patch presents a new element to help that: clockselect. clockselect is a pipeline with two properties to select a clock. One property, "clock-id", enables one to choose between "monotonic", "realtime", "ptp" or "default" clock - where default keeps pipeline behaviour of choosing a clock based on its elements. The other property, "ptp-domain" gives one the choice of which PTP domain should be used. Some very simple tests also added for this new element.	2019-11-06 08:58:53 -08:00