|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#16
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
Last edited by techhelpbb : 18-03-2016 at 15:53. |
|
#17
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
|
|
#18
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
I think there's something more going on. Using the Microsoft lifecam software you can get varying exposure with out it appearing so binary.
But I don't have more to contribute than that. One option we've considered is running a monitor/keyboard with the Kangaroo and having settings for the lifecam set on that. As long as the lifecam doesn't get power cycled, it maintains its exposure and brightness settings. |
|
#19
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
Much like this custom driver for the PS3 Eye: https://codelaboratories.com/products/eye/driver/ However most of the video capture related software in use on the Linux RoboRIO depend on V4L's ability to configure said cameras (GRIP uses OpenCV which uses V4L). As Billbo911 has demonstrated above - on a bunch of models of the Microsoft cameras it doesn't work like you would expect. The V4L project is the core common solution to USB webcam support for Linux systems. If that doesn't work for a particular camera it either needs to be addressed there or a lot of development work would need to happen to create another framework unique to a camera. Course a brighter light or tinted lens as a hack works as well. Last edited by techhelpbb : 18-03-2016 at 17:44. |
|
#20
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
|
|
#21
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
Last edited by techhelpbb : 18-03-2016 at 17:57. |
|
#22
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
To the person that recommended that we the lifecam software to set exposure, what software did you mean and where can we get it? |
|
#23
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Running late and my Raspbian SD card is acting up...
So I put my ODroid XU4 with MATE on one of the older Microsoft LifeCam VX-6000 cameras I have. My 'uname -a' on there is as below: Code:
Linux odroid 3.10.92-71 #1 SMP PREEMPT Fri Dec 18 00:38:54 BRST 2015 armv7l armv7l armv7l GNU/Linux Code:
v4l2-ctl -l
User Controls
brightness (int) : min=0 max=255 step=1 default=127 value=127 flags=slider
contrast (int) : min=0 max=255 step=1 default=127 value=127 flags=slider
saturation (int) : min=0 max=255 step=1 default=127 value=127 flags=slider
hue (int) : min=-180 max=180 step=1 default=0 value=0 flags=slider
red_balance (int) : min=0 max=127 step=1 default=40 value=40 flags=slider
blue_balance (int) : min=0 max=127 step=1 default=40 value=40 flags=slider
gamma (int) : min=0 max=255 step=1 default=16 value=16 flags=slider
exposure (int) : min=0 max=6016 step=1 default=51 value=51 flags=inactive
gain_automatic (bool) : default=1 value=1 flags=update
gain (int) : min=0 max=28 step=1 default=0 value=0
horizontal_flip (bool) : default=0 value=0
vertical_flip (bool) : default=0 value=0
JPEG Compression Controls
compression_quality (int) : min=50 max=90 step=1 default=80 value=80
brightness (int) : min=0 max=255 step=1 default=127 value=127 flags=slider
contrast (int) : min=0 max=255 step=1 default=127 value=127 flags=slider
saturation (int) : min=0 max=255 step=1 default=127 value=127 flags=slider
hue (int) : min=-180 max=180 step=1 default=0 value=0 flags=slider
red_balance (int) : min=0 max=127 step=1 default=40 value=40 flags=slider
blue_balance (int) : min=0 max=127 step=1 default=40 value=40 flags=slider
gamma (int) : min=0 max=255 step=1 default=16 value=16 flags=slider
exposure (int) : min=0 max=6016 step=1 default=51 value=51 flags=inactive
gain_automatic (bool) : default=1 value=1 flags=update
gain (int) : min=0 max=28 step=1 default=0 value=0
horizontal_flip (bool) : default=0 value=0
vertical_flip (bool) : default=0 value=0
root@odroid:/home/odroid# v4l2-ctl --set-ctrl gain_automatic=0
These series of commands fixed it for me: Code:
v4l2-ctl --set-ctrl gain_automatic=0 v4l2-ctl --set-ctrl gain=10 The ranges are now reasonable for this older camera. I will order the LifeCam 3000 HD to experiment further. Below are the options from V4L presented for the Logitech C920 on the same embedded system: Code:
v4l2-ctl -l
brightness (int) : min=0 max=255 step=1 default=128 value=128
contrast (int) : min=0 max=255 step=1 default=128 value=128
saturation (int) : min=0 max=255 step=1 default=128 value=128
white_balance_temperature_auto (bool) : default=1 value=1
gain (int) : min=0 max=255 step=1 default=0 value=0
power_line_frequency (menu) : min=0 max=2 default=2 value=2
white_balance_temperature (int) : min=2000 max=6500 step=1 default=4000 value=2397 flags=inactive
sharpness (int) : min=0 max=255 step=1 default=128 value=128
backlight_compensation (int) : min=0 max=1 step=1 default=0 value=0
exposure_auto (menu) : min=0 max=3 default=3 value=3
exposure_absolute (int) : min=3 max=2047 step=1 default=250 value=250 flags=inactive
exposure_auto_priority (bool) : default=0 value=1
pan_absolute (int) : min=-36000 max=36000 step=3600 default=0 value=0
tilt_absolute (int) : min=-36000 max=36000 step=3600 default=0 value=0
focus_absolute (int) : min=0 max=250 step=5 default=0 value=0 flags=inactive
focus_auto (bool) : default=1 value=1
zoom_absolute (int) : min=100 max=500 step=1 default=100 value=100
led1_mode (menu) : min=0 max=3 default=0 value=3
led1_frequency (int) : min=0 max=255 step=1 default=0 value=0
brightness (int) : min=0 max=255 step=1 default=128 value=128
contrast (int) : min=0 max=255 step=1 default=128 value=128
saturation (int) : min=0 max=255 step=1 default=128 value=128
white_balance_temperature_auto (bool) : default=1 value=1
gain (int) : min=0 max=255 step=1 default=0 value=0
power_line_frequency (menu) : min=0 max=2 default=2 value=2
white_balance_temperature (int) : min=2000 max=6500 step=1 default=4000 value=2397 flags=inactive
sharpness (int) : min=0 max=255 step=1 default=128 value=128
backlight_compensation (int) : min=0 max=1 step=1 default=0 value=0
Last edited by techhelpbb : 20-03-2016 at 16:23. |
|
#24
|
|||
|
|||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
Quote:
http://www.chiefdelphi.com/forums/sh....php?p=1560711 |
|
#25
|
|||
|
|||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
http://comments.gmane.org/gmane.linu...uvc.devel/5717
This is from 2011, and for a slightly different camera, but it seems like this is how MS built their UVC descriptor. The WPILib wrapper turns all properties into a percentage, so these sorta-geometric scalings will be even more difficult to specify, but apparently there are special numbers that set exposure. Greg McKaskle |
|
#26
|
||||
|
||||
|
Re: USB MS Lifecam HD 3000 Exposure Issues
I finally had a chance to put the PS3 Eye and a Microsoft LifeCam HD-3000 on my ODroid XU4:
PS3 Eye: Code:
v4l2-ctl -l
User Controls
brightness (int) : min=0 max=255 step=1 default=0 value=0 flags=slider
contrast (int) : min=0 max=255 step=1 default=32 value=32 flags=slider
saturation (int) : min=0 max=255 step=1 default=64 value=64 flags=slider
hue (int) : min=-90 max=90 step=1 default=0 value=0 flags=slider
white_balance_automatic (bool) : default=1 value=1
exposure (int) : min=0 max=255 step=1 default=120 value=120 flags=inactive, volatile
gain_automatic (bool) : default=1 value=1 flags=update
gain (int) : min=0 max=63 step=1 default=20 value=20 flags=inactive, volatile
horizontal_flip (bool) : default=0 value=0
vertical_flip (bool) : default=0 value=0
power_line_frequency (menu) : min=0 max=1 default=0 value=0
sharpness (int) : min=0 max=63 step=1 default=0 value=0 flags=slider
Camera Controls
auto_exposure (menu) : min=0 max=1 default=0 value=0 flags=update
brightness (int) : min=0 max=255 step=1 default=0 value=0 flags=slider
contrast (int) : min=0 max=255 step=1 default=32 value=32 flags=slider
saturation (int) : min=0 max=255 step=1 default=64 value=64 flags=slider
hue (int) : min=-90 max=90 step=1 default=0 value=0 flags=slider
white_balance_automatic (bool) : default=1 value=1
exposure (int) : min=0 max=255 step=1 default=120 value=120 flags=inactive, volatile
gain_automatic (bool) : default=1 value=1 flags=update
gain (int) : min=0 max=63 step=1 default=20 value=20 flags=inactive, volatile
horizontal_flip (bool) : default=0 value=0
vertical_flip (bool) : default=0 value=0
power_line_frequency (menu) : min=0 max=1 default=0 value=0
sharpness (int) : min=0 max=63 step=1 default=0 value=0 flags=slider
Code:
v4l2-ctl -l
brightness (int) : min=30 max=255 step=1 default=133 value=133
contrast (int) : min=0 max=10 step=1 default=5 value=2
saturation (int) : min=0 max=200 step=1 default=83 value=83
white_balance_temperature_auto (bool) : default=1 value=1
power_line_frequency (menu) : min=0 max=2 default=2 value=2
white_balance_temperature (int) : min=2800 max=10000 step=1 default=4500 value=2800 flags=inactive
sharpness (int) : min=0 max=50 step=1 default=25 value=0
backlight_compensation (int) : min=0 max=10 step=1 default=0 value=0
exposure_auto (menu) : min=0 max=3 default=1 value=3
exposure_absolute (int) : min=5 max=20000 step=1 default=156 value=156 flags=inactive
pan_absolute (int) : min=-201600 max=201600 step=3600 default=0 value=201600
tilt_absolute (int) : min=-201600 max=201600 step=3600 default=0 value=0
zoom_absolute (int) : min=0 max=10 step=1 default=0 value=0
brightness (int) : min=30 max=255 step=1 default=133 value=133
contrast (int) : min=0 max=10 step=1 default=5 value=2
saturation (int) : min=0 max=200 step=1 default=83 value=83
white_balance_temperature_auto (bool) : default=1 value=1
power_line_frequency (menu) : min=0 max=2 default=2 value=2
white_balance_temperature (int) : min=2800 max=10000 step=1 default=4500 value=2800 flags=inactive
sharpness (int) : min=0 max=50 step=1 default=25 value=0
backlight_compensation (int) : min=0 max=10 step=1 default=0 value=0
Those values only work at normal room lighting. If you light the room up abnormally bright - you still see some exposure control- but the camera frame rate is impacted. Basically it's like the shutter speed on a hand held film or digital camera. So guess what: if you put sunglasses in front of the camera lens it lowers the light level and the frame rate increases. I played around a bit, but to be honest, I can't get to the settings from that interface to alter the camera behavior and I can in Windows. Last edited by techhelpbb : 27-03-2016 at 22:33. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|