I would like to request to add setting the camera tilt with floating point precision to the ARDroneSDK.
This request is based on my experience with the SDK and somewhat related to this topic: Camera tilt and pan speed
Here is why:
I like the concept of cinematic looking videos produced by the Bebop Drone. In my eyes a lot complaints about the Bebops camera quality are based on the fact that people expect crisp and smooth video from the drone even though they have no experience in flying, have their drone on maximum speed settings, etc.
So they use flight plan to achieve cinematic videos, which look even better since the POI feature was implemented.
What I disliked was the fact that you don’t have direct control over your drone when using flightplan so you have to decide if you want to fly or to film. Based on this concept I wrote an app that gives you direct control over the drone but still enable you to get smooth cinematic video. But here is the down-side: It is not possible to control the camera in a precise way. Slow movements just look better, so of course I used a floating point value to represent the camera angle (in my case tilt only, I don’t care much for pan) internally. But when I send it to the drone the angle will be rounded to full degrees. This is just too much. When I do a flyby of an object the video looks beautiful, but as soon as I touch the camera tilt my smooth motion will be transformed into a staircased mess. And POI of flight plan doesn’t have that problem, so it must be possible for the stabilization algorithms to handle sub-degree camera angles. So please enable us developers to have more granularity on the camera angles. Even if the 4 bytes of a float are too expensive to send to the drone, at least give as 2 bytes and hundredth of degrees or something like that.
I would like to hear from other developers if I’m alone with this problem or if I somehow missed the documentation on how to send sub-degree camera positions.