<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>I don't have gst_pipeline_set_latency as I am stuck on gstreamer 1.4.5 and can't change it due to embedded system.<div>Is there a way to use do_latency signal to do this?<br><br><div>Subject: Re: appsrc flushing, or decoder flushing<br>From: nicolas.dufresne@gmail.com<br>To: gstreamer-devel@lists.freedesktop.org<br>Date: Tue, 22 Mar 2016 19:52:43 -0400<br><br><pre>Le mardi 22 mars 2016 à 16:08 -0700, Ash 20001 a écrit :<br>> gst-launch-1.0 -v filesrc location=out.264 ! h264parse ! decodebin !<br>> xvimagesink<br>> <br>> I have converted this pipeline into C++ code using appsrc as the<br>> source. The pipeline requires several frames before it actually start<br>> to output (around 7 frames by my calculations, depending on content).<br>> So if my appsrc is a live source, I can never seem to render the most<br>> up to date frame because it is always 7 frames behind. Is there a way<br>> to set something on the pipeline or flush the pipeline for live<br>> sources?<br> <br>H264 decoder element should expose their latency in order to work<br>properly in live mode. Did you verify that OMX decoder do that ? You<br>can always manually force a latency to get going. See<br>gst_pipeline_set_latency().<br> <br>Nicolas<br></pre><br>_______________________________________________ gstreamer-devel mailing list gstreamer-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</div></div> </div></body> </html>