Maybe not a bug but another failed mission...
I was trying the mapping component again and used the community component to start the video, and got this failure right after takeoff.
Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
9 comments
Not sure which component you are referring to but the original author may not have designed it with your drone in mind. You either need to mark the resolution command as not required, or modify to work with your hardware.
It just does this, and I am using a Mavic Air. Should it work?
Not sure, you may need to change it to 23.976 FPS. Basically it's trial and error to see what the DJI SDK accepts on a per drone basis.
That is probably it.
The specs on the DJI website say "24" but I bet it is really 23.976.
I vote to make Dronelink display 24, 25, 30, 50, and 60 but if someone selects 24, it really requests 24.976. If someone selects 30, it requests 29.97. If someone selects 60, it requests 59.94. This is what the Go4, most all camera, and the other apps do and people are used to that.
This will eliminate 99% of these issues that are hard to deal with in real time in the field from a phone.
Unfortunately it's not that simple. The DJI SDK has both values for each pair of frame rates in the API, and there is no documentation on which of each pair should be used for which drone, hence the trial and error.
You can see here:
https://developer.dji.com/api-reference/ios-api/Components/Camera/DJICamera.html?search=djicameravideoframerate&i=0&#djicamera_djicameravideoframerate_inline
I suspect that all DJI drones support 23.976, 29.97, and 59.94 but only a few support 24.0, 30.0, and 60.0.
You are providing access to moves that virtually no one uses, but are very easy to use by mistake and get a failed mission. All other apps hide these modes.
If other members of the community are willing to perform the testing and produce a dataset that confirms this, we would be happy to hide the appropriate options.
I've started the work on building a dataset. Check out this thread for more info.
https://support.dronelink.com/hc/en-us/community/posts/360037551214-Verification-of-video-recording-fps
Please sign in to leave a comment.