feat: show face, neck, torso and arms tracking on camera - #21
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The overlay drew hands only, so "it is not working" and "it cannot see your face" looked identical. Now every tracked part is drawn in its own colour, with a chip per part that goes green when it is being tracked and red when it is not.
Separate colours because the parts fail independently: hands track fine at arm's length while the face is out of frame, or the torso is cropped while everything else is good. One uniform skeleton would hide which.
The face is drawn as points rather than mesh edges — 468 edges are unreadable at video size, and a scatter already shows it is tracked. Legs are not tracked at all: nothing below the hips carries meaning in LSE.
Why pose is here at all
Measured, not assumed. On SWL-LSE's held-out test split, normalising hand position against the torso instead of the image frame is worth +5.7 points of top-1 (0.632 → 0.689). "Hand at chin height" is a fixed number in body coordinates and a moving one in image coordinates — it changes when the signer steps closer.
Pose and face load with
.catch(() => null)and the app keeps working without them: hands are the only model recognition genuinely needs, so the other two are enhancements, not dependencies.source.availablereports which came up.Engine grows from ~32 MB to ~41 MB; the storage panel says so and can still free it.