|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Toggle Between Two Cameras in Vision Processing
Was there any significant progress by now?
I have tried to use the exact same code earlier this season and got the same error on the Open vi. We now open the camera which we want to use on each switch and the lag is very noticeable. We use 2 Lifecams 3000, one for far shooting and one for close shooting and switching during a match makes the driver wait for the other camera to show an image. We really need a solution for this! Will using a different camera model fix this? Last edited by GuyM142 : 18-03-2016 at 12:41. |
|
#2
|
|||
|
|||
|
Re: Toggle Between Two Cameras in Vision Processing
Quote:
http://www.chiefdelphi.com/forums/sh....php?p=1560711 |
|
#3
|
|||
|
|||
|
Re: Toggle Between Two Cameras in Vision Processing
The good/bad news post is from last season, and I believe fixed. Though I didn't personally verify this, I did file the bug report.
The camera exposure settings for all MS LifeCams seems to be odd on UVC/linux devices. The parameters are described and given ranges that various APIs will use to communicate requested properties to the camera. The MS LifeCam exposure is described as going from 5 to 20,000, with increment of one. That is a lot of range. http://comments.gmane.org/gmane.linu...uvc.devel/5717 That link is to a 2011 forum post about a lifeCam 5000, but explains the same behavior. I does list the magic values, which are twelve geometrically scaled numbers centered around 156. I don't have a camera to try, but if you can use the percentage equivalents, or make your own Set Exposure to avoid the floating point scaling, you can probably make a LifeCam specific Exposure VI work. Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|