Fwd: gstomxvideodec asynchronously cleans the older frames./Delay in pushing the frame

sudipj sudipj79 at gmail.com
Tue Sep 9 21:30:40 PDT 2014


Forwarding to Sebastian

---------- Forwarded message ----------
From: Sudip Jain <sudipj79 at gmail.com>
Date: 9 September 2014 11:21
Subject: gstomxvideodec asynchronously cleans the older frames./Delay in
pushing the frame
To: gstreamer-devel at lists.freedesktop.org


The decode loop asynchronously cleans older frames from queue, as it
expects every acquired is filled, which may not be always true. It results
in pushing empty buffer to downstream element. Specially when there is no
injection between two acquired buffers.

The acquire/release mechanism in decode loop introduce delay as it does not
push the buffer ASAP "FilledBufferDone" It waits for the same buffer to be
acquired again after recycling all the buffers in the pending list. By this
time a few input buffers are queued, which eventually gets cleaned up
without being productive.

I have OMX IL based on v4l2 decoder which configures the output port after
the header is injected i.e allow going in OMX_Executing state.

Can you suggest if  I must or "not" use the --no-disable-output hack ?

Regards,
Sudip




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Fwd-gstomxvideodec-asynchronously-cleans-the-older-frames-Delay-in-pushing-the-frame-tp4668628.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140909/91f9da91/attachment.html>


More information about the gstreamer-devel mailing list