KSPROPERTY_CAMERACONTROL_PANTILT: values not in arc-seconds as documented

In fact, you can simply compare to the individual pan and tilt properties, which are actually specified in degrees - that is the trivial solution which we have implemented. But that is not the question I was asking. The underlying UVC interface definitely is specified in arcsec. I am trying to understand

• whether the usbvideo.sys simply mis-implements this property, or whether the hardware is inconsistent with the standard. In the former case we might try to access the USB port directly, in the latter this would be a waste of time
• whether there is any other way of getting the information at high resolution position.

Hello @TomQuant ,

To handle this situation, you might consider an approach of dynamically detecting based on the supported value bounds. You could refer to the following implementation approach:

1. Use the IKsControl::KsProperty function with the KSPROPERTY_TYPE_BASICSUPPORT flag to retrieve the KSPROPERTY_STEPPING_LONG structure, which describes the bounds of the Pan/Tilt property.
2. Based on the Bounds.SignedMaximum value, you can make an assessment:
   • If the maximum value is relatively small (e.g., <= 360), it is highly likely that the driver is using degrees.
   • If the maximum value is quite large (e.g., close to 180 * 3600 = 648000), this indicates the driver might be adhering to the documentation and using arc-seconds.
3. Build a logic check to automatically apply the appropriate conversion ratio based on the conditions evaluated in step 2.

In addition, you might also consider submitting a report via the feedback feature directly on the documentation page. You can find the "Was this page helpful?" section with thumbs up/down icons on the right side of the page. Clicking either icon will open a dialog where you can select a reason and use the "Tell us more" box to share information about the inconsistencies in real-world drivers. This could help the Microsoft documentation team consider adding necessary notes, which would better support the developer community in the future.

Hopefully, these suggestions will be helpful for you. If you found my response helpful or informative, you could follow this guide to provide feedback.

Thank you.