mediapipe: JavaScript Face Mesh multiFaceGeometry returns empty

Hi,

I am using MediaPipe’s FaceMesh solution in JavaScript. I am able to obtain landmarks from multiFaceLandmarks which returns 468 landmarks. There is also multiFaceGeometry array which is empty and I would like to know why it returns empty. multiFaceGeometry might be what I am actually intend to use because as stated in MediaPipe Face Mesh

The Face Geometry module moves away from the screen coordinate space towards a metric 3D space and provides necessary primitives to handle a detected face as a regular 3D object. By design, you’ll be able to use a perspective camera to project the final 3D scene back into the screen coordinate space with a guarantee that the face landmark positions are not changed.

Here is the result that I get:

Screen Shot 2022-01-13 at 3 14 41 PM

Can you help me with this? Thanks in advance!

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16

Most upvoted comments

@tyrmullen any ETA for multiFaceGeometry API official release?

Screen Shot 2022-02-04 at 5 36 32 PM

Hello again, is there any documentation for me to understand above values? For multiFaceLandmarks it’s pretty straightforward and explained in the documentation.

Screen Shot 2022-02-04 at 5 38 00 PM

The update seems to be gone? Now the latest version is 0.4.1633559619 again 👀

I have seen that there has been an update of the face mesh module on NPM to version 0.4.1657299874 three days ago. Are any updates included regrading this issue?

Correct-- further release of multiFaceGeometry should allow it to work with refineMesh.

@tyrmullen just to confirm: further release of multiFaceGeometry API should resolve the issue and we need to wait for the release. Correct? Thanks

Correct-- and this will likely be the next update, but there’s no definite ETA at this point.

That’s what I was referring to when I said you’d need to leave refineMesh as false above. The CodePen does not crash if you enable face geometry and DON’T enable mesh refinements. So you can experiment with one or the other, but not both.

The multiFaceGeometry API has not yet been officially released (IIRC we still need to fix its interactions with refineMesh), so really that property should simply not exist. However, if you want to experiment with it (with no guarantees for any sort of proper behavior), then you might be able to see something if you set enableFaceGeometry to true in the options.