-
Notifications
You must be signed in to change notification settings - Fork 1
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
Can't set camera above 640p. (Help- This camera can peform higher then 720p..) #14
Comments
Hello there. Thank you for your report. The reason Facetracker potentially shows lower resolutions and frame rates than what is actually supported by the webcam is due to OpenSeeFace itself. Facetracker can only tell OpeSeeFace which camera to use, which resolution and at how much frames per second. Unfortunately I can not tell OSF the video codec it should actually use for capturing the frames from the webcam. While a webcam might in theory support higher resolutions at a certain video codec (usually this is MJPEG) it can happen that the webcam reports the RAW video format and it's supported video formats using this codec first. While OSF does not allow for specifying the video codec it will always uses the very first reported video codec. For example my webcam supports 1920x1080 @ 30 fps using MJPEG You can counter test this like this, inside the Facetracker flatpak there is a pre-compiled OpenSeeFace binary which in theory should run outside of flatpak on the host. You can find it at:
-W is the width of the video Here is an example of my 1080p@30fps camera (which only supports this frame rate using MJPEG but here is the result using OSF): Bildschirmaufnahme_20240914_102925.webmIf you can in fact use higher resolutions and frame rates and the video is still fluent in a VTubbing application let me now. |
Hm, yes I see. I think I need to add some debug info menu button to Facetracker to get all video formats found by Facetracker before it filtered them for use with OpenSeeFace. |
Let me know when your able to patch it up 👀 |
(From Flathub!)
The text was updated successfully, but these errors were encountered: