You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that the face tracking feature on Android is more prone to instability when compared to iOS. It frequently loses track of faces, making it challenging to maintain a consistent bounding box across frames. On the other hand, I find the face tracking on iOS to be reasonably reliable.
I'm curious to know if others have encountered a similar issue. Despite using the same options for the face detector in both versions, I suspect that the inconsistency may stem from the ML Kit library itself.
To investigate further, I plan to assess the quality of face tracking on both Android and iOS using the same image file. I will share the results with you here as soon as possible.
The text was updated successfully, but these errors were encountered:
@salembaira No. I didn't have time to investigate it. Besides, this issue might be related to the difference between platforms in ML Kit's implementation, rather than this frame processor. Unfortunately, ML Kit is not open-sourced and it makes it very hard to solve this issue.
I have noticed that the face tracking feature on Android is more prone to instability when compared to iOS. It frequently loses track of faces, making it challenging to maintain a consistent bounding box across frames. On the other hand, I find the face tracking on iOS to be reasonably reliable.
I'm curious to know if others have encountered a similar issue. Despite using the same options for the face detector in both versions, I suspect that the inconsistency may stem from the ML Kit library itself.
To investigate further, I plan to assess the quality of face tracking on both Android and iOS using the same image file. I will share the results with you here as soon as possible.
The text was updated successfully, but these errors were encountered: