Closed zzzark closed 7 months ago
Actually we do not use the raw lafan data, instead, we first retarget them to our character (including mapping the joint name and joint rotations), and the dataset can only process the motion that matches our characters. Maybe you can use our bvh as a template and try some retarget tools.
@heyuanYao-pku Thank you for your quick reply! Unfortunately I failed to download the BVH data in https://github.com/heyuanYao-pku/Control-VAE/tree/main/Data/ReferenceData/runwalkjumpgetup
due to the quota limit:
$ git-lfs pull
batch response: This repository is over its data quota. Account responsible for LFS bandwidth
should purchase more data packs to restore access.
Could you please provide a shorter BVH template (only the skeleton's topology) for reference?
@zzzark Hi, I've updated the repo and shifted LFS files to regular Git. Please check it out. For any issues, I'll be on it tomorrow.
@heyuanYao-pku Hi, I received the BVH data you provided, but the mapping of the joints doesn't seem very obvious. For instance, the number of joints and joint offsets in the original lafan1 data doesn't precisely match the retargeted data. Could you please share the code or tool you used to retarget the motion data?
@zzzark Thanks for reaching out about the BVH data. Actually, we started the project using data that had already been retargeted by previous teams, so we don't have a specific tool or code to share for that process. Maybe you can try some well-established tools like blender or motion builder.
OK, I'll try these tools.
@heyuanYao-pku Thank you for providing us the source code! I am trying to process the data with lafan1 dataset with the following code:
However, it seems that the names of the character's joints do not match what is in the BVH data. And I encountered an error
KeyError: 'pelvis_lowerback'
in this file. Is there any solution to work around this problem?