Capture interval - is it constrained to integer values?
Is the capture interval constrained to integer values? I tried to set the interval to 2.5 seconds but it did not accept the value (fails silently). Setting the value to integers works. Is this a Drone hardware limitation or a bug?
Comments
1 comment
When the map is set to time-based capture priority, it uses the camera in interval photo mode, which is restricted to whole numbers by DJI / camera firmware. Because of this limitation, the current algorithm restricts it for time and distance based capture priority, though arguably it could use fractions for distance based capture. Moving to feature requests in that case.
Please sign in to leave a comment.