Difference between motionx2humanml and the original HumanML3D data

[weihaosky]

Hi, I convert the MotionX data to humanml format according to motionx2humanml, but the converted data is slightly different from the original HumanML3D data, as shown in the following:

output.mp4

The first one is the original HumanML3D data '000000.npz'. The second one is converted from motionx2humanml. The third one is MotionX. Their framerates are different. Then I adjust the framerate to make them in the same framerate, as shown in the following:

output.mp4

However, they are still slightly different if you watch carefully. Also, the scale of the trajectory on the ground is different.

May I ask what is the cause of the difference and how to solve it? Many thanks!

[XingliangJin]

I found the same issue. It's more evident in the clip "000021.npy". Here, the first one is the original HumanML3D data. The second one is converted from motionx2humanml. The third one is MotionX. It can be seen that the trajectory difference between them is obvious. The motion trajectory of MotionX is elongated, and there is a serious foot sliding problem.

[shunlinlu]

Hi,

Thanks for your information. It may be because we use different subsets of AMASS. Original humanml uses smplh, while we use smplx. We checked that there are differences between the same case of smplh and smplx. We can not solve it now, since it's more like the AMASS problems. If you want to keep the same with the original Humanml, you may use smplh subset.

Shunlin

[XingliangJin]

Thank you for your checking! Since it's an AMASS problem, I will use smplh subset for the Humanml set.