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

Visual Studio frameRate issue. #14

Open
AndreasRef opened this issue Nov 28, 2016 · 3 comments
Open

Visual Studio frameRate issue. #14

AndreasRef opened this issue Nov 28, 2016 · 3 comments

Comments

@AndreasRef
Copy link

Hi

Thanks to @Mrzl newest pull I am able successfully run the addon on Windows.

However I experience a very low frameRate:
Even though I build the project in release mode (setting settings to Release and x64) the tracker thread framerate is low (3-5 fps), and I get the warning saying I should run the program in release mode. Also the general framerate is unusually high (200-300 fps), which seems a bit strange as well?

Any ideas to what might be causing this?

Setup: Windows 10 - Visual Studio 2015 - of_v0.9.8 / of_v0.9.3

skaermbillede 10

@schwittlick
Copy link
Contributor

hey there,
i've tested a little bit and getting 17fps on the detection. might be related to the fact that i am using an image (320x400px) to do the detection on, which is much smaller in resolution. apparently you can safely scale down the frame you are passing to the detector, as dlib's face detection only uses 80x80px images anyways..
it could be worth a shot to try downscaling the webcam image and then feeding it into the detector.

moreover, ive found an interesting comment here, that states that gcc compiled code will always outperform msvc compiled code. the reason is unknown to me, but seems like it's a fact: cmusatyalab/openface#157 (comment)

the error/warning message there is still due to some osx specific macro that doesn't exist on windows.

marcel

@youandhubris
Copy link

Hi @AndreasRef and @Mrzl ,

Did you get the 'CreateSemaphore not found' error? If so, how did you overcame this?

Thanks!

@joaodafonseca
Copy link

joaodafonseca commented May 19, 2018

Hi all, I'm experiencing the same issue. Even if i run it in Release mode I still get the error/warning message. I also compared with the mac version that runs much faster on release mode and no warning.

Did you guys manage to solve this?

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

4 participants