-
Notifications
You must be signed in to change notification settings - Fork 29
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
Weird offset in image when using this with facetracking #12
Comments
Hi, Are you sure you are using the same image (format, resolution, etc) to feed the tracker and to display in the window? Hugues. |
Hi Hugues. If I run the entirely same program, but using the webcam input it tracks without any issues. It is completely bewildering to me, since it seems to be tracking somehow but not offset with a certain proportionality. I've tried with different setups and I only get this outcome using BlackMagic. |
I was not clear. With ofxBlackMagic you have access to the 'video data' in different formats. Those are things I thinking of without looking at your code, sorry if you have already checked all that. |
Hi Hugues. This is my code below. } //-------------------------------------------------------------- //-------------------------------------------------------------- Here I added cam.getColorPixels() to ofImage i, just to be sure that they were fed the same as the face tracker. The offset is not a constant, but seems to increase the further I move to the right in the picture. Thank you for your help. |
Hey.
This might not be the right place to post this, but I'll give it a shot. I'm trying to use a Black Magic deck link and use the image for facetracking using ofxDlib. For some reason it seems as though it is successfully tracking the face, but drawing the facetracking with some kind of offset.
This isn't a issue when using the built in webcam, which is my reason for posting this here.
Do you know how I could fix this?
Sorry if this issue is unrelated to ofxBlackMagic.
Best regards,
Frederik
The text was updated successfully, but these errors were encountered: