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.

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

Hand pose frame #19

Open
taewookim0812 opened this issue Feb 20, 2024 · 2 comments
Open

Hand pose frame #19

taewookim0812 opened this issue Feb 20, 2024 · 2 comments

Comments

@taewookim0812
Copy link

taewookim0812 commented Feb 20, 2024

Hello

It seems the optimization function "solver.retarget()" accepts two inputs of hand_joint_seq and hand_frame_seq.
The hand_joint_seq can simply be acquired by 3rd-party libraries such as mediapipe, however, I wonder how did you get the hand_frame_seq, which represents the transformations between hand landmarks.

It would be appreciate if you let me know the way you get the hand_frame_seq, whether you get it from other libraries or any other implementation code is inside this repository.

Best regards

@yzqin
Copy link
Owner

yzqin commented Feb 21, 2024

Hello @taewookim0812,

hand_frame_seq refers to the sequence of hand poses derived from detectors that utilize the MANO framework. Since MediaPipe operates independently of the MANO/SMPL-X model, it doesn't provide such data.

If you're specifically interested in the retargeting aspect of DexMV, I suggest exploring our new retargeting library. It offers significantly enhanced performance compared to the previous retargeting module found in the DexMV repository.

@taewookim0812
Copy link
Author

I appreciate your prompt response. I'll check the library

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants