Avoiding stall in a transcoding pipeline - how?

Baby Octopus jagadishkamathk at gmail.com
Wed Jun 14 11:32:05 UTC 2017


Pipeline negotiation issue should be easy to debug. Have you enabled -v
verbose mode. Do you see a particular element exposing caps which the next
element may not support?

~BO

On Wed, Jun 14, 2017 at 3:27 PM, Graham Leggett [via GStreamer-devel] <
ml+s966125n4683375h92 at n4.nabble.com> wrote:

> On 14 Jun 2017, at 6:19 AM, Baby Octopus <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=4683375&i=0>> wrote:
>
> > There is no hard and fast rule to make the pipeline bullet proof! It
> entirely
> > depends on the type of stall that you see and the reason for it, whether
> it
> > is internal issue due to the pipeline itself, or caused by dirty input
> that
> > you are referring to
>
> Obviously, however seeing the state of the pipeline and where the data is
> stuck will lead you right to the problem, and then you can fix it and move
> on.
>
> > Can you explain the scenarios where you the stall and sample input with
> the
> > pipeline on how to reproduce it?
>
> The pipeline consists of a decodebin wired into an encodebin, which
> transcodes an mpegts containing video and audio at 44.1khz. The pipeline is
> successfully linked, but 44.1k audio refuses negotiation and the pipeline
> stalls. Ignoring the 44.1khz audio and transcoding a parallel 48khz stream
> works. I have not got to the bottom of that problem yet, but I now know it
> exists and can avoid it for now.
>
> There was also an attempt to dump a subtitle stream to fakesink, and that
> was blocking due to the length-in-time of the queue. Making that queue
> leaky unblocked that part of the pipeline.
>
> Regards,
> Graham
>>
>
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4683375&i=1>
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
> *smime.p7s* (4K) Download Attachment
> <http://gstreamer-devel.966125.n4.nabble.com/attachment/4683375/0/smime.p7s>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://gstreamer-devel.966125.n4.nabble.com/Avoiding-stall-
> in-a-transcoding-pipeline-how-tp4683287p4683375.html
> To unsubscribe from Avoiding stall in a transcoding pipeline - how?, click
> here
> <http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4683287&code=amFnYWRpc2hrYW1hdGhrQGdtYWlsLmNvbXw0NjgzMjg3fC0yNDIzMzk5Mjc=>
> .
> NAML
> <http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Avoiding-stall-in-a-transcoding-pipeline-how-tp4683287p4683380.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170614/8fdb0fec/attachment.html>


More information about the gstreamer-devel mailing list