-
Notifications
You must be signed in to change notification settings - Fork 24
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
Questions: new upcoming models (replacing v0 ones) + details #199
Comments
Hi @jchwenger, thank you for the questions!
The llama branch was an experiment to run a small language model in-browser. We are also looking into incorporating Transformers.js into the library. There are things we have to consider like API for larger cloud models and increased package size. Things are mostly experimental at the moment, but we are excited about diffusion models and transformers. Suggestions and contributions are always welcome!
The
I just checked the v0 face mesh and there is a scaled version that no longer exists in v1. I am not too sure what the scaled version is since I never worked on the v0 models. Perhaps others can provide more context about it. If it is something that people find helpful, we could add it back! |
Hi @ziyuan-linn, And thanks a lot for your answers! Integrating the flexibility of Huggingface for models would be quite amazing! I would be interested in helping out if I can, although that might have to wait until January next year, it's going to be tricky for me before that. Props to the Sound + Teachable Machine docs! As for the scaling, it returned normalised keypoints, which would allow you to have a facemesh following your movements, but say only in one corner of the canvas. I think this can still be achieved by normalizing by the canvas size manually (I haven't tried, but that seems straightforward). Probably best not to have it, so that the object returned by the model is slightly simpler and easier to read! |
Hi there,
Since @ziyuan-linn said I could do that, I'm opening this more as a question for the future of the new API rather than a bug report:
Thanks a lot!
The text was updated successfully, but these errors were encountered: