Time-based actions
Hi folks.
For users whose primary use case is photography/videography, there are many times where time-based actions rather than location-based actions would be extremely useful. At the moment, the only such function that I am aware of would be the interval setting on the camera. That allows for only one command (camera photo capture) but there are a number of other time-based scenarios that would make Dronelink more useful and attractive for photographers and videographers. For example, I would love to be able to move along a path with a specified gimble orientation and take an AEB shot every 3 seconds for a set time or distance (even better would be to be able to stop and hover while taking the AEB shot, then continue along the path, but that's a different request). As far as I know, the only way to do this would be to create lots of markers (100-200 for my needs) spaced at a distance calculated using the set speed and desired time between shots, with a camera capture command at each.
Another example use scenario would be to be able to have the drone follow a subject for a specified period of time before stopping the follow and allowing the subject to move off and out of frame, or executing another component. Theoretically, I could do this manually if I was not the subject but if I was the subject, I would not want the controller in the shot and/or might not be able to use it (e.g., driving a car or snowmobile). Loads of other uses for time-based actions.
Hope that makes sense.
Thanks.
Comments
3 comments
This is only possible right now with markers (as you say), or if you want to come to a complete stop, using Destinations with all the AEB commands in the achieved component. There are some other time/distance options in Facade and rotation, but they won't accommodate AEB capture specifically.
Follow is already on the roadmap: https://trello.com/c/VgGWPzok/2-follow
As is triggered capture for maps: https://trello.com/c/yU18o0Eb/92-triggered-capture-for-maps
Thanks Jim. For people doing mostly mapping, site surveys, etc. I would guess that location-based actions are quite sufficient. Being able to say, "Do this for X seconds and then execute the next command" might unlock a lot of creative options for photographers and videographers whether they're looking to create next-level hyperlapse or have more control over cinematic shots and transitions.
I don't do much mapping. How would triggered capture work in Dronelink?
Triggered capture just sends individual camera start capture commands to the drone instead of using intervalometer (this is how Facade already works). Map and Facade, and these options are definitely intended for inspection use cases as you point out, and this is where our focus currently is as most of our paying customers are working on these types of use cases.
Please sign in to leave a comment.