- From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jun 2017 11:16:55 +0000
- To: public-media-capture-logs@w3.org
@anssiko I would vote for degrees. Most of the motorized heads or servo motors express rotation values in degrees (or radians). Easier to understand and use for web developers. Also, windows uses degrees for [pan](https://msdn.microsoft.com/en-us/library/windows/desktop/dd376320(v=vs.85).aspx), [roll](https://msdn.microsoft.com/en-us/library/windows/desktop/dd376325(v=vs.85).aspx) and [tilt](https://msdn.microsoft.com/en-us/library/windows/desktop/dd376328(v=vs.85).aspx) for user space APIs and same units on the 'driver' level ([tilt](https://msdn.microsoft.com/library/windows/hardware/ff564454), [roll](https://msdn.microsoft.com/en-us/library/windows/hardware/ff564432(v=vs.85).aspx), [pan](https://msdn.microsoft.com/en-us/library/windows/hardware/ff564424(v=vs.85).aspx)). If someone would like to use Image Capture API e.g., for astrophotography and HW supports fine step increments, 15 decimal places (double) should be enough to represent fractions of a degree / arc-second. @dsanders11 BTW, why just Pan and Tilt without Roll? I have a camera where pan, tilt and roll can be controlled separately. Also, I think it would be better to specify order for applying 'rotation' constraints, so that vendors can implement interoperable API (pan-tilt-roll, zyx). -- GitHub Notification of comment by alexshalamov Please view or discuss this issue at https://github.com/w3c/mediacapture-image/pull/182#issuecomment-308702140 using your GitHub account
Received on Thursday, 15 June 2017 11:17:02 UTC