GNOME Bugzilla – Bug 672824
[0.11] v4l2src exits with error unless num-buffers set
Last modified: 2012-03-26 15:07:53 UTC
Works: gst-launch-0.11 --gst-debug=v4l*:4 v4l2src io-mode=1 num-buffers=5 ! autovideosink Gives Error: gst-launch-0.11 --gst-debug=v4l*:4 v4l2src io-mode=1 ! autovideosink ERROR: v4l2src gstv4l2src.c:822:gst_v4l2src_fill:<v4l2src0> error processing buffer The same error also occurs in a Python application when calling: Gst.Element.send_event(self.pipeline, Gst.Event.new_eos()); or self.pipeline.set_state(Gst.State.PAUSED) Tested variant pipelines in 0.10.35 which both work without error: gst-launch --gst-debug=v4l*:3 v4l2src num-buffers=5 ! autovideosink gst-launch --gst-debug=v4l*:3 v4l2src ! autovideosink Note: The 0.10.35 tests work in MMAP mode as io-mode is new and the only way I could start a v4l2src in 0.11 per this bug: https://bugzilla.gnome.org/show_bug.cgi?id=672813 See attached for debug info...
Created attachment 210598 [details] Log output from test cases
commit 01838ff97512a8a97c12136f8095e5874ab46d2b Author: Wim Taymans <wim.taymans@collabora.co.uk> Date: Mon Mar 26 15:59:01 2012 +0200 v4l2src: don't error in shutdown Don't log with the ERROR category when we are stopping because we are shutting down. Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=672824