Two processes happening at the same time?

[NathanMllt]

I am running FaceIt on a video using the DBSCAN and constant binary method and in FaceIt's command prompt this is displayed:

2025-11-05 17:01:58,662 - INFO - [Stream] 0% (1/61391) (00:00 @ 55.5 fps)
2025-11-05 17:01:58,666 - INFO - [Stream] 0% (1/61391) (00:00 @ 33.8 fps)
2025-11-05 17:01:58,666 - INFO - [FaceIt] 0% (0/61391) | elapsed 00:00 | ETA --:--
2025-11-05 17:05:31,370 - INFO - [Stream] 10% (6140/61391) (03:32 @ 28.9 fps)
2025-11-05 17:07:46,201 - INFO - [Stream] 10% (6140/61391) (05:47 @ 17.7 fps)
2025-11-05 17:08:02,060 - INFO - [FaceIt] 10% (6140/61391) | 16.9 fps | elapsed 06:03 | ETA 54:30
2025-11-05 17:08:16,417 - INFO - [Stream] 20% (12279/61391) (06:17 @ 32.5 fps)
2025-11-05 17:35:27,789 - INFO - [Stream] 30% (18418/61391) (33:29 @ 9.2 fps)
2025-11-05 17:38:32,443 - INFO - [Stream] 20% (12279/61391) (36:33 @ 5.6 fps)
2025-11-05 17:38:48,642 - INFO - [Stream] 40% (24557/61391) (36:49 @ 11.1 fps)
2025-11-05 17:39:19,553 - INFO - [FaceIt] 20% (12279/61391) | 5.5 fps | elapsed 37:20 | ETA 2:29:22
2025-11-05 17:41:55,365 - INFO - [Stream] 50% (30696/61391) (39:56 @ 12.8 fps)
2025-11-05 17:44:55,035 - INFO - [Stream] 60% (36835/61391) (42:56 @ 14.3 fps)
2025-11-05 17:48:06,652 - INFO - [Stream] 70% (42974/61391) (46:08 @ 15.5 fps)
2025-11-05 17:49:59,860 - INFO - [Stream] 30% (18418/61391) (48:01 @ 6.4 fps)
2025-11-05 17:50:15,105 - INFO - [FaceIt] 30% (18418/61391) | 6.4 fps | elapsed 48:16 | ETA 1:52:37
2025-11-05 17:51:38,805 - INFO - [Stream] 80% (49113/61391) (49:40 @ 16.5 fps)

I was more used to having the frames loaded first and then the pupil and face traces being computed but now it seems that I have both a Stream and a FaceIt process occurring at the same time? Is this normal?

[NathanMllt]

It seems there was an issue with the plotting of the pupil at the end even though it is being detected

[NathanMllt]

This looked like this before removing blinking:

[faezehrabbani]

Regarding your first question, Yes, that’s normal.
FaceIt now runs streaming and analysis in parallel. The [Stream] log shows frames being read, while [FaceIt] shows the actual processing. This design improves efficiency and reduces memory usage for long videos.

[faezehrabbani]

It seems there was an issue with the plotting of the pupil at the end even though it is being detected

When there’s a very strong outlier in the pupil ROI calculation — typically caused by blinking or noise — the rest of the trace may appear almost flat. If the blinking or noise persists for too long, it’s possible that FaceIt’s built-in blinking detection or pupil filtering cannot fully identify it, which is a current limitation of the pipeline.

Without directly checking the video and raw data, it’s difficult to determine the exact cause. However, I recommend updating your FaceIt installation to the latest version and running the analysis again.

If the issue persists, you could inspect the video and the detected pupil area trace (from the .npz file) before blinking removal to verify whether the raw pupil detection follows the data trend. Based on your screenshots, the pupil seems to be detected correctly, so it’s likely that FaceIt performs well before filtering — but the strong blinking outlier makes it hard to visualize the true trace.

In that case, the best approach might be to disable FaceIt’s blinking detection for that session and instead remove blink frames later using a custom post-processing step.

[NathanMllt]

Thank you for your answer! I will try this

[faezehrabbani]

It seems there was an issue with the plotting of the pupil at the end even though it is being detected

The issue was caused by an incorrect total-frame calculation here. It’s been fixed in the latest commit. Please update FaceIt and let me know if the problem persists

[NathanMllt]

With the new update I cannot open videos in FaceIt