High initial playback delay when using audiomixer

Ajit Warrier ajit.warrier at gmail.com
Fri Dec 9 00:48:36 UTC 2016


Unfortunately, I will need to re-visit this issue. I found that the
start-time-selection=1 works as expected (no playback delay) if:

1. Pipeline has just started - audiomixer has no sink pads and a new sink
pad is created.
2. Audiomixer has at least one (inactive) sink pad, and audio is played on
a new sink pad.

In the scenario that all sink pads on audiomixer are removed, the next new
sink pad will incur the high delay as before. The delay gets longer
proportional to the time between "no sink pads" to "audio arrives on the
new sink pad".

Does this make sense ? Does the start-time-selection property (or its
implied behavior) get reset when all sink pads are removed ?

Thanks,
Ajit.

On Tue, 29 Nov 2016 at 19:13 Nicolas Dufresne <nicolas.dufresne at gmail.com>
wrote:

> Le mercredi 30 novembre 2016 à 01:57 +0000, Ajit Warrier a écrit :
> > Ah! That was it ! Thanks! This property seems not documented either
> > in audiomixer/aggregator. Any reason for this ?
>
> Sorry I didn't notice as I often look at the gst-inspect-1.0 output
> instead. The property should show up in the html doc of GstAggregator,
> but is indeed missing. This is a documentation bug, I will file.
>
> Nicolas_______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20161209/3987b249/attachment.html>


More information about the gstreamer-devel mailing list