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

Maybe your time is not correct #5

Open
celerychen opened this issue Jun 12, 2017 · 2 comments
Open

Maybe your time is not correct #5

celerychen opened this issue Jun 12, 2017 · 2 comments

Comments

@celerychen
Copy link

Hi, I found that your test code is clock()/10e3, I think this is a bug, maybe is clock()/1e3, so the time maybe is 260ms?

@AlphaQi
Copy link
Owner

AlphaQi commented Jun 12, 2017

Thank you for your problem, but I think your conclusion is wrong, if 260ms per image, the image window will update 3.8 frame per second, that's impossible, you can use waitKey(260) with no face detect , and compare with my program.

@AlphaQi
Copy link
Owner

AlphaQi commented Jun 12, 2017

Hi, thanks again for your problem, I found there is something wrong in my code , I retest my program under windows, the result shows about 68ms per image, I' ll change the README file.

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

No branches or pull requests

2 participants