Comment 40 for bug 105638

gstreamer-properties doesn't keep custom v4l2 pipelines (and reverts whatever you change in gconf), I got it to work with:

v4l2src ! video/x-raw-yuv,format=(fourcc)UYVY,width=352,height=288
v4l2src ! video/x-raw-yuv,format=(fourcc)UYVY,width=320,height=240

It seems 640x480 has issues (these could be kernelwise, but I can't say)

It seems to me that the camera works great with the module, but gstreamer has issues with the maximum resolution.

A test command that uses lower resolution:

gst-launch-0.10 v4l2src ! video/x-raw-yuv,format=\(fourcc\)UYVY,width=352,height=288 ! ffmpegcolorspace ! ximagesink

Cheese seems to check the camera capabilities and fails, since the camera is reporting to support 640x480 but for some reason it doesn't work well with that resolution...

If cheese permitted custom pipelines we could bypass these issues for now, other gstreamer apps that check on gconf for pipeline info, you can change to the custom pipelines I posted above, but if gstreamer-properties is run they are reverted to the original v4l2src.

The gconf path is /system/gstreamer/0.10/default

The keys
<videosrc>
v4l2src ! video/x-raw-yuv,format=(fourcc)UYVY,width=352,height=288
<videosink>
ffmpegcolorspace ! ximagesink

Should this bug be moved to gstreamer or are the resolution issues related to the module?