imagefreeze + leaky queue problem

[Sebastian Dröge]

On Do, 2016-06-09 at 00:10 -0700, mariannasb wrote:
> 
> By setting the debug levels I can see that the problem is the imagefreeze
> increment the timestamp way too fast (it moves in increments corresponding
> to the fps, but it is not following the clock).
> It seems to me that it tries to push buffers as fast as it can, incrementing
> the timestamp by the fps interval each time, and since the queue leaks it
> manages to do it way faster than it should...

That's exactly the problem and how it is intended to work. If you need
the input stream to be produced in real-time, you could add an identity
element with sync=true before the leaky queue.

leaky queues will generally only work in a meaningful way with live
input.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160609/728509a4/attachment.sig>