# \[v2 dev\] Milestone 2 - Frame Detection

**URL:** <https://forums.kinograph.cc/t/v2-dev-milestone-2-frame-detection/1578>\
**Category:** v2 Development\
**Created:** [October 17, 2019, 6:18pm UTC](https://forums.kinograph.cc/t/v2-dev-milestone-2-frame-detection/1578 "2019-10-17T18:18:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![cpixip](https://forums.kinograph.cc/user_avatar/forums.kinograph.cc/cpixip/32/852_2.png) [@cpixip](https://forums.kinograph.cc/u/cpixip)\
**Post date:** [December 4, 2019, 2:11pm UTC](https://forums.kinograph.cc/t/v2-dev-milestone-2-frame-detection/1578/4 "2019-12-04T14:11:16Z")

</div>

openCV has quite a few algorithms (optical flow/tracker) which might be able to estimate the shifts you are describing in your video. Some are also reasonably fast.

So one could just do the capture with a mostly free running camera, store the resulting images on disk and align them (calculate your “L”) in a later processing step.

One needs a sufficiently larger overlap between neighbouring captures, slightly more disk space (because of the overlap required between frames) and some additional processing time (from my experience, anything between 300 msec and 1 sec per frame).

---

_[View the full topic](https://forums.kinograph.cc/t/v2-dev-milestone-2-frame-detection/1578)._