-
Notifications
You must be signed in to change notification settings - Fork 3
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
CPU usage is rather high for gaming #2
Comments
I didn't test different parameters but I guess that there might be one. Otherwise, you might have to modify the call to the C++ code or check if there's some missing parameter that could be useful in the C# wrapper. My initial idea was to run this program in a raspberry pi or some small computer so it doesn't affect the main CPU... |
OpenFace offers two other less accurate algorithms through the boolean params in FaceModelParameters; unfortunately I can't test them unless I download and rebuild GazeTracker code. |
It works for VS2017. |
I'm right now moving to another city but as soon as I'm stablished I'll try to have a look, is this parameter dependent on the building or can it be added it in the C# wrapper and send it to the unmanaged code? |
Just check the constructor of ImageProcessDataflow, where the FaceModelParameters are created. |
I have an Intel Core i7-7700HQ and I verified that the CPU usage is rather high, with all cores (+HT) being used.
Maybe there is a way to limit the number of threads, or switch to a less intensive algorithm in OpenFace.
Did you test GazeTracker with other FaceModelParameters?
The text was updated successfully, but these errors were encountered: