Skip to content

face and hand landmark detection semantics and helper functions #5980

Open
@cloudspins

Description

@cloudspins

Google MediaPipe's face and hand landmark detection functionalities are essentially wrappers around OpenCV, which slows down the API. Proper use of the API requires additional solving as there are essentially no helper functions for solid HPR and XYZ extraction from the landmarks. The landmark API interface is inconsistent due to the fact that Mediapipe started as a 'hack' of OpenCV instead of an algorithm from the ground up, although the attempt is on-target. Acceleration can be introduced by OpenCV platform agnostic GPU, accelerated matrices, and polling. Training both back, left, right, top, bottom and front of face could improve detection as currently only the front upper half (quarter sphere) segment is trained; nevertheless, introducing horizontal and quaternion-pitch can compensate the front bottom half. The hand detection could be improved by training closed- fist and open- hand landmarks from different angles. Direct use of OpenCV without Mediapipe, or different algorithms, might be a more stable alternative.

Metadata

Metadata

Assignees

Labels

platform:pythonMediaPipe Python issuesstat:awaiting googlerWaiting for Google Engineer's Responsetask:face landmarkerIssues related to Face Landmarker: Identify facial features for visual effects and avatars.task:hand landmarkerIssues related to hand landmarker: Identify and track hands and fingerstype:performanceExecution Time and memory heap, stackoverflow and garbage collection related

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions