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.

Sign up for GitHub

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

Jump to bottom

Mediapipe pose unstable on phone compared to desktop #387

Closed
usmanroshan opened this issue Dec 21, 2022 · 1 comment
Closed

Mediapipe pose unstable on phone compared to desktop #387

usmanroshan opened this issue Dec 21, 2022 · 1 comment
Labels
Out of scope Issues or features that are outside the scope of the plugin Pose Detection Issues corresponding to Pose Detection API Won't fix This will not be worked on

Comments

@usmanroshan
Copy link

Hi, I find the mediapipe pose to be much more unstable on the phone compared to on the desktop. For example on the phone the leg and feet keypoints move a lot whereas on the desktop they are much more stable (for the same video). Are the mediapipe models for phone and desktop different? Is there a way I can stabilize mediapipe pose on the phone? Thanks.
@fbernaly fbernaly added Won't fix This will not be worked on Pose Detection Issues corresponding to Pose Detection API Out of scope Issues or features that are outside the scope of the plugin labels Jun 26, 2023
@fbernaly
Copy link
Collaborator

Google's ML Kit is built only for Mobile. I dont know what API you are using to detect pose in desktop, so therefore I guess they are different models.
Please check out the first section of our README to learn how this plugin works and follow from there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Out of scope Issues or features that are outside the scope of the plugin Pose Detection Issues corresponding to Pose Detection API Won't fix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fbernaly @usmanroshan