Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separating motion frame extraction with its further processing #50

Closed
GoogleCodeExporter opened this issue Jun 22, 2015 · 3 comments
Closed

Comments

@GoogleCodeExporter
Copy link

At this point current motion detection classes are based on the two frames 
difference or on background modeling. In the case if new method for motion 
frame calculation is created, it will be required to create new motion 
detector. It is required to split motion detection classes to a set of 
classes, which calculate motion frames (binary frame with motion regions), 
and set of classes, which process the motion frame further.

Original issue reported on code.google.com by andrew.k...@gmail.com on 20 Feb 2008 at 8:53

@GoogleCodeExporter
Copy link
Author

Original comment by andrew.k...@gmail.com on 12 Jul 2009 at 1:54

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

The enhancement is finished in revision 1003. Will be released in 2.0 version.

Original comment by andrew.k...@gmail.com on 15 Jul 2009 at 9:37

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by andrew.k...@gmail.com on 22 Jul 2009 at 3:50

  • Changed state: Released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant