Configuración Webcam

Configuración Webcam

Hola. Tengo una Webcam Showtime Plus de NGS. He instalado mi Ubuntu 6.06 actualizada. Mi Webcam me la detecta y parece funcionar.

Los modulos estan activados y la Webcam con el piloto encendido de que funciona, pero por ejemplo cuando uso el Amsn me dice que no hay dispositivos instalados, o el gnoometing que no se encuentra el /dev/video0.

He seguido las instrucciones de instalacion del drivers de la Web Oficial y nada. Despues con el comando "modconf" un dia me decidi a probar cargar otro modulo y cargue el 0v518. Entonces ya todos los software de uso Webcam funcionaban. La cam me funcionaba a la perfeccion, me la detectaban como USB Camera, el problema que tengo ahora es que no se ve nada. Se ve muchos colores que cambian continuamente y sobre todo el verde.

¿Puede ser problema de la compresion o algo? Por favor intenten ayudarme, si consigo instalar esta Webcam podre emigrar a Linux y dejar el software propietario de Windows.

La Web oficial de los drivers es: http://alpha.dyndns.org/ov511/download.html

Muchas Gracias a todos.

Re: Configuración Webcam

He estado mirando en un archivo TXT y visto algunos parametros de configuración del módulo de mi CAM (ov511). ¿Creeis que puede ser alguno de estos el que debo de modificar el por el cual se ven muchos colores por la cam pero no me veo yo?

Los modulos son estos:

MODULE PARAMETERS:

You can set these with: insmod ov511 NAME=VALUE
There is currently no way to set these on a per-camera basis.

NAME: autobright
TYPE: integer (Boolean)
DEFAULT: 1
DESC: Brightness is normally under automatic control and can't be set
manually by the video app. Set to 0 for manual control.

NAME: autoexp
TYPE: integer (Boolean)
DEFAULT: 1
DESC: Auto Exposure Control enable.

NAME: debug
TYPE: integer (0-6)
DEFAULT: 3
DESC: Sets the threshold for printing debug messages. The higher the value,
the more is printed. The levels are cumulative, and are as follows:
0=no debug messages
1=init/detection/unload and other significant messages
2=some warning messages
3=config/control function calls
4=most function calls and data parsing messages
5=highly repetitive mesgs

NAME: snapshot
TYPE: integer (Boolean)
DEFAULT: 0
DESC: Set to 1 to enable snapshot mode. read()/VIDIOCSYNC will block until
the snapshot button is pressed. Note: enabling this mode disables
/proc/video/ov511/<minor#>/button

NAME: cams
TYPE: integer (1-4 for OV511, 1-31 for OV511+)
DEFAULT: 1
DESC: Number of cameras allowed to stream simultaneously on a single bus.
Values higher than 1 reduce the data rate of each camera, allowing two
or more to be used at once. If you have a complicated setup involving
both OV511 and OV511+ cameras, trial-and-error may be necessary for
finding the optimum setting.

NAME: compress
TYPE: integer (Boolean)
DEFAULT: 0 (OV511) or 1 (OV51
DESC: Set this to 1 to turn on the camera's compression engine. This can
potentially increase the frame rate at the expense of quality, if you
have a fast CPU. OV518 cameras require compression, so this option can't
be disabled with them.

NAME: dumppix
TYPE: integer (0-2)
DEFAULT: 0
DESC: Dumps raw pixel data and skips post-processing and format conversion.
It is for debugging purposes only. Options are:
0: Disable (default)
1: Dump raw data from camera, excluding headers and trailers
2: Dumps data exactly as received from camera

NAME: led
TYPE: integer (0-2)
DEFAULT: 1 (Always on)
DESC: Controls whether the LED (the little light) on the front of the camera
is always off (0), always on (1), or only on when driver is open (2).
This is not supported with the OV511, and might only work with certain
cameras (ones that actually have the LED wired to the control pin, and
not just hard-wired to be on all the time).

NAME: dump_bridge
TYPE: integer (Boolean)
DEFAULT: 0
DESC: Dumps the bridge (OV511[+] or OV51+]) register values to the system
log. Only useful for serious debugging/development purposes.

NAME: printph
TYPE: integer (Boolean)
DEFAULT: 0
DESC: Setting this to 1 will dump the first 12 bytes of each isoc frame. This
is only useful if you are trying to debug problems with the isoc data
stream (i.e.: camera initializes, but vidcat hangs until Ctrl-C). Be
warned that this dumps a large number of messages to your kernel log.

NAME: phy, phuv, pvy, pvuv, qhy, qhuv, qvy, qvuv
TYPE: integer (0-63 for phy and phuv, 0-255 for rest)
DEFAULT: OV511 default values
DESC: These are registers 70h - 77h of the OV511, which control the
prediction ranges and quantization thresholds of the compressor, for
the Y and UV channels in the horizontal and vertical directions. See
the OV511 or OV511+ data sheet for more detailed descriptions. These
normally do not need to be changed.

NAME: lightfreq
TYPE: integer (0, 50, or 60)
DEFAULT: 0 (use sensor default)
DESC: Sets the sensor to match your lighting frequency. This can reduce the
appearance of "banding", i.e. horizontal lines or waves of light and
dark that are often caused by artificial lighting. Valid values are:
0 - Use default (depends on sensor, most likely 60 Hz)
50 - For European and Asian 50 Hz power
60 - For American 60 Hz power

NAME: bandingfilter
TYPE: integer (Boolean)
DEFAULT: 0 (off)
DESC: Enables the sensorŽs banding filter exposure algorithm. This reduces
or stabilizes the "banding" caused by some artificial light sources
(especially fluorescent). You might have to set lightfreq correctly for
this to work right. As an added bonus, this sometimes makes it
possible to capture your monitorŽs output.

NAME: fastset
TYPE: integer (Boolean)
DEFAULT: 0 (off)
DESC: Allows picture settings (brightness, contrast, color, and hue) to take
effect immediately, even in the middle of a frame. This reduces the
time to change settings, but can ruin frames during the change. Only
affects OmniVision sensors.

NAME: force_palette
TYPE: integer
DEFAULT: OV511/OV511+: 0 (off); OV518/OV518+: 15 (YUV420P)
DESC: Forces the palette (color format) to a specific value. If an
application requests a different palette, it will be rejected, thereby
forcing it to try others until it succeeds. This is useful for forcing
greyscale mode with a color camera, for example. Supported modes are:
0 (Allows all the following formats)
1 VIDEO_PALETTE_GREY (Linear greyscale)
10 VIDEO_PALETTE_YUV420 (YUV 4:2:0 Planar)
15 VIDEO_PALETTE_YUV420P (YUV 4:2:0 Planar, same as 10)

NAME: tuner
TYPE: integer
DEFAULT: -1 (autodetect)
DESC: This sets the exact type of the tuner module in a device. This is set
automatically based on the custom ID of the OV511 device. In cases
where this fails, you can override this auto-detection. Please see
linux/drivers/media/video/tuner.h for a complete list.

NAME: backlight
TYPE: integer (Boolean)
DEFAULT: 0 (off)
DESC: Setting this flag changes the exposure algorithm for OmniVision sensors
such that objects in the camera's view (i.e. your head) can be clearly
seen when they are illuminated from behind. It reduces or eliminates
the sensor's auto-exposure function, so it should only be used when
needed. Additionally, it is only supported with the OV6620 and OV7620.

NAME: unit_video
TYPE: Up to 16 comma-separated integers
DEFAULT: 0,0,0... (automatically assign the next available minor(s))
DESC: You can specify up to 16 minor numbers to be assigned to ov511 devices.
For example, "unit_video=1,3" will make the driver use /dev/video1 and
/dev/video3 for the first two devices it detects. Additional devices
will be assigned automatically starting at the first available device
node (/dev/video0 in this case). Note that you cannot specify 0 as a
minor number. This feature requires kernel version 2.4.5 or higher.

NAME: remove_zeros
TYPE: integer (Boolean)
DEFAULT: 0 (do not skip any incoming data)
DESC: Setting this to 1 will remove zero-padding from incoming data. This
will compensate for the blocks of corruption that can appear when the
camera cannot keep up with the speed of the USB bus (eg. at low frame
resolutions). This feature is always enabled when compression is on.

NAME: mirror
TYPE: integer (Boolean)
DEFAULT: 0 (off)
DESC: Setting this to 1 will reverse ("mirror") the image horizontally. This
might be necessary if your camera has a custom lens assembly. This has
no effect with video capture devices.

NAME: i2c_clockdiv
TYPE: integer (0-255)
DEFAULT: 1 (46.75 KHz)
DESC: This allows you to slow the I2C clock down for devices that can't
support the full rate. Most cameras don't need this, but you might if
you are using custom hardware, or if your camera doesn't work and you
see I2C errors in your syslog.

The clock is determined by the formula:

I2C_bit_rate = 93.5 Khz / (i2c_clockdiv + 1)

This was set to 0 (93.5 KHz) in older drivers. If that setting works
but the default doesn't, please report it to me.

NOTE: OV518/OV518+ cameras do not implement this module parameter

NAME: dev_hint
TYPE: 0-16 comma-separated strings
DEFAULT: N/A (automatically assign minors (/dev/video nodes))
DESC: This allows you to force cameras with specified custom IDs to register
with specific minor numbers. If the minor is in use, the unit_video
parameter will be tried next, and if none of those is free, the next
available one will be assigned.

Syntax: c<custom_id>:<minor>[,c<custom_id>:<minor>]...

Example: Assign camera with custom ID 21 (Creative Webcam 3) to
/dev/video4, and assign camera with custom ID 0 to /dev/video1:

dev_hint=c21:4,c0:1

NAME: v4l2
TYPE: integer (Boolean)
DEFAULT: 0 (disabled)
DESC: This enables Video4Linux2 support, if you have a kernel that supports
it. Driver support is incomplete, so there is no reason to do that yet.

Note: V4L2 custom controls and most other ioctls are always supported,
regardless of this setting. This setting just enables VIDIOC_QUERYCAP.