Troubleshooting the Camera Driver Data Structure Verification Test
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The following table shows troubleshooting tips for the Camera Driver Data Structure Verification test.
| Item | Solution |
|---|---|
Test cases 1301-1304 are failing. |
This test does not verify dynamic frame dropping, only whether the property can be queried or not. Any test failures occur because driver bugs block querying the frame dropping data. |
Test cases 1501-1505 are failing. |
Failures occur because drivers incorrectly handle the getting and setting of video control caps. |
Test cases 1601-1605 are failing. |
This test is only valid if the camera driver supports video compression natively. (Video that is output by the driver is pre-encoded as WMV.) Any test failures occur because the driver fails to retrieve or set these properties if they are reported to be supported. |
General failures |
On test failure, detailed failure information is given about which properties failed and why. Failures occur because of driver bugs when accessing or modifying the properties. Properties which are not supported are reported as skipped. Therefore, when you develop a new driver, it is best to verify that no tests are skipped for properties that are expected to be supported. |
For more troubleshooting help, see Troubleshooting the CETK Tests.