Hi,
The way aggregator based elements like audiomixer work is that it waits
for input on all pads... Unless one of them is a live source. So if you
have at least one live source, it should timeout after "latency" time
and produce a buffer anyway even if nothing was received.
Olivier
On Wed, 2016-07-06 at 20:31 +0200,
[hidden email] wrote:
> Hello,
>
> I have a case I struggle to understand.
>
> I have multiqueue ! audiomixer ! something pipeline.
>
> In order to keep it flowing all the time, and for testing purposes I
> add audiotestsrc in front of it.
>
> Then I dynamically add branches that fetch data via shmsrc.
>
> If I set audiotestsrc is-live = false, and shmsrcs' is-live = true,
> then stopping data flow on one of shmsrcs is not stopping rest of
> them.
>
> If I use any different combination, stopping one of shmsrcs causes
> others to stop.
>
> What is the rationale behind this?
>
> Marcin
> _______________________________________________
> gstreamer-devel mailing list
>
[hidden email]
>
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel--
Olivier Crête
[hidden email]
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
