Re: Error message when running cheese

[Filippo Argiolas <fargiolas gnome org>]

On Mon, Jun 21, 2010 at 11:05 PM, Stefan Kost <ensonic hora-obscura de> wrote:
>
> hi,
> Am 09.06.2010 00:09, schrieb lesliek ozemail com au:
>> The output of v4l-info (of whose existence I was unaware till you mentioned
>> it--sorry!) is as follows:
>>
>> ### v4l2 device info [/dev/video0] ###
>> general info
>>     VIDIOC_QUERYCAP
>>       driver                  : "zc3xx"
>>       card                    : "PC Camera"
>>       bus_info                : "usb-0000:00:13.1-1"
>>       version                 : 2.6.0
>>       capabilities            : 0x5000001 [VIDEO_CAPTURE,READWRITE,STREAMING]
>>
>> standards
>>
>> inputs
>>     VIDIOC_ENUMINPUT(0)
>>       index                   : 0
>>       name                    : "zc3xx"
>>       type                    : CAMERA
>>       audioset                : 0
>>       tuner                   : 0
>>       std                     : 0x0 []
>>       status                  : 0x0 []
>>
>> video capture
>>     VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE)
>>       index                   : 0
>>       type                    : VIDEO_CAPTURE
>>       flags                   : 1
>>       description             : "JPEG"
>>       pixelformat             : 0x4745504a [JPEG]
>
> Yes, this is jpeg only. Imho it still works fine, despite the warning and it is
> fixed in never libv4l. I am now wondering why cheese is run with libv4lconvert
> preloaded, maybe it works better without for you.

Hey Stefan,
I don't think cheese runs with libv4lconvert preloaded itself. It's
gst-plugins-good that's compiled with libv4l2 support and
automatically calls to libv4lconvert code to decode everything that
differs from common rgb and yuv formats.
That's the whole point of libv4l support in gstreamer, decode exotic
formats transparently without the user of v4l2src ever noticing.
And cheese wouldn't work at all without it with jpeg cameras as we
support rgb and yuv caps only.

Anyway, fixed in libv4l or not, that error message is (was?) pretty
common and AFAIK it doesn't cause any noticeable issue other than
cluttering the output.

Regards,
Filippo