[gstreamer-bugs] [Bug 338818] [PLUGIN-MOVE] v4l2src from bad to good

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=338818
 GStreamer | gst-plugins-good | Ver: HEAD CVS





------- Comment #12 from Thomas Vander Stichele  2006-09-02 13:45 UTC -------
Stefan,

You mention a problem yourself in comment 9, but did not get a reply - does
that mean you don't think this is a problem that needs to be solved first ?

To sponsor the move you need to take the checklist from moving-plugins and
verify that these items are taken care of.


Since this was lacking from this bug report, I took a look at it myself.


The first thing I did was the same as you:

[gst-head] [thomas at otto v4l2]$ gst-launch v4l2src ! videoscale ! videorate !
video/x-raw-rgb,width=320,height=240,framerate='(fraction)'15/1 ! ximagesink
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /pipeline0/v4l2src0: Error getting capabilities
'/dev/video0': 22, Invalid argument. It isn't a v4l2 driver. Check if it is a
v4l1 driver

Additional debug info:
v4l2_calls.c(58): gst_v4l2_get_capabilities (): /pipeline0/v4l2src0:
system error: Invalid argument
Setting pipeline to NULL ...
FREEING pipeline ...

This is a downright terrible error message.  Imagine a recording application
throwing up a dialog box with this text.  What does 22 mean ? What does Invalid
argument mean ? Who cares ?

So I looked through the code and saw a bunch more like these.  Since the first
thing I try with this plugin is something that fails the checklist, I assume no
one has done a full review yet, and this should be done first before it can be
approved for move.

Anyone willing ?


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.