Closed philiprkk closed 4 months ago
Hi @philiprkk,
We believe this behavior applies across all platforms. You can see an example input from our team. However, please allow us some time to discuss with the team and confirm once.
Thank you!!
Hi @philiprkk,
We have received confirmation from the team that this behavior is expected. The first frame is ignored in Android, similar to Python and JavaScript, indicating it occurs across all platforms.
Thank you!!
This issue has been marked stale because it has no recent activity since 7 days. It will be closed if no further activity occurs. Thank you.
This issue was closed due to lack of activity after being marked stale for past 7 days.
Description of issue (what needs changing)
No response
Clear description
Why does the Python documentation for live stream mode say:
"When running in the live stream mode, the Face Landmarker task returns immediately and doesn’t block the current thread. It will invoke the result listener with the detection result every time it finishes processing an input frame. If the detection function is called when the Face Landmarker task is busy processing another frame, the task will ignore the new input frame."
But the Android version only says:
"When running in the live stream mode, the Face Landmarker task returns immediately and doesn’t block the current thread. It will invoke the result listener with the detection result every time it finishes processing an input frame."
Does the Android version not ignore frames when the solver is currently processing? It does seem that way sometimes in my experience.
Correct links
https://ai.google.dev/edge/mediapipe/solutions/vision/face_landmarker/android https://ai.google.dev/edge/mediapipe/solutions/vision/face_landmarker/python
Parameters defined
No response
Returns defined
No response
Raises listed and defined
No response
Usage example
No response
Request visuals, if applicable
No response
Submit a pull request?
No response