Regarding the multiqueue buffering timeout

[Justin J. Kim]

Hello,

> It means if the data feeding is blocked somewhere upstream, the multiqueue never post timeout message to the bus.


If somewhere in upstream is blocked, the blocked element would have a problem.
multiqueue is a kind of passive element so it cannot know when the next data comes.

FWIW, in some special case like interleaved stream in push mode,
I’m trying to find solution here by assistance of decodebin, https://bugzilla.gnome.org/show_bug.cgi?id=733235 <https://bugzilla.gnome.org/show_bug.cgi?id=733235>

Thanks,
Justin


> 2015. 8. 1., 오후 10:35, tt <ystoto at gmail.com> 작성:
> 
> Hi, there
> 
> It seems the gstmultiqueue can measure the buffering period only from new data pushing.
> It means if the data feeding is blocked somewhere upstream, the multiqueue never post timeout message to the bus.
> This Is a weakpoint of multiqueue, isn't it? 
> Does anybody have a plan to improve this?
> 
> Thanks
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20150802/bedb6563/attachment.html>