[gstreamer-bugs] [Bug 467214] New: Could not get buffers from device '/dev/video0'

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=467214

  GStreamer | gst-plugins-good | Ver: HEAD CVS
           Summary: Could not get buffers from device '/dev/video0'
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: hongyang at redflag-linux.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


$> gst-launch-0.10 v4l2src ! ffmpegcolorspace ! xvimagesink
Setting pipeline to PAUSED ...
0:00:00.118412000 16414 0x804e050 WARN               v4l2src
v4l2src_calls.c:1025:gst_v4l2src_capture_init:<v4l2src0> error: Could not get
buffers from device '/dev/video0'.
0:00:00.118538000 16414 0x804e050 WARN               v4l2src
v4l2src_calls.c:1025:gst_v4l2src_capture_init:<v4l2src0> error: error
requesting 0 buffers: Cannot allocate memory
Pipeline is live and does not need PREROLL ...
ERROR: from element /pipeline0/v4l2src0: Could not get buffers from device
'/dev/video0'.
Additional debug info:
v4l2src_calls.c(1025): gst_v4l2src_capture_init (): /pipeline0/v4l2src0:
error requesting 0 buffers: Cannot allocate memory
ERROR: pipeline doesn't want to preroll.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...

If I give a parameter "queue-size=2" to the v4l2src, the pipeline works
smoothly. Why v4l2src doesn't work with default parameter (queue-size=2)?

$> gst-launch-0.10 v4l2src queue-size=2 ! ffmpegcolorspace ! xvimagesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
0:00:00.810488000 16490 0x804e050 WARN              pipeline
gstpipeline.c:491:gst_pipeline_change_state:<pipeline0> failed to query
pipeline latency
New clock: GstSystemClock
0:00:03.141901000 16490 0x8066610 WARN           xvimagesink
xvimagesink.c:1199:gst_xvimagesink_handle_xevents:<xvimagesink0> error: Output
window was closed
ERROR: from element /pipeline0/xvimagesink0: Output window was closed
Additional debug info:
xvimagesink.c(1199): gst_xvimagesink_handle_xevents (): /pipeline0/xvimagesink0
Execution ended after 2331573000 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=467214.