Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

detectMultiScale speed

Hello,
I've recently upgraded to OpenCV 3.0 and found out, that (atleast in my case) the detectMultiScale overload that takes reject_levels and level_weights parameters is twice as fast as the other two (the one taking the num_detections vector and the default one). I've tested this many times on a large enough sample of images. Has it happened to any of you?
I've looked through the source code and it seems that the only difference it comes to is in CascadeClassifierInvoker and doesn't look like it should alter the speed in such a way it does.