Comment 114 for bug 290506

Hi folks,

I think parts of this bug were also worked around in libv4l. The last two releases of libv4l in particular address two serious bug, one being the cheese slowness and the other being an issue with uvcvideo driver:
libv4l-0.5.6
------------
* Always do a s_fmt on uvc cams even if this changes nothing, as not doing
  the s_fmt triggers a bug in the uvcvideo driver in kernel <= 2.6.28
  (with certain cams)

libv4l-0.5.5
------------
* Avoid the use of try_fmt as much as possible on UVC cams, instead use the
  results of the enum_framesizes ioctl. This is because:
  1) try_fmt actually causes IO with UVC cams making apps which do lot of
     querrying of device capabilities slow (cheese)
  2) some buggy cams don't like getting lots of UVC video probes and crash
     when they do

I've pushed an updated libv4l to my intrepid ppa at: https://launchpad.net/~lool/+archive

If you see any /regression/ from intrepid's libv4l (0.5.0-3~intrepid1) in cheese or any other app caused by the upgrade to libv4l 0.5.6-1, please notify this bug or notify me. If this update improves things in any way, I'm also interested!

The actual libv4l SRU is currently being prepared in bug #286070, where your comments on the libv4l improvements / regressions are also welcome.