<v4l2src0> lost frames detected

Nicolas Dufresne nicolas at ndufresne.ca
Fri Jun 19 14:35:55 UTC 2020

Le vendredi 19 juin 2020 à 07:54 -0500, Aniket0987 a écrit :
> Hello Nicolas,
> Here is my pipeline:
> v4l2src device=/dev/video0 do-timestamp=true !

Please avoid using do-timestamp property with v4l2src, this will cause drift and
could even be the source of your troubles.

> image/jpeg,width=1920,height=1080 ! jpegparse ! jpegdec !

You don't need jpegparse here, jpegdec has it's own framing parser. jpegparse is
not ranked (hence not autoplugged) as it has many known defects.

> video/x-raw,format=I420 ! videorate ! video/x-raw,framerate=5/1 !

For live streams, drop-only property on videorate can improve performance,
though it might reduce accuracy.

> videoconvert ! queue leaky=downstream max-size-time=100000000000 !
> openh264enc ! h264parse ! out. splitmuxsink name=mp4mux

As you are using leaky queues, it is quite strange why the v4l2src overrun. That
being said, leaky queues is not strictly needed as v4l2src will kindly drop
frames for you.

> max-size-time=60000000000 max-size-bytes=134217728 location=/tmp/file_ tee
> name=out ! queue ! mp4mux.video

It could be storage jitter though, as storage will buffer for a while until it
absolutely need to write.

> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

More information about the gstreamer-devel mailing list