[X] I have updated the extension to the latest version
What happened?
This prevents users from converting the input_face_index widget to an input in order to index the same face using SEGS or other detection nodes.
I spent a fair amount of time trying to figure out the detection order, but it seems unpredictable. These are the most common results I got. Expected index order = 0, 1, 2, 3 etc, left-to-right for faces of the same size and level).
Actual index orders:
2 faces = 1, 0 (sometimes 0, 1)
3 faces = 2, 0, 1
4 faces = 0, 2, 1, 3
Steps to reproduce the problem
2 workflows attached
Indexing am image with 4 faces
Aa comparison of how SEGS and the and the FaceCropper node index the same image.
First, confirm
What happened?
This prevents users from converting the
input_face_index
widget to an input in order to index the same face using SEGS or other detection nodes.I spent a fair amount of time trying to figure out the detection order, but it seems unpredictable. These are the most common results I got. Expected index order = 0, 1, 2, 3 etc, left-to-right for faces of the same size and level).
Actual index orders:
Steps to reproduce the problem
2 workflows attached
FaceShaper 4 Faces Indexing.json FaceShaper Index Compare.json
Sysinfo
Mac Studio 24 core, 64 GB. MacOS 14.6.1. Safari, Chrome, Brave
Relevant console log
Additional information
Adding a
detection_order
widget might fix this issue (I'm adding this as a feature request as well).