Re: [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
- From: Kurt Stephens <ks kurtstephens com>
- To: Damien Sandras <dsandras seconix com>
- Cc: ks video kurtstephens com, gnomemeeting-list gnome org, bdirks pacbell net, cluenin1 bigred unl edu
- Subject: Re: [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
- Date: Mon, 01 Jul 2002 19:13:58 -0500
Ok, now I understand: gnomemeeting is asking for 176x144 from the driver
, the driver is returning "OK" and not giving back 176x144 frames. That
is definitely a bug.
Thanks All,
Kurt Stephens
Damien Sandras wrote:
On Mon, Jul 01, 2002 at 04:50:33PM -0500, Kurt Stephens wrote:
Isn't the driver returning the frames in the resolution as supported by
the camera? Or is the driver misreporting the dimensions of the
frames from the ioctl() call? Not supporting an application-specific
I don't know the behavior of the driver...
(H.261) format does not necessarly make the driver buggy, unless that is
It has never been said that H.261 was an application specific format. H.261
is a codec. What I said is that, apparently, the driver didn't support
the QCIF size (176x144), which is not application-specific. Not supporting
it is not a bug, but apparently, it doesn't report any error when you
request that unsupported size, but instead gives a broken image.
part of the V4L specification (i.e. a set of lowest common denominator
formats must be supported for a V4L device).
Making the application handle more device formats makes the application
work with more drivers. If I add scaling or padding code to
gnomemeeting would it allow it to use more devices. If I add scaling or
padding code to ultracam.c, it only adds functionality to that device.
Or does V4L2 handle this issue?
You misunderstood the problem, please read above and the preceding mail.
The problem is not with scaling or padding. GnomeMeeting already does
padding. The problem with the driver is that it doesn't support (apparently)
the QCIF size, but instead of reporting an error when an user program tries
to use that size, it doesn't report any error, but sends a broken image.
BTW: gcqcam-0.9 does not work with this driver either; I wonder if it
makes the same assumptions about frame dimensions? It opens the device
GnomeMeeting only assumes that if it ask for 176x144, and if the driver
reports it is ok, then it can use it.
but does not seem to honor the format that the device supports and/or
reports; I get the same type of bogus display.
I'm trying to figure out where my effort is best directed.
Damien
- References:
- [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
- Re: [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
- Re: [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
- Re: [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
- Re: [GnomeMeeting-list] IBM Ultraport II Cam and gnomemeeting 0.85.1, RH 7.3, kernel 2.4.18-3
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]