Hello, I have now a version of my patch ready for inclusion in Kopete SVN. It is done against the 3.5 stable branch. I don't know if it can be applied seamlessly in the trunk. The patch is available at the following address: <http://www.alexandredenis.net/software/kopete-uvc/kopete-uvc-patch-20060206.tgz>
It adds support for the UVC driver and fixes various webcam-related bugs I encountered in Kopete. Change log: -- add support for MJPEG pixel format. -- implement the "preview image as mirror" feature (tested in MSN but not in Yahoo. However, this is a 1-line change in Yahoo plugin). -- add support for V4L2 controls: contrast, brightness, saturation, whiteness, hue. -- fix various parameters save. This patch supposedly fixes the following bugs: -- 138812: Kopete crashes when configuring webcam -> My webcam is precisely a Quickcam Pro 5000, and now it works. -- 131568: uvcvideo webcam doesn't work -> Duplicate of bug #138812 (same driver: uvc) -- 131822: Webcam image using spca500 driver fills only about 1/4 of the webcam screen, rest are green lines -> (supposedly) caused by parameter "workaround broken driver" saved incorrectly. That's why I disabled the "workaround broken driver" in the first place, but actually the problem comes from parameter save (rationale: in "workaround" mode, the webcam is first detected as V4L1 and the detected format is YUYV; later, the webcam is detected as V4L2 with MJPEG format. However, the picture size is different in YUYV and MJPEG format.) -- 131448: Webcam configuration does not save -> some parameters were actually mixed and some were lost -- 131322: when webcam configuration is called for the first time, Kopete does not properly show webcam -> (supposedly) another symptom of bug #131822 -- 131319: changes in webcam configuration not saved properly -> duplicate of bug #131448 -a. On Wednesday 24 January 2007 10:31, Taupter wrote: > Hi, Alexandre. > > > I'm the maintainer of Kopete's video support. > Thanks for the patch! I'm reviewing it for inclusion in the SVN. > I have a question about your patch. You said you disabled V4L support > if V4L2 was detected. Trying V4L is necessary because if the V4L2 > driver is incomplete (missing functionality) or broken the user has > the option (configurable by the video device control panel) to try to > access the video device in "workaround mode", and some problems with > buggy drivers can be bypassed by this strategy. A V4L2 driver doesn't > have the obligation to have a V4L compatibility layer, so the code > tests it to be sure it will be able to use the device in "workaround > mode" if the user asks to. The sole function of the "workaround mode" > is to do this, so there are no device-specific workaround code and I > advise people to be in touch with the driver's developers to fix > those quirks (once I found a driver that returned BGR images when it > was asked to use GBR or RGB modes), but the size of the image of some > cameras and the MJPEG frames were concerns to be addressed and your > code is _very_ appreciated. > If you have ideas, reasons or strategies that would be applicable in > Kopete's video support please stay in touch with me. I'd love to > discuss about it. The easier way to reach me is sending an email to > [EMAIL PROTECTED] or #kopete (freenode). > > > Thanks and best regards > > > Cláudio Pinheiro _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
