From 1692f910e7237a828ed7987ab30f08c793a6b695 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tim-Philipp=20M=C3=BCller?= Date: Fri, 14 Jul 2017 13:54:31 +0100 Subject: [PATCH] audiomixer: document caps negotiation raciness Until we land conversion support in audioaggregator (#773762). https://bugzilla.gnome.org/show_bug.cgi?id=777915 --- gst/audiomixer/gstaudiomixer.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/gst/audiomixer/gstaudiomixer.c b/gst/audiomixer/gstaudiomixer.c index 0ac0f4afc2..66ca3ec2e4 100644 --- a/gst/audiomixer/gstaudiomixer.c +++ b/gst/audiomixer/gstaudiomixer.c @@ -28,7 +28,15 @@ * The audiomixer allows to mix several streams into one by adding the data. * Mixed data is clamped to the min/max values of the data format. * - * Unlike the adder element audiomixer properly synchronises all input streams. + * Unlike the adder element audiomixer properly synchronises all input streams + * and also handles live inputs such as capture sources or RTP properly. + * + * Caps negotiation is inherently racy with the audiomixer element. You can set + * the "caps" property to force audiomixer to operate in a specific audio + * format, sample rate and channel count. In this case you may also need + * audioconvert and/or audioresample elements for each input stream before the + * audiomixer element to make sure the input branch can produce the forced + * format. * * The input pads are from a GstPad subclass and have additional * properties to mute each pad individually and set the volume: