Trying to capture I420 FHD at 5fps on RP4.
Pipeline is as follows, v4l2src device=/dev/video0 io-mode=dmabuf ! video/x-raw,width=1920,height=1080 ! videoconvert ! video/x-raw,format=RGBA ! videorate ! video/x-raw,framerate=5/1 ! queue leaky=downstream ! v4l2h264enc capture-io-mode=dmabuf ! video/x-h264,profile=main ! h264parse splitmuxsink name=mp4mux max-size-time=60000000000 max-size-bytes=134217728 location=/tmp/vid_ sync=false ! queue ! mp4mux.video After a certain time, v4l2src starts dropping everything. 0:10:33.385742774 42 0xa3bfb0 INFO v4l2src gstv4l2src.c:961:gst_v4l2src_create:<v4l2src0> sync to 0:10:30.400000000 out ts 0:10:30.557956381 0:10:33.585610267 42 0xa3bfb0 DEBUG v4l2src gstv4l2src.c:925:gst_v4l2src_create:<v4l2src0> ts: 1:05:16.523210000 now 1:05:16.695278946 delay 0:00:00.172068946 0:10:33.585754746 42 0xa3bfb0 INFO v4l2src gstv4l2src.c:961:gst_v4l2src_create:<v4l2src0> sync to 0:10:30.600000000 out ts 0:10:30.757941863 0:10:33.689999870 42 0xa3bfb0 WARN v4l2bufferpool gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> Dropping truncated buffer, this is likely a driver bug. 0:10:33.690498344 42 0xa3bfb0 WARN v4l2bufferpool gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> Dropping truncated buffer, this is likely a driver bug. 0:10:33.693825940 42 0xa3bfb0 WARN v4l2bufferpool gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> Dropping truncated buffer, this is likely a driver bug. 0:10:33.694079417 42 0xa3bfb0 WARN v4l2bufferpool gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> Dropping truncated buffer, this is likely a driver bug. 0:10:33.697968615 42 0xa3bfb0 WARN v4l2bufferpool gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> Dropping truncated buffer, this is likely a driver bug. 0:10:33.698261555 42 0xa3bfb0 WARN v4l2bufferpool gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> Dropping truncated buffer, this is likely a driver bug. Is there any issue in my pipeline or is it a v4l2 driver bug? -- Sent from: http://gstreamer-devel.966125.n4.nabble.com/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Le mercredi 24 juin 2020 à 22:47 -0500, Aniket0987 a écrit :
> Trying to capture I420 FHD at 5fps on RP4. > Pipeline is as follows, > > v4l2src device=/dev/video0 io-mode=dmabuf ! > video/x-raw,width=1920,height=1080 ! videoconvert ! video/x-raw,format=RGBA > ! videorate ! video/x-raw,framerate=5/1 ! queue leaky=downstream ! > v4l2h264enc capture-io-mode=dmabuf ! video/x-h264,profile=main ! h264parse > splitmuxsink name=mp4mux max-size-time=60000000000 max-size-bytes=134217728 > location=/tmp/vid_ sync=false ! queue ! mp4mux.video > > After a certain time, v4l2src starts dropping everything. > > 0:10:33.385742774 42 0xa3bfb0 INFO v4l2src > gstv4l2src.c:961:gst_v4l2src_create:<v4l2src0> sync to 0:10:30.400000000 out > ts 0:10:30.557956381 > 0:10:33.585610267 42 0xa3bfb0 DEBUG v4l2src > gstv4l2src.c:925:gst_v4l2src_create:<v4l2src0> ts: 1:05:16.523210000 now > 1:05:16.695278946 delay 0:00:00.172068946 > 0:10:33.585754746 42 0xa3bfb0 INFO v4l2src > gstv4l2src.c:961:gst_v4l2src_create:<v4l2src0> sync to 0:10:30.600000000 out > ts 0:10:30.757941863 > 0:10:33.689999870 42 0xa3bfb0 WARN v4l2bufferpool > gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> > Dropping truncated buffer, this is likely a driver bug. > 0:10:33.690498344 42 0xa3bfb0 WARN v4l2bufferpool > gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> > Dropping truncated buffer, this is likely a driver bug. > 0:10:33.693825940 42 0xa3bfb0 WARN v4l2bufferpool > gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> > Dropping truncated buffer, this is likely a driver bug. > 0:10:33.694079417 42 0xa3bfb0 WARN v4l2bufferpool > gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> > Dropping truncated buffer, this is likely a driver bug. > 0:10:33.697968615 42 0xa3bfb0 WARN v4l2bufferpool > gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> > Dropping truncated buffer, this is likely a driver bug. > 0:10:33.698261555 42 0xa3bfb0 WARN v4l2bufferpool > gstv4l2bufferpool.c:2066:gst_v4l2_buffer_pool_process:<v4l2src0:pool:src> > Dropping truncated buffer, this is likely a driver bug. > > Is there any issue in my pipeline or is it a v4l2 driver bug? The warning from gst is correct, it's a driver bug. But as you can see, it has a workaround. The driver I made this workaround for is now fixed in mainline kernel. > > > > -- > Sent from: http://gstreamer-devel.966125.n4.nabble.com/ > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Okay. So this has been fixed in v4l2-core? or are we talking about gstreamer
1.17.1. -- Sent from: http://gstreamer-devel.966125.n4.nabble.com/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Le lundi 29 juin 2020 à 01:57 -0500, Aniket0987 a écrit :
> Okay. So this has been fixed in v4l2-core? or are we talking about gstreamer > 1.17.1. v4l2-core, but I tried to add a workaround in gstreamer master, but there is a limit of what we can do about it in userland. > > > > -- > Sent from: http://gstreamer-devel.966125.n4.nabble.com/ > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
If this is fixed in v4l2-core I believe it will come out with the next linux
kernel release, correct me if otherwise. Is there any other way to upgrade v4l2? -- Sent from: http://gstreamer-devel.966125.n4.nabble.com/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Le sam. 4 juill. 2020 07 h 45, Aniket0987 <[hidden email]> a écrit : If this is fixed in v4l2-core I believe it will come out with the next linux The next kernel release is very ambiguous, since there is often a certain lag between the official release and distro / embedded board being updated. Also, bug fixes can be backported.
_______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Free forum by Nabble | Edit this page |